Skip to main content Skip to complementary content

Permissions in User Default and custom roles

User Default settings and custom roles control permissions for users and administrators. User Default defines a baseline for all users, while custom roles allow more specific permissions for selected users or groups. The table below lists all available settings, with additional details in the sections that follow.

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

Understanding User Default permissions

The User Default permissions act as a tenant-wide baseline profile, applying a standard set of permissions to all users in the tenant by default. Administrators can modify the User Default settings to remove certain permissions for everyone, effectively restricting broad access.

Understanding custom roles

To grant more specific or elevated permissions, custom roles are used. These roles allow administrators to selectively assign permissions to individual users or groups, overriding the restrictions set by the User Default role. This approach provides a granular and controlled way to manage access—first by limiting general permissions through the User Default role, and then by granting necessary access only to selected users or groups via custom roles.

Permission hierarchy

Default permissions and custom roles, along with built-in security roles, control user and administrator access at the tenant level. Additionally, space roles control user actions on content within specific spaces. For more information about the different types of roles, see Roles and permissions for users and administrators.

Permission settings

The following sections list the permissions available in the User Default or custom role settings.

For custom roles, you will also have the option to inherit the User Default permission, shown as "User default (permission setting)"—for example, "User default (Not allowed)". This means that the setting in the custom role will match whatever the default is set to.

The "Not allowed" option is only available for the User Default settings because custom roles can’t remove permissions that are already allowed by default.

Permission settings — Content types

The Content types section contains permissions to take action on different content types. These are user permissions.

Permission settings — Features and actions

The Features and actions section contains permissions for tenant-wide access to special features and actions. These are user permissions.

Permission settings — Admin permissions

The Admin permissions section contains permissions for administrators of the Qlik Cloud tenant.

'In-app content download' permission: Additional details

The value assigned to a user for the In-app content download permission can impact their access to other Qlik Cloud features. The following sections breaks down the difference between each of the available options.

No data

The following apply for the No data option:

  • Provides full access to Insight Advisor Chat when it is accessed through Qlik Cloud or an external collaboration platform (for example, Microsoft Teams).

Allowed

The following apply for the Allowed option:

  • Provides full access to Insight Advisor Chat when it is accessed through Qlik Cloud or an external collaboration platform (for example, Microsoft Teams).

Not allowed

The following apply for the Not allowed option:

  • The user will not see static charts in Insight Advisor Chat. The user will also not be able to see any visualizations when using Insight Advisor Chat through a collaboration platform (for example, Microsoft Teams). All other Insight Advisor Chat capabilities, such as natural language insights, will be available.

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 – please let us know!