Home > Appendices > Appendix F - Supported Variable Roles
Download this articleAppendix F - Supported Variable Roles
AvePoint Cloud Governance supports setting variable roles when you select users in approval processes, site collection policies, services, renewal profiles, etc.
NOTE
-
When you specify a user role as the primary contact or secondary contact, one of the group or team owners will be randomly chosen as the primary or secondary contact.
-
In the role name, the character $ and the punctuation () and "" must be entered under the English input method, regardless of whether you select which language as the AvePoint Cloud Governance display language.
The following roles are available, but the roles vary when specifying roles in different fields.
| Role Name | Description |
|---|---|
| $Primary contact | The primary workspace contact that is configured in AvePoint Cloud Governance. |
| $Manager of primary contact | The manager of the primary contact. The manager is configured in Microsoft Entra. |
| $Secondary contact | The secondary workspace contact that is configured in AvePoint Cloud Governance. |
| $Manager of secondary contact | The manager of the secondary contact. The manager is configured in Microsoft Entra. |
| $Primary site collection administrator | The primary site collection administrator that is configured in AvePoint Cloud Governance or SharePoint. |
| $Additional site collection administrators | The users or groups within the SharePoint Site Collection Administrators group, except for the primary site collection administrator. |
| $New contact | The user that takes over the role of contact. |
| $Site collection owners group | The users or groups within the SharePoint Site Collection Owners group. |
| $Users with the Full Control permission | The users who have the Full Control permission to the site collection. |
| $Users with the Edit permission | The users who have the Edit permission to the site collection. |
| $Primary site contact of source | The primary site contact of the source node. |
| $Secondary site contact of source | The secondary site contact of the source node. |
| $Primary site contact of target | The primary site contact of the target node. |
| $Secondary site contact of target | The secondary site contact of the target node. |
| $Group/Team/Power App/Power Automate flow owner or community admin | The owner of a Microsoft 365 Group/Microsoft Team/Power Automate flow, admin of a Viva Engage community, or owner and co-owner of a Power App; they are configured in Microsoft 365, Microsoft Teams, Viva Engage, or AvePoint Cloud Governance. |
| $Community admins | The administrator of a Viva Engage community; it is configured in Viva Engage or AvePoint Cloud Governance. |
| $Source user | The user from whom the permissions will be cloned or transferred. |
| $Manager of source user | The manager of the user from whom the permissions will be cloned or transferred. |
| $Target user | The user to whom the permissions will be cloned or transferred. |
| $Manager of target user | The manager of the user to whom the permissions will be cloned or transferred. |
| $Manager of task approver | The manager of the task approver. |
| $Manager of previous stage approver | The manager of the previous stage’s approver. This role is only available to the second or third stage of approval in an approval process. |
| $Requester | The user who submits a request. |
| $Manager of requester | The manager of the requester. The manager is configured in Microsoft Entra. |
| $Administrator contact | The administrator contact of a service. |
| $Service metadata ("Metadata name") | The Person or group/User Profile Property/Microsoft Entra property metadata that is added to the service with the approval process applied. Make sure the Allow a variable role reference to this metadata in the approval process option enabled on the metadata. The users or groups as the metadata value will be retrieved. Replace Metadata Name with the metadata name. |
| $Object metadata ("Metadata name") | The Person or group/Microsoft Entra property/Lookup metadata that is applied to the object. Make sure the Allow a variable role reference to this metadata in the approval process option is enabled on the metadata. The users or groups as the metadata value will be retrieved. |
| $New object metadata ("Metadata name") | The Person or group/Microsoft Entra property/Lookup metadata that is applied to the object. Make sure the Allow a variable role reference to this metadata in the approval process option is enabled on the metadata. The users or groups as the newly added/changed metadata value will be retrieved. |
| $Site collection metadata ("Metadata name") | The Person or group/User Profile Property/Microsoft Entra property metadata that is applied to the site collection. Make sure the Allow a variable role reference to this metadata in the approval process option is enabled on the metadata. The users or groups as the metadata value will be retrieved. Replace Metadata Name with the metadata name. |
| $Group/Team/Community metadata ("Metadata name") | The Person or group/User Profile Property/Microsoft Entra property metadata that is applied to the group, team, or community. Make sure the Allow a variable role reference to this metadata in the approval process option is enabled on the metadata. The users or groups as the metadata value will be retrieved. Replace Metadata Name with the metadata name. |
| $SharePoint Online Group ("$SiteName Group Name Suffix") | The custom SharePoint Online group. For site-specific groups, use the following format: $SiteName Group Name Suffix. Replace Group Name Suffix with your desired value (i.e. Owners). SiteName will be automatically replaced with the appropriate site title. |
| $Guest inviter | The user who invited the guest user to the tenant. |
| $Task assignee | The users who are specified as the assignees to complete the task. |
| $Task approver | The user who has approved/rejected the task. |
| $Site property ("Property name") | The property value of a site, and it's specified in AvePoint Cloud Governance or ServiceNow. Replace the Property name with the property name in your site property bag. |
| $Private channel owner | The owner of a private channel. It is configured in AvePoint Cloud Governance. |
| $Shared channel owner | The owner of a shared channel. It is configured in AvePoint Cloud Governance. |
| $Team owner | The owner of a Microsoft Team. |
| $Group owner | The owner of a distribution group, security group, or mail-enabled security group. |
| $Shared mailbox member | The members of a shared mailbox. |
| $Power App co-owner | The co-owner of a Power App. |
| $Power App owner | The owner of a Power App. |
| $Power BI workspace member | The member of a Power BI workspace. |
| $Environment admin of Power Automate flow or Power App | The environment admin of a Power Automate flow or Power App. |
| $Object creator | The creator of a Microsoft 365 Group, team, Power App, Power Automate flow, or Power Platform environment. |
| $Manage of object creator | The manager of the role $Object creator when the object admin is a user. |
| $Object admin | The team owner, group owner, community admin, site administrator, Power App owner, Power Automate flow owner, Power BI workspace admin, environment admin, or environment system administrator. |
| $Manager of object admin | The manager of the role $Object admin when the object admin is a user. |
| $Manager of original active contact | The manager of the primary or secondary contact who is no longer active. |
On this page