Using Functional Profiles
Functional profiles group together Security Profiles and Application Roles associated with job functions in Vault CRM. Align operational users can use functional profiles to automate the assignment of permissions to users, enabling quick configuration of Vault CRM features.
For example, the Align operational user needs to manage permissions for a field force containing 500 sales representatives. First, the user creates a functional profile and associates a Security Profile and five application roles to that profile. Then the user assigns the functional profile to the field force. After pushing the data, all fifty users in the field force are assigned the Security Profile and the five application roles.
Who can use this feature?
- Browser Users
- Users require an Align License
- Align Operational Users
Configuring Functional Profiles for

To configure this feature, ensure Configuring Align is complete.
Creating a Functional Profile as

Functional profiles contain the following components:
- CRM Security Profile – Only one CRM Security Profile can be assigned to a functional profile
-
CRM Application Roles – A functional profile can have zero or many CRM application roles assigned to it
Admins can also directly assign CRM Application Roles to individual roster members.
-
CRM Groups – Admins can additionally configure Align to assign CRM groups to functional profiles
To create a functional profile:
- Navigate to the Functional Profiles page in the Align Admin tab.
- Select Create.
-
Populate the Security Profile field with the appropriate Vault CRM Security Profile.
- Select Save.
-
Add all appropriate application roles using the Application Roles related list.
An error displays when pushing to CRM if a Security Profile or application role imported from Vault CRM was deleted in Vault CRM, but is still assigned to an Align-mastered roster member.
-
Add all appropriate CRM groups using the CRM Groups related list, if enabled.
Assigning Functional Profiles as

Functional profiles are assigned to a hierarchy level of a field force. Any roster member assigned to that hierarchy level inherits the Security Profile and application roles defined by the functional profile. This enables Align operational users to quickly assign Security Profiles and application roles to large numbers of users at once.
To assign a field force to a functional profile:
- Navigate to Align Admin > Functional Profiles and select the appropriate functional profile.
- Navigate to the Field Force related list.
- Select Create.
- Select the appropriate field force.
- Select the appropriate hierarchy level.
- Select Save.
Functional profiles can also be assigned using the Functional Profiles related list on the Field Force detail page.
Assigning Functional Profiles to Align Territories
Align territories assigned to a field force automatically inherit the functional profile of the field force. This inherited value displays in the functional_profile__inherited__v field, which cannot be edited. However, Align operational users can manually override this and directly assign a functional profile to an Align territory:
- Navigate to the appropriate aln_territory__v record.
- Populate the aln_functional_profile__v lookup field with the appropriate functional profile.
- Select Save.
The aln_functional_profile__v field always overrides the functional_profile_inherited__v field. To revert back to the inherited functional profile, clear the aln_functional_profile__v field.
Roster Members with Multiple Inherited Functional Profiles
A roster member can inherit multiple functional profiles from assigned Align territories. Roster members with multiple inherited functional profiles receive all application roles defined by all inherited functional profiles. A conflict occurs when a roster member inherits multiple functional profiles where both of the following conditions are met:
- The functional profiles have different values for the following configuration settings:
- Security Profiles
- Application Profiles
- Layout Profiles
- Security Policies
- Overrides for the roster member do not exist for any of the above configuration settings
If this happens, an error occurs when pushing data. Align operational users can prevent this error via the following methods:
- Designate one of the roster member’s territories as a primary territory. This prioritizes the primary territory’s attributes over other territories assigned to the roster member.
- Use the appropriate override lookup field on the appropriate roster member record to manually select the desired configuration setting