There are several options available for exporting security and security policies.
The system Security Policy defines security for the system and for all Root Folders. If you export the System Security Policy and then import the package, the security defined in the destination is replaced with the security contained in the package.
If you export the security properties of the exported objects and then import the package, you import the objects' inheritance setting and the security rows of groups and roles defined on the objects. Inherited security rows are not exported.
Usually you will want to avoid the transfer of irrelevant users from one database to another. If you need to transfer users, you have to explicitly request that security rows of single users be exported. This option controls three security properties that all avoid the transfer of users:
- User permissions - user security rows are exported and users are derived. (only if either of the first two checkboxes are set)
- Owners - the owners of all objects are maintained and all relevant users are derived.
- Group users - all users in User Groups are included and users are derived.
In the following example, exporting this object's security exports only its inheriting setting. Since all of its security rows are inherited, they are not exported.
In the following example, the object's inheriting setting, and the security rows defined on the object itself, the 2 last rows, are exported.
- If you do not want to export the security rows of single users and object users, then only the Application Managers row is exported.
- If you do export the security rows of single users and object users, the John Doe row is exported and the John Doe user is derived.
In the following example, if you export the security rows of single users and objects, John Doe remains the scorecard owner, and the user "Susan Free" is derived.
If you do not export the security rows of single users and objects, Susan Free does NOT remain the scorecard owner. The user that logs in when importing the package becomes the owner of this scorecard.
Security and hierarchy maintain a very strong relationship. If you want to transfer security settings for objects, you must export the hierarchy.
Note: Security settings do not include the parent or any other object besides those selected.