Skip to main content Skip to complementary content

Permissions granted by security roles

A security role grants a set of permissions to all users who have been assigned the role. When a user is assigned to more than one role, they are granted the permissions from each role. Permissions define what a user can see and do in Qlik Cloud.

Information noteThis topic is applicable to the Standard, Premium, and Enterprise editions of Qlik Cloud Analytics and Qlik Cloud Data Integration. If you have a Qlik Sense Enterprise SaaS, Qlik Sense Business, or Qlik Cloud Government subscription, see Managing users - User-based subscriptions.

Security roles control actions and access rights for users and administrators in the tenant. In addition to the tenant-level roles, there are also space roles that control user actions on content within spaces. For more information about space roles, see Managing permissions in shared spaces, Managing permissions in managed spaces, and Data space roles and permissions.

Permissions for tenant administrators

Users who are assigned the Tenant Admin role have broad permissions to manage a tenant. This includes managing users, access control, and tenant configuration.

For certain actions, the tenant administrator needs additional permissions. You need the Developer role to create API keys and you need to be a member of a space to access data and apps in that space.

Tenant administrators are the only administrators that can take ownership of and delete other users' personal content. Tenant admins cannot export apps from other users' personal spaces, but they can take ownership of these apps and then export them. See: Changing owner of apps and Exporting apps.

The table lists the permitted actions on content in other users' personal spaces.

Tenant Admin permissions on content in other users' personal spaces
Resources Permissions
Apps

List, Open, Delete, Change owner

Data connections

List, Edit, Delete, Open (for app reload)

Can also open (read) data files for app reload.

Information noteA tenant administrator cannot delete their own Tenant Admin role.
Warning note

Anyone who is assigned the Tenant Admin role may be granted access to content (which may include personal content) relating to all users in the tenant to which the Tenant Admin role is assigned.

Permissions for analytics administrators

Users who are assigned the Analytics Admin role are administrators with limited permissions. They have access to parts of the Management Console, such as managing shared and managed spaces, extensions, and themes.

Analytics administrators cannot manage users in the Users section of the Management Console. They can manage space members in space types that they are allowed to manage.

Analytics administrators can manage user resources for analytics services within shared and managed spaces. They cannot access content in other users' personal spaces. This includes apps, data files, data assets, and data connections.

The tables list the permissions that are granted by this role.

Analytics Admin permissions
Resources Permissions
Shared spaces Create, Read, Update, Delete
Managed spaces Create, Read, Update, Delete
Extensions Create, Read, Update, Delete
Automations Enable, Disable, List, Delete, Change owner
Themes Create, Read, Update, Delete
Sharing service task Create, Read, Update, Delete
Analytics Admin permissions on content in shared and managed spaces
Resources Permissions
Apps List, Delete
Generic links Create, Read, Update, Delete
Data sets Read, Delete
Data assets Read, Delete
REST data files List, Delete
Data connections List, Delete

Permissions for data administrators

Users who are assigned the Data Admin role are administrators with limited permissions for data spaces and data resources within those spaces. In the Management Console, they can access only the areas for which they have permissions.

Data administrators cannot manage users in the Users section of the Management Console. They can manage space members in space types that they are allowed to manage.

Data administrators cannot access content in other users' personal spaces.

The tables list the permissions that are granted by this role.

Data Admin permissions
Resources Permissions
Data space Create, Read, Update, Delete
Data Admin permissions on content in data spaces
Resources Permissions
Data sets List, Read, Delete
Data assets List, Read, Delete
Resource connections List, Create, Read, Update, Delete
Data stores List, Read, Delete

Permissions for audit administrators

Users who are assigned the Audit Admin role, in addition to the Developer role, can access app feedback and usage information captured as part of the Natural Language API. An audit administrator can view a variety of usage metrics for Insight Advisor and Insight Advisor Chat. This API enables evaluation of patterns in user interactions with apps, including feedback provided for analyses generated by Insight Advisor and Insight Advisor Chat. This information can be used to improve user experience through adjustments to the app, either within the data or in the business logic of the app.

This API only returns app information from shared and managed spaces. An audit administrator does not have access to usage metrics data for personal spaces.

To view the usage metrics of an app, an audit administrator must also be assigned one of the following space roles in the space where the app is located.

Roles in shared spaces:

  • Owner

  • Can manage

  • Can edit

  • Can view

Roles in managed spaces:

  • Is owner

  • Can manage

  • Can contribute

  • Can view

  • Has restricted view

Information noteThe Natural Language API does not check section access controls in the app's load script. If an audit administrator has the Developer role and can open apps (as provided through the space permissions), they can view the app usage metrics.

For more information about how Insight Advisor user interaction data can be used to improve app usability, see Using feedback and usage metrics to improve app usability. For specifics about the Natural Language API, see Natural language, and for a tutorial on using the Natural Language API, see Collect and share Insight Advisor feedback.

The table lists the permissions that are granted by this role.

Audit Admin permissions
Resources Permissions
Audit

Read

Filter action of the Natural Language API Read

Permissions for space creators

Users with one of the space creator roles have the permission to create a space of that type from the hub.

The table lists the permissions that are granted by the roles.

Data Space Creator permissions
Resources Permissions
Data spaces Create
Managed Space Creator permissions
Resources Permissions
Managed spaces Create
Shared Space Creator permissions
Resources Permissions
Private spaces Create

For new tenants, the Shared Space Creator role is automatically assigned to all users by default. Tenant administrators can turn off this automatic role assignment by toggling off the Auto assign option under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

