Wednesday, December 2, 2015

User Roles for a successful eMAM implementation

POC –   Point of Contact for eMAM system

This is the business contact for an organization for any legal or accounting issues.   They may or may not be have other roles below.  POC must maintain communication channels between the different internal staff and the eMAM teams to coordinate activities.   They should play a similar role with system integrators, hardware, and software vendors.   


This person is a Hardware/Software systems administrator. This person must have a working knowledge of Windows Server, basic knowledge of Microsoft SQL server, and networking experience. This person must have administrator access and knowledge of how to create and share volumes on the storage device used by the eMAM system.  If eMAM is implemented in an Active Directory/LDAP environment, then this person will also need to have knowledge and permission to create LDAP/AD users.  This person  should be the main IT administrator for the transcoder, archive software, and other systems that will be implemented with eMAM.

Unit Admin:

This person has a leadership role for one or more groups of business users.  He/she should set up and manage the metadata structure, user accounts, and categories/projects, and assign metadata sets to users and groups. This person will decide what ingest and delivery profiles users and groups use.  He/she must work closely with the Super Admin to effect changes in the system as needed.  This person must work to train and support the users in their unit.


This person is the production operator of the system. This person will have only the rights and permissions and access to the select categories of assets given by the Unit Admin(s).  This person may be an ingest operator using eFeeder, a person with view only access to videos, an editor using an editing software such as Adobe Premiere, a librarian who is responsible for entering in metadata, or an Archive/Restore specialist.  A power user is licensed for all of the user roles in the systems.   A basic user has access to only browse and share functions, with no access to ingest, archive, media management, or the tablet interfaces.


Individuals not defined as users in the system cannot look at the content in the system in any way unless a user shares with them through a social media link, through an eBIN email, or an external review/approval link sent by email.  

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.