/
How are permission schemes migrated?

How are permission schemes migrated?

The Default Permission Scheme is only migrated on the first migration.

Suggestions

After a permission scheme is migrated, we suggest to:

  1. Not rename this scheme.

  2. Not modify any of its permissions.

 

These 3 Projectrak permissions share the same configuration between Server/Datacenter and Cloud, which provide the ability to associate a layout with a project and view and edit Projectrak fields’ values.

None of these permissions will be lost during migration from Server/DC to Cloud, they will be accumulated instead. This means that some users might have more permissions than expected, so please, review the following cases carefully:

  • Initial state - Server/DC has the following “Default permission scheme” associated to Project A:

  • First migration - project A and permission scheme “Default permission scheme” are created in Cloud, being associated to each other.

  • User actions - Cloud “Default permission scheme” is renamed to “Support scheme” and the new group “developers” is added to the “View project values” permission:

     

  • Second migration - the permissions will be accumulated in Cloud “Support scheme”, as you can see in the screenshot below:

This permission is only present on Server/DC, therefore it will not be migrated.



Related content

How do Projectrak fields behave on migrations?
How do Projectrak fields behave on migrations?
Read with this
How are Projectrak layouts migrated?
How are Projectrak layouts migrated?
Read with this
How are field visibility restrictions migrated?
How are field visibility restrictions migrated?
Read with this
Migration to Cloud
Migration to Cloud
Read with this
How are Projectrak global permissions migrated?
How are Projectrak global permissions migrated?
Read with this
Migration to Cloud
Migration to Cloud
Read with this