Permissions for private analytics content creators

Users with the Private Analytics Content Creator role can create analytics content in personal spaces. Users without this role can still create monitored charts, alerts, subscriptions, and notes in their personal space.

The table lists the permissions that are granted by this role on resources in personal spaces.

Private Analytics Content Creator permissions
Resources Permissions
Qlik Sense apps

Create, Duplicate, Import, Source

QlikView apps

Duplicate, Import, Source

Data connections Create, Update, Change space
Data files

Create, Update

Data sets Create, Update, Profile

Note that tenant administrators must also have the Private Analytics Content Creator role to perform the actions in the table.

For new tenants, the Private Analytics Content Creator role is automatically assigned to all users by default. Tenant administrators can turn off this automatic role assignment by toggling off the Auto assign option under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

As you can see in the table above, this role does not control all actions on the resources. If you remove the role from a user who has analytics content in their personal space, the user can still use that content. Any already existing data connections and data files can be selected and used, and scripts can be updated and reloaded.

If a scheduled reload task, that has a binary load or store in the script and is located in a personal space, stops working, the user of the personal space needs to log in. By logging in, the Private Analytics Content Creator role is automatically assigned to the user, which solves the reload issue.

Permissions for automation creators

Users with the Automation Creator role can create automations in personal spaces.

The table lists the permissions that are granted by this role.

Automation creator permissions
Resources Permissions
Qlik Application Automation

Create, Update, Run, Enable, Disable, Duplicate

For new tenants, the Automation creator role is automatically assigned to all users by default. Tenant administrators can turn off this automatic role assignment by toggling off the Auto assign option under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

Permissions for collaboration platform users

Users with the Collaboration Platform User role in the tenant can interact with the Insight Advisor Chat service in external collaboration platforms.

The Collaboration Platform User role is assigned on an opt-in basis, meaning that tenant administrators must assign the role to specific users who need it. The Auto assign option is off by default for this user role. Tenant administrators can turn on this automatic role assignment by toggling the option on under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

Permissions for developers

You need the Developer role to generate API keys. Users with this role have an API keys section on their user profile menu. For more information, see Managing API keys.

The table lists the permissions that are granted by this role.

Developer permissions
Resources Permissions
API keys

List, Create, Read, Update, Delete

Permissions for data services contributors

You need the Data Services Contributor role to work with Qlik Cloud Data Integration. Users with this role can access the Qlik Cloud Data Integration home by selecting Data Integration from the launcher menu .

The table lists the permissions that are granted by this role.

Data Services Contributor permissions
Resources Permissions
Data services

Read

For new tenants, the Data Services Contributor role is automatically assigned to all users by default. Tenant administrators can turn off this automatic role assignment by toggling off the Auto assign option under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

Permissions for business glossary stewards

With the Steward role, you can create, update, and delete a glossary as well as edit or delete a term in Verified state or change the term status to Verified. In addition to the Steward role, you must also be assigned the Can edit space role in the space where the glossary is located.

The table lists the permissions that are granted by this role.

Steward permissions
Resources Permissions
Business glossaries

Create, Read, Update, Delete

Glossary terms Change status

For new tenants, the Steward role is automatically assigned to all users by default. Tenant administrators can turn off this automatic role assignment by toggling off the Auto assign option under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

Permissions for embedded analytics users

The Embedded Analytics User role is a limiting user role. This role provides access to apps and app content while disabling access to all other parts of Qlik Cloud, such as the Analytics hub, Application Automation, Data Integration, and profile settings.

If a user is assigned both the Embedded Analytics User role and administrator roles, they can access the parts of the Management Console permitted by their administrator roles via https://<your tenant address>/console.

Users with the Embedded Analytics User role can access apps and sheets via direct links, for example, in embedded use cases. What the user is permitted to do with apps is based on the user's other security roles and space roles.

The Embedded Analytics User role is disabled for all users by default. Tenant administrators can turn on automatic assignment of the role to all users by toggling on the Auto assign option under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

Permissions for AutoML experiment contributors

The Automl Experiment Contributor role allows a user to work with ML experiments. With this role, you can create and manage ML experiments. You can also create ML deployments from models trained in an experiment, and view the ML deployments in a space where you have the required permissions.

Note that to work with ML experiments, you must meet all other user requirements as well. For a list of requirements for working with Qlik AutoML, see Who can work with Qlik AutoML.

The table lists the permissions that are granted by this role.

Automl Experiment Contributor permissions
Resources Permissions
ML experiments

Read, Create, Update, Delete, Move

ML deployments Read, Create

This role is automatically assigned to all users by default. Tenant administrators can turn off this automatic role assignment by toggling off the Auto assign option under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

Permissions for AutoML deployment contributors

The Automl Experiment Contributor role allows a user to work with ML deployments. With this role, you can create and manage ML deployments. You can also view the ML experiments in a space where you have the required permissions.

Note that to work with ML experiments, you must meet all other user requirements as well. For a list of requirements for working with Qlik AutoML, see Who can work with Qlik AutoML.

The table lists the permissions that are granted by this role.

Automl Deployment Contributor permissions
Resources Permissions
ML experiments

Read

ML deployments Read, Create, Edit, Delete, Move, Run (use in predictions)

This role is automatically assigned to all users by default. Tenant administrators can turn off this automatic role assignment by toggling off the Auto assign option under Users > Permissions in the Management Console. See Assigning security roles to everyone in the tenant.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!