Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content

User permissions

Security roles allow you to grant Qlik Compose users different roles according to the tasks you want them to perform. Qlik Compose comes with the following predefined security roles: Admin, Designer, Operator and Viewer. Each role has its own set of permissions, as described in Default user permissions according to role.

You can associate a user with a security role by adding the user to the appropriate Active Directory group or by assigning a role directly to the user. By default, the user under whose account you install Qlik Compose is an Admin. You can also fine-tune access control per user or group. For more information, see Granular access control

As a user with the relevant permissions, you can view and change the permissions for existing users or groups, or add users or groups that do not yet exist in Qlik Compose.

The advantage of adding groups over users is that you can assign a security role to a group as a whole, instead of to individual users, and any new user that is added to an existing group automatically acquires the security role granted to that group.

To set user permissions using Active Directory groups, you can either create Active Directory groups with the names listed in the table below, or you can create Active Directory groups with different names. Then, add users to the groups according to the role you want them to perform.

If you create your own Active Directory groups, you need to add them to the User Permissions tab in the Settings window and set their permissions as described in Managing user permissions.

Predefined user permission roles
Role Active Directory Group

Administrator

QlikComposeAdmins

Designer

QlikComposeDesigners

Operator

QlikComposeOperators

Viewer

QlikComposeViewers

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!