Migrating users, groups, rules, and user allocations

Users and groups

• User definitions are added to the tenant as users log in.

  • Prepopulate if you need to assign space permissions (by user) before users log in for the first time.

  • Prepopulate Users using CLI script 1_setusers.ps1

• Group definitions are added to the tenant as users log in.

Administrative roles

Identify and assign users and groups to admin/user roles. In most cases you want users to have the same roles as before, and so you can create a list that maps the users to a role similar to what they had in Qlik Sense Enterprise on Windows.

Mapping roles in Qlik Sense Client-Managed to Qlik Cloud

This is the recommended mapping of roles in Qlik Sense Client-Managed to roles in Qlik Cloud. Use the Roles tab in the Migration Worksheet for planning help.

• Content Admin > Analytics Admin

• Deployment Admin > Tenant Admin

• Root Admin > Tenant Admin

• Security Admin > Tenant Admin

• Audit Admin > Audit Admin

• Custom roles > Qlik Cloud roles and permissions

Additional roles

The following roles are not admin roles, but roles assigned to users who need permission to create shared, managed, or data spaces, or generate API keys. You can have more than one of these roles.

• Shared space creator: can create shared spaces

  • Project team users, Collaborators, BI Admins, Developers

• Managed space creator: can create managed spaces

  • BI Admins, IT

• Data space creator: can create data spaces

• Developer: can generate API keys

Security rules in Qlik Sense Client-Managed

Use the Security Rules tab in the Migration Worksheet for planning help.

1. Look through your Qlik Sense Client-Managed security rules, and note any groups used. The worksheet shows mapping from default rules to Qlik Cloud.

2. Note custom rules and define the business process around these.

3. Note the groups all of these rules are using as they will be used in Qlik Cloud.