Deployment Step: Full Profiles

Updated 20 hours ago by David Venegas

This article is part of the Deployment Steps.

The Full Profiles deployment step allows you to deploy a profile with all its properties from one Org to another using the Metadata API.

The term “Full” Profiles is due to Copado doing a full describe of your org, to make sure that every single property of the profile is included in the deployment. Profile properties include User Permissions, Field Level Security, Object Level Security, Tab Visibility, RecordType Visibility, Layout Assignments and more.

During the deployment, profiles are automatically cleaned by removing any components that do not exist in the destination Org (by retrying) and preventing the deployment to fail. The engine retries until it either gets a successful deployment or gives up after 100 retries.

To deploy specific properties of a profile, and not the entire profile, you can use the Metadata Step where the specific properties of a profile that get deployed will be relative to the set of metadata included in the same step (e.g. custom fields, custom objects, record types, layouts, etc).
Some limitations are imposed by the API, for example Tab settings are not deployable. For more details, please review the Metadata API documentation.


How did we do?