Start a conversation

How does migrating from QPP NextGen 2.x to 3.x impact the licenses and privileges?

Product: Quark Publishing Platform (QPP) NextGen

System Admin (default user)

QPP NextGen has one default or system-defined user called the System Admin (User ID = 1).
Pre-migration: There are only two licenses, Author and Access (Docurated in 3.x), and the System Admin has the Author license.
Post migration: The System Admin has the Admin license and the default Administrator role (who has all the privileges). There can be several users with the Administrator role and Admin license.

Roles not associated to any user or group in 2.x

Roles that are not associated with any user or group in 2.x do not have a license associated with them. During migration, you see the field Select License Type in which you can assign the license to a role as required.
 Roles associated to a user in 2.x:
License assigned to a role in 2.x License assigned to the same role in 3.x on migration
Author Author
Access Docurated
Author and Access Docurated (based on the lowest in the license hierarchy*)

* Lowest in the license hierarchy means the license that has the least number of privileges.

License Hierarchy:
  1. Admin (most/all privileges)
  2. Author
  3. Contributor
  4. Consumer (least privileges)
Roles associated to a group in 2.x:
The license is assigned based on the user in the group whose license is the lowest in the hierarchy.
For example, on 2.x the role X is associated with a group with two users – U1 and U2. U1 has the Author license and role Y. U2 has the Access (Docurated) license with role Z. On migration to 3.x, the role X is assigned the Docurated license.

Note: To change the license assigned to a role (associated to a group), as an administrator, you first must remove the users from the group who have licenses that are lower in the hierarchy from the license you want to assign to the role.
 
Demote and remove user license in 3.x:
  • An administrator can demote a user’s license when the user is not part of a group that has a role with a higher license in the license hierarchy. In such cases, the administrator can only demote the user’s license by first removing the user from the concerned group.
  • An administrator can keep or add a user without assigning a license by first assigning the role with no privileges to the user. However, if the user is already part of a group with an associated role, the administrator must first remove the user from the group.
 
Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments