Close

User Management

Omniata allows controlling for what tools and content the Omniata users can access. The access rights are determined by user groups through Roles. There is no limit for the number of different Roles in the organization or for the number of Roles per user. Permissions are assigned for Roles, and if one User has several Roles with different Permissions, the User has the broadest access given by the Roles.

Access control is managed under User Management that can be accessed by selecting the main navigation on the left top corner, selecting Global Settings all the way down, and navigating to 'User Management' section. Within the section you can see first assigned Roles per account, manage Roles, and define Permissions.

Permissions can be set on several different levels (see picture): per Environment, per Application, per Project and per Dashboard Group. Permissions can be set per each Environment/Project/Application separately or to all Environments/Projects/Applications. There are also Permissions for controlling organization administration.

Accounts

Users are members of the organization or its external partners who need access to Omniata platform. Here you can:

  1. Add new Users by sending invite
  2. Edit Roles of User
  3. Delete User by removing that user from the Organization

Adding New Users (Sending an Invitation)

New users are added by sending them invitation to the organization. To send an invitation to the organization, navigate to Global Settigns > User Management > Accounts.

  1. Select 'Invite New User'.
  2. Enter the email(s) of the people to invite, separated by comma, semicolon or in separate lines.

  3. Select the Role(s) that you'd like to give to the people you are inviting. This setting can be changed later if necessary.

  4. Click Send Invites.

The selected users will receive an email with login instructions.

Editing Roles of Users

To edit the roles of an user, click on the user name and redefine the Roles.

Deleting Users (Removing from Organization)

To delete an user, select 'Remove' from Actions.

Roles

Roles are groups of users that share the same access privileges. There are some built-in roles in Omniata, and you can create new roles in order to limit the access that people should have according to your policies. Roles can be created for example for different projects or different user levels.

  1. Edit the Permissions of the Role.
  2. Edit the Role.
  3. Delete the Role.
  4. Create new Role.

Built-In Roles are the following:

  • All Users: Access to everything, excluding admin rights.
  • Omniata Organization Admin: Access to everything, including admin rights.

Built-in Roles cannot be edited or deleted. Their Permission settings can be edited.

Creating New Role

Select New Role. Here you can:

  1. Enter the name of the Role.
  2. Click Create Role.

Editing Role

Select Edit on the Role in question. Here you can:

  1. Edit the details.
  2. Click Update Role.

Deleting Role

Select 'Delete' under Action on the Role in question.

Permissions

Global Permissions

On global level, the following permissions can be set.

  • People
    • Invite People to Organization - Allows to invite additional users to Omniata
    • Remove Members from Organization - Allows to revoke user's access from Omniata
    • Manage Roles - Allows to create, modify and delete roles
    • Manage Role Permissions - Allows to change the permissions of a role
    • Update Member's Roles - Allows to change another user's role
    • Send Notifications to Users - Allows to send a notification to other users
  • Engager
    • Manage Channels - Allows to modify, create and delete channels in the Engager
    • Manage Segments - Allows to modify, create and delete segments in the Engager
    • Manage Experiments - Allows to modify, create and delete experiments in the Engager
    • Manage Content - Allows to modify, create and delete content in the Engager
    • Manage Content Types - Allows to modify, create and delete content types in the Engager
  • Environments
    • Query All Environments - Allows to view data in all Environments
    • Query [Your Environment A] - Allows to view data in [Your Environment A]
    • Query [Your Environment B] - Allows to view data in [Your Environment B]
  • Configuration
    • Organization Settings - Allows to modify organization settings
    • Manage All Lookup Tables - Allows to modify, create and delete items in Lookup Tables
  • Applications
    • Manage All - Allows edits to Applications
    • Read All - Only view rights.
  • Projects: set Permissions to all Projects. For information on the different options, see below Project Permissions.

Project Permissions

