Users
Last updated
Last updated
Allows you to add or remove users from the project and limit the actions they can do (edit user privileges).
An Administrator (by default, the project creator) has access to all aspects of the project, can add a new user and edit their basic information (name, email address, password, etc.), as well as edit the privileges and permissions of each.
It is also possible, by assigning criteria and categories, to limit the content distribution options of each non-administrator user.
Add User: Create a new system user (enter name, email and password) and add it to the project.
Invite a user: (already existing in the system) to the project.
Shows and allows you to edit user details, such as name, email or password to access the portal
Edit user privileges, limit access to different sections of the portal.
Edit the criteria that the user can assign.
Edit the categories that the user can assign
Configure the notifications that reach the Administrators or the user’s mail when a user performs an action
Filter the viewing permissions of Playlist, Blocks, etc.
Admira’s user management system allows the configuration of specific roles for each project and is based on the establishment of a hierarchy of user levels.
There are five levels ordered numerically, depending on the level of the hierarchy, each user role defined in the project will have more or less permissions.
The hierarchy with all the permissions will be that of level 1 and as the level descends, the permissions will be reduced to level 5, which will have the most limited permission configuration in terms of access to the different sections of the portal and to the contents and information of the circuit.
By default, all projects have two roles already created by the system:
Admin: Belonging to the level 1 hierarchy. It includes all permissions and is the one assigned to the creator user and/or project administrator
User: Belongs to the level 2 hierarchy. It is related to the Admin role (higher level) and includes all channel management permissions except those specific to project administration (eg user management)
It is possible to uncheck or add the desired permissions from these predefined settings.
In addition, more personalized modifications can be made to each level of the hierarchy and adapted to the needs of the project since as many roles as necessary in each case can be created.
Each user role can only be assigned to one level of the hierarchy that will be defined at the time of creation and cannot be changed later.
At most, a role can have all the permissions available to its level in the hierarchy and at least one permission. It may be the case that a level 2 role has fewer permissions than a level 5 role, however the hierarchical level of the roles is important because there is a relationship between levels:
Each role will be related to at least one role at the level above it. Roles at level 1 are excluded since there is no higher level and roles at level 5 because there are no lower levels.
There are no relationships between roles at the same level.
The elements of the system affected by this relationship between levels are:
Contents
Campaigns
Templates
Playlists
Blocks
By default, each role will only be able to see the elements created by that role and, optionally, through permissions, it will be able to see the elements created by other users of the same role.
In case you have relationships with lower level roles, you will also be able to see items from those other roles.
In case of having criteria and categories assigned to the users of those roles, they can be used to filter the elements that are not the user’s own.
To assign or modify a user’s role, click on the “privileges” icon in the list of project users, as shown in the image, and select the desired role.
In addition to the access permissions to the portal sections and project management capabilities that are defined in the user’s role, it is also possible to limit the visibility of the different elements of the system (content, players, playlists, reservations…) through assigning criteria and category tags to users and subsequent permission filter marking.
From this section you can define the elements created in the project such as playlists, blocks, templates, schedules, reports… to which the user will have access, as well as filtering by criteria and categories of players, content and reservations (advanced mode of distribution).
It is important that the user with filtered permissions has the criteria and category tags correctly assigned, from the project user list options
