You are here:

This section allows adding or removing users from the project and limiting the actions they can take (editing user privileges).

An Administrator (by default, the creator of the project) 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.

Gestión de usuarios

Setting options

  • Add User: Create a new system user (introducing its basic information as name, email and password) and add it to the project
  • Invite: (an already existing) user to the project

It shows and allows to edit the user’s details, such as the name, email or password to access the portal

Edit the user’s privileges, limit access to the different sections of the portal

Edits the criteria that the user can assign

Edit the content categories that the user can upload

Configure the notifications that reach the Administrators or the user’s mail when a user performs an action

Filter the viewing permissions of Playlists, Blocks, etc

User Management System

Admira’s new user management system allows for an specific role setup for each project, based on a user level hierarchy.

There are five levels ordered by number, depending on this hierarchy levels each user role created for a project will have more or less permissions available.

The hierarchy level with all permissions included is the first one, lower levels will have more permit limitations regarding access to the web portal sections, content and project information.

User Management System


By default all projects have two roles available created by the system:

  • Admin: Belongs to level 1. Includes all permissions and is the role assigned to the project creator and/or administrator
  • User: Belong to level 2. This role has a relation with the Admin role (upper level) and includes all channel management permits except those regarding the project administration (like the user management system)

It is possible to deselect or add the desired permissions included in these default roles.

Also, admin user may modify each hierarchy level to adapt the user settings to the specific project needs (there is no limit to create as many roles as needed) 


Each user role has to be assigned only to one hierarchy level, this setup is defined when creating a new role and can’t be changed later



A role may have a maximum of permissions included in its hierarchy level and a minimum of one.

It may also occur that a role in level 2 has less permissions selected that another one of level 5, despite of this fact the hierarchy level is still important because there is a relation between levels:

Each role is at least related with one of the upper levels and to all roles created at upper levels, as a maximum. Roles created at the first level are excluded because there are not upper levels, and roles created at level 5 also are excluded from this relation because there are not lower levels.


There are no relations between roles created at the same level

Viewing options

System elements affected by this relation between levels are:

  • Contents
  • Reservations
  • Templates
  • Playlists
  • Blocks

By default, each role will be able to see only the elements created by users of the same role and, optionally, through permissions, will also be able to see elements created by other roles at the same level. In addition, if there are relations with roles located at lower levels, it will be able to see elements of those roles.

Finally, if criteria and/or categories are assigned to the users, they can be used to filter the elements that don’t belong to the user.

How to assign roles to project users

To assign or modify a user role, you may clic on the “privileges” icon, on the project users list, as shown in the image below. Then, select the desired role.

User role

User permissions filter

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 (contents, players, playlists, reservations … ) by assigning criteria and category tags to users and subsequent selection of the permissions filtering options.


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 distribution mode).

Permissions filter
Apply criteria to user


It is important that the user with filtered permissions has the criteria and category tags correctly assigned, from the options of the project’s user list

Print Friendly, PDF & Email
Next Dashboard
Table of Contents