Preserve Delegated Developer permissions

[Ole Kirkegard]

How to best preserve delegated developer permissions configured in sub-prod environments such as e.g. DEV,  so that when performing a clone of PROD down over the DEV environment. The delegated groups or individual developer associated permissions are retained and doesn't need to be reconfigured?

Does anyone have experience and/or recommendation how to preserve these configurations in sub-prod instances. maybe identified the table for which to create Data Preservers for the respective clone profiles or other suggestions?

[lauri457]

The following tables are used to store the information on collaborators and permissions. I suppose if you are only using delegated development then you'd want to preserve and exclude the three tables and make sure that the dd roles and role assignments are cloned. For app collaboration the tables have oob preservers in the default clone profile.

App collaboration:
sys_appcollab_descriptor [descriptor of permission collection]

sys_appcollab_user [links user and assigner to descriptor and app]

sys_appcollab_group [links group and assigner to descriptor and app]

sys_appcollab_permission_m2m [links set of permissions to descriptor]

Delegated development:

sys_development_permission_set [set of resources grouped together]

sys_development_permission [individual resource]

sys_scope_permission_set_role_assignment [links dd role to a set of permissions and scope]

sys_user_role [dd roles]

sys_user_has_role [users with dd roles]

[Ole Kirkegard]

Thank you, I was looking at the mentioned tables for Delegated Development. Excluding and preserving these tables is this something you have have setup yourself and thereby can confirm is in fact working?

Thing is we only delegate on the applications in DEV environment and therefore the delegation is not configured in the PROD instance. We need to be able to segregate developer access between the environments. 🙂