Permissions on Data Model level control what operations a Role can do with the Data Model. These permissions affect only the Data Model in question. Roles can be assigned in the following categories.

  1. Viewer
    • Can view Widgets and Dashboards
    • Can view all other ProjectObjects
  2. Editor
    • Viewer permissions
    • Can edit Widgets and Dashboards
  3. Data Analyst
    • Editor permissions
    • Can create, edit and delete data fields and reporting tables
    • Can create and edit jobs and publish data
    • Can use SQL mode
  4. Developer
    • Viewer permissions
    • Can use Event Console
  5. Data Engineer
    • Data Analyst permissions
    • Can use Event Console
  6. Data App (Project) Owner
    • Can create, edit and delete all Project objects
    • Can use Event Console and SQL mode
    • Can edit or delete the Project.

On Global Level, Project Permissions can be set to all Projects of the organisation as a whole.

Permissions to individual Projects and permissions to all Projects are interpreted parallel. For example if a Role has Editor permissions to all Projects and Developer permissions to one certain Project, the Role has a combination of Editor and Developer permissions to that Project and Editor permissions to all the other Projects.

Application Permissions

Permissions on Application level control what operations a Role can do with the Application. These permissions affect only the Application in question. Roles can be assigned either reading permissions or reading and writing permissions.

Reading permissions enable the Role to see:

  • The Application and all data assigned to it
  • All Engager material of the Application (Channels, Segments, Experiments, Contents, Content Types)

In addition to these, reading and writing permissions enable the Role to edit and delete the Application. In order to edit Engager materials, a Role needs to be set Engager permissions on the Global Level.

On Global Level, Application Permissions can be set to all Applications of the organisation as a whole.

Permissions to individual Applications and permissions to all Applications are interpreted parallel. For example if a Role has reading permissions to all Applications and reading and writing permissions to one certain Application, the Role has reading and writing permissions to that Application and only reading permissions to all the other Applications.

Dashboard Group Permissions

Permissions on Dashboard Group level control what operations a Role can do with the Dashboard Group. These permissions affect only the Dashboard Group in question. Roles can be assigned either reading permissions or reading and writing permissions.

Reading permissions enable the Role see that Dashboard Group and its Dashboards in Analyzer. Reading and writing permissions enable the Roles also edit the Dashboard Group.

By default, Dashboard Group Permissions are inherited from the Data Model which contains the Dashboard Group. Thus, Roles with Viewer or Data QA permissions to the Data Model have reading permissions to Dashboard Group and Roles with Editor, Data Analyst, Data Engineer or Data Model Owner permissions to the Data Model have reading and writing permissions to the Dashboard Group. However, if any Role is manually assigned either reading or reading and writing permissions to a Dashboard Group, that overrides all the default permissions.

Dashboard Group Permissions which are assigned manually are used instead of the default permissions, not in addition to them.

Dashboard Subgroup Permissions

If Dashboard Group has Subgroups, by default, the permissions of the parent group are passed down to all the child groups. If any Role is manually assigned permissions to Dashboard Subgroup, those permissions override all the default permissions inherited from the parent group. However, permissions of other Subgroups of the parent group are not affected.

Managing Permissions

Managing Global Permissions

Select Edit Permissions on the Role in question. There you can:

  1. Set up Global Permissions. For more information on Global Permission, see Permissions.
  2. Click Update Permissions.

Managing Project Permissions

Select Edit Permissions on the Role in question. The following page opens up.

  1. Set up Project Permissions to individual Projects.
  2. Set up Project Permissions to all Projects.
  3. Click Update Permissions.

For more information on Project Permissions, see Permissions.

To edit the Permissions of one specific Project, one can also navigate within a Project to Settings > General > Permissions.

Managing Application Permissions

Application permissions are edited for one Application at a time. To edit the Application permissions, navigate within a Project to Settings > Applications > Edit. There you can set up Application Permissions. For more information on Application Permission, see page Permissions.

Managing Dashboard Permissions

Dashboard permissions are edited for one dashboard at a time. To edit the Dashboard permissions, navigate within a Project to Settings > Dashboards. There you can set up Dashboard Permissions.

If Role is manually assigned either reading or reading and writing permissions to a Dashboard, that overrides all the default permissions inherited from the Project, or the parent Dashboard, if applicable.

This article was last updated on February 25, 2016 22:22. If you didn't find your answer here, search for another article or contact our support to get in touch.

Contact Sales

Add Phone Number