Home > Configure System Settings > Workspace and Service Management

Export to PDF

Workspace and Service Management

Workspace and service management provides centralized settings to control how workspaces and services are configured, secured, and maintained in AvePoint Cloud Governance. These options allow administrators to manage authentication, notifications, integrations, metadata, reporting, and advanced workspace behaviors to ensure consistent governance and efficient administration across the environment.

Manage API Authentication Profiles

To consume AvePoint Cloud Governance API, you need an access token. An access token can be generated via a client ID and a client secret. To obtain a client ID and a client secret, configure an API authentication profile. To manage API authentication profiles, click the API authentication profiles card on the System settings page and go to the API authentication profiles page.

To create API authentication profiles, click Create on the ribbon, and then configure the following settings:

- **Name** – Enter a name for this API authentication profile. A client ID and a client secret will be generated upon the provisioning of this profile. - **Client** **secret** **duration** – Configure a duration for the client secret. The start time is the profile created time. Enter a number in the text box and select **Days**, **Weeks**, **Months**, or **Years** as the unit. - Choose whether to **Define what services can be called using this Cloud Governance API access token**. With this option enabled, click **Add**, select the services that can be called using this Cloud Governance API access token from the **Add service** panel, and then click **Add** to define the services. You can also delete a service already added to the list by clicking the delete (![Button: Delete](/en/cloud-governance-administrator-guide/configure-system-settings/images/image902.png "Button: Delete")) button.

When you finish, click Save to save all your configurations.

After you click Save, the Note window appears for you to view the API authentication details. Note that the client secret will only be displayed one time, and you cannot retrieve it after you close the window. You can click the copy (Button: Copy) button to copy the client secret to your clipboard.

With the client ID and client secret, you can generate an access token to call the AvePoint Cloud Governance API. For details, see AvePoint Cloud Governance API.

Configure the Administrator Notification

Administrator notification allows you to configure a notification to inform the administrator contact if any service request encounter an error.

To configure administrator notification settings, click the Administrator notification card on the System settings page, and complete the following configurations:

- **Alternate** **administrator** **contact** – Specify a user or group (Microsoft 365 Group, distribution group, security group, or mail-enabled security group) to be an alternate administrator contact in case that the administrator contact is inactive. - **Email** **settings** – You can choose whether to **Notify the** **service** **request** **administrator** **contact when** **the task is assigned** once a task has been assigned to that administrator contact when an error occurs. With the notification enabled, select an email template from the drop-down list for this email notification. - **Duration and** **escalation** – Select the **Enable** **duration and** **escalation** checkbox to notify another administrator contact if an error task has not been handled within the specified amount of time. Make sure that the user receiving the escalated tasks has enough permission to handle all tasks. - **Duration** – Enter a number in the text box for the deadline, and select **Days** or **Weeks** as the time unit for the duration. You can select the **Send a reminder** **email** **to theadministrator contact** **before the task is escalated** checkbox to remind the administrator contact before the error task expires. Select a reminder profile from the drop-down list. You can click the create (![Button: Create](/en/cloud-governance-administrator-guide/configure-system-settings/images/image904.png "Button: Create")) button or go to **Management** > **Profiles & templates** > **Reminder** **profiles** to create a profile reminder profile. For more instructions, refer to [Configure Reminder Profiles](../manage-additional-profiles/configure-reminder-profiles.md). You can also click the refresh (![Button: Refresh](/en/cloud-governance-administrator-guide/configure-system-settings/images/image905.png "Button: Refresh")) button to retrieve the latest available profiles. - **Escalation** – Select the action that the escalation will trigger from the drop-down list. - **Notify** – The specified user will be notified when the task is escalated. Enter the username in the text box. Press **Enter** to check if the name is valid. You can also enter **$** to select the role **$Manager of** **task** **approver**. The manager of the task approver of the task will be notified when the task is escalated. - **Re-assign to** – The task will be re-assigned to the specified users when the task is escalated. Enter the username in the text box. Press **Enter** to check if the name is valid. You can also enter **$** to select the role **$Manager of** **task** **approver**. The task will be reassigned to the manager of the task approver when the task is escalated. - **Email** **template** – Select an email template from the drop-down list.

Click Save to save the configurations.

Manage Archived Team Governance

You can manage the state and related tasks of archived teams. To configure the setting for managing the archived teams, click Archived team governance card on the System settings page, you can choose to turn on or off the Enable archived team governance toggle. Note that the setting only takes effect on teams that have applied modern team renewal profiles.

Click Save to save all your configurations.

Manage Available Services and Questionnaires

You can manage the scope of provisioning services and questionnaires that are available for users when they click Create a workspace. To manage available services/questionnaires, click the Available services/questionnaires card on the System settings page. Then, complete the following steps:

  1. Select one or more services and questionnaires under the various categories, and your selected services and questionnaires will be available after users click Create a workspace. You can click Select all to select all services and questionnaires under each category, as well as click Clear all to deselect all selected services and questionnaires.

    *Note: If there are no available services and questionnaires in this setting, you can go to configure the services and questionnaires in the classic Cloud Governance admin center at first.

  2. Click Save to save your configurations.

Note the following:

- This setting will not take effect when the **Native Microsoft 365** is selected as the workspace provisioning method in **Settings** > **Hub settings** > **Workspace provisioning**. - When there are new services or questionnaires created in Cloud Governance, you can update the configurations if you want the new services/questionnaires to be accessible to your end users.

Configure Bulk Action Confirmation

You can configure to show a confirmation pop-up before executing bulk actions in the Workspace report, highlighting the object count that will be affected by the actions. To configure the bulk action confirmation, click the Bulk action confirmation card on the System settings page.

To enable the bulk action confirmation, turn on the Show a confirmation pop-up with the selected object count before executing action in workspace report toggle, and enter a number as the confirmation threshold. Bulk action confirmations will be shown when the number of affected objects for the action exceed the entered number.

When you finish, click Save to save your configurations.

Manage Categories

You can manage categories which are used to organize services, approval processes, policies, questionnaires, etc., into logical groupings. To manage categories, click the Category management card on the System settings page and go to the Category management page.

To create categories, click Create on the ribbon, and then configure the following settings:

- **Name** – Enter the name of the category that you are about to create. - **Category name mapping** – This allows the category to be displayed as different names in AvePoint Cloud Governance with different display languages. Enter the category names for different languages in the corresponding text boxes. If you do not wish to configure the category name mapping manually, AvePoint Cloud Governance automatically uses the category name specified in step 1 for the category names of all languages. The textboxes will be filled in with the name entered in the **Name** field when your cursor is moved away from the category name. - When you finish, click **Save** to save your configurations. - To define the display order of categories in service requests, click **Define display order** on the ribbon. In the **Define display order** panel, choose one of the following options: - **In alphabetical order** – The categories will be displayed in alphabetical order in requests. - **Sort manually** – Drag the names to manually adjust the display order of categories in requests.

When you finish, click Save to save your configurations.

Configure Channel Settings

To configure whether to allow channels to follow the settings of the policy or profile of their parent teams, click the Channel settings card on the System settings page to open the Channel settings panel. In this panel, you can configure settings for private channels and shared channels.

Select the corresponding checkboxes in the Private channel settings or Shared channel settings section if you want to allow channels to follow the external sharing settings, access settings, or site storage of their parent teams, and click Save to save your configurations.

- Allow private/shared channels to follow the external sharing settings and access settings of policies or profiles applied to their parent teams – By enabling this option, the external sharing settings and access settings of all channels will follow their parent teams’ settings during the following management processes: - Create channel request - Apply profile - Apply policy - Import process - Change policy request - Change profile request - Allow private/shared channels to follow the site storage of policies or profiles applied to their parent teams – With this option enabled, you can select the scope of channels. The external sharing settings, access settings, and site storage of the channels will follow their parent teams’ settings during the following management processes: - Create channel request - Apply profile - Apply policy - Import process - Change storage request - Change policy request - Change profile request

Manage Contact Membership

For site collections, Microsoft 365 Groups, Microsoft Entra groups, teams, Viva Engage communities, guest users, shared mailboxes, and Power BI workspaces managed by AvePoint Cloud Governance, you can now configure the automatic management of the contact membership through the management process in Cloud Governance. To manage the contact membership, click the Contact membership card on the System settings page. In the Contact membership panel, configure the following settings:

- If you want to enable the automatic management of the Microsoft 365 Group contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image906.png "Button: The toggle that is turned on.")) to **Enable Microsoft 365 Group contact membership management**. Then, choose to automatically add primary and secondary contacts as the group owners, members, or both: - **Owners** – The group contacts will be automatically added as the group owners. > ***Note**: Previously, Microsoft 365 Group owners were automatically added as group members. However, with the recent change in Microsoft's guidelines, if your organization sets contacts as owners only, they will no longer be added as group members together. - **Members** – The group contacts will be automatically added as group members. You can decide whether to **Remove original contacts from the group at the same time**. > ***Note**: This setting will take effect on groups during the following Cloud Governance management processes: - Automatic/Manual import - Group provisioning - Change contact - Specify contact - Contact election - Update information in bulk - Renewal - If you want to enable the automatic management of the Microsoft Entra group contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image907.png "Button: The toggle that is turned on.")) to **Enable** **Microsoft Entra** **group** **contact membership management**. Then, choose to automatically add primary and secondary contacts as: - **Owners** – The group contacts will be automatically added as the group owners. - **Members** – The group contacts will be automatically added as group members. You can decide whether to **Remove original contacts from the group at the same time**. Note the following: - This setting will take effect on groups during the following Cloud Governance management processes: - Automatic/Manual import - Group provisioning - Change contact - Specify contact - Contact election - Renewal - This setting will not take effect on hybrid Exchange groups. - If you want to enable the automatic management of the team contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image908.png "Button: The toggle that is turned on.")) to **Enable team contact membership management**. Then, choose to automatically add primary and secondary contacts as: - **Owners** – The team contacts will be automatically added as the team owners. - **Members** – The team contacts will be automatically added as team members. > ***Note**: For teams whose membership is dynamically assigned, this setting does not take effect, and team contact cannot be automatically added as team members. You can decide whether to **Remove original contacts from the** **team** **at the same time**. > ***Note**: This setting will take effect on the team during the following Cloud Governance management processes: - Automatic/Manual import - Team provisioning - Change contact - Specify contact - Contact election - Update information in bulk - Renewal - If you want to enable the automatic management of the community contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image909.png "Button: The toggle that is turned on.")) to **Enable community contact membership management**. Then, choose to automatically add primary and secondary contacts as: - **Owners** – The community contacts will be automatically added as the community owners. - **Members** – The community contacts will be automatically added as the community members. You can decide whether to **Remove original contacts from the** **community** **at the same time**. > ***Note**: This setting will take effect on communities during the following Cloud Governance management processes: - Automatic/Manual import - Community provisioning - Change contact - Specify contact - Contact election - Renewal - If you want to enable the automatic management of the site collection contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image910.png "Button: The toggle that is turned on.")) to **Enable site collection contact membership management**. Then, choose to automatically add primary and secondary contacts as: - **Site collection administrators** – The contacts will be automatically added as site collection administrators. - **Members of a specified SharePoint group** – Specify a SharePoint group using the following format: **$SiteName Group Name**. For example, **$SiteName Owners**. The **SiteName** will be automatically replaced with the appropriate site title. You can decide whether to **Remove original contacts from the** **site collection** **at the same time**. > ***Note**: This setting will take effect on site collections during the following Cloud Governance management processes: - Automatic/Manual import - Site collection provisioning - Change contact - Specify contact - Contact election - Update information in bulk - Renewal - If you want to enable the automatic management of the guest user contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image911.png "Button: The toggle that is turned on.")) to **Enable** **guest user** **manager update**. Then, choose to automatically update the guest user manager when: - **The primary contact specified as the manager is updated** - **The secondary contact specified as the manager is updated** Note the following: - If the secondary guest user contact is also the guest user manager, when there is nobody specified as the secondary contact after contact updating, the guest user manager will be cleared as well. - Enabling this setting will update the guest user manager’s Microsoft Entra property value with the new contact. - If you want to enable the automatic management of the shared mailbox contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image912.png "Button: The toggle that is turned on.")) to **Enable Shared mailbox contact membership management**. With this setting enabled, primary and secondary contacts will be added as shared mailbox members automatically. You can decide whether to **Remove original contacts from the** **shared mailbox** **at the same time**. Note the following: - This setting will take effect on shared mailboxes during the following Cloud Governance management processes: - Automatic/Manual import - Shared mailbox provisioning - Change contact - Specify contact - Contact election - Renewal - This setting will not take effect on hybrid Exchange groups. - If you want to enable the automatic management of the Power BI workspace contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image913.png "Button: The toggle that is turned on.")) to **Enable** **Power BI workspace** **contact membership management**. Then choose to automatically add primary and secondary contacts as: - **Admins** – The workspace contacts will be automatically added as the workspace admins. - **Members** – The workspace contacts will be automatically added as the workspace members. - **Contributors** – The workspace contacts will be automatically added as the workspace contributors. - **Viewers** – The workspace contacts will be automatically added as the workspace viewers. You can decide whether to **Remove original contacts from the workspace at the same time**. > ***Note**: This setting will take effect on Power BI workspaces during the following Cloud Governance management processes: - Automatic/Manual import - Change contact - Specify contact - Contact election - Renewal - If you want to enable the automatic management of the Confide project contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image914.png "Button: The toggle that is turned on.")) to **Enable** **Confide project** **contact membership management**. With this setting enabled, primary and secondary contacts will be added as project admins automatically. > ***Note**: This setting will take effect on Confide projects during the following Cloud Governance management processes: - Confide project provisioning - Renewal - If you want to enable the automatic management of the Loop workspace contact membership, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image915.png "Button: The toggle that is turned on.")) to **Enable** **Loop** **workspace** **contact membership management**. Then choose to automatically add primary and secondary contacts as: - **Owners** – The Loop workspace contacts will be automatically added as the Loop workspace owners. - **Editors** – The Loop workspace contacts will be automatically added as the Loop workspace editors. You can decide whether to **Remove original contacts from the** **Loop** **workspace at the same time**. > ***Note**: This setting will take effect on Loop workspaces during the following Cloud Governance management processes: - Loop workspace provisioning - Renewal

When you finish, click Save to save all your configurations.

Configure Group/Team Advanced Settings

To configure Microsoft 365 Groups or Microsoft Teams advanced settings, such as classification or restriction of the group or team provisioning, click the Group/Team advanced settings card on the System settings page to open the Microsoft 365 Groups/Microsoft Teams advancedsettings panel. Then, configure the following settings in the panel:

- **Tenant** – Select a Microsoft 365 tenant as the scope for groups and teams. > ***Note**: To configure some advanced settings for groups or teams, a specific license may be required in your selected tenant. For detailed requirements, refer to [Manage groups with PowerShell MSOnline](https://docs.microsoft.com/en-us/azure/active-directory/enterprise-users/groups-settings-cmdlets#template-settings). - **Group/Team provisioning restriction** – You can select **Only allow members of a** **Microsoft 365 Group, distribution group, security group, or mail-enabled security group** **to create** **Microsoft** **365 Groups or Microsoft Teams** to restrict group or team provisioning to the members of a group. Enter the name of a group in the text box and select the group from the suggestion list. - **Classification** – Classifications can be used for Microsoft 365 Groups, Microsoft Teams, and SharePoint communication sites. You can perform the following actions to manage classifications: - Add a classification – Click **Add**, and the **Add a classification** window appears. Enter the name and an optional description for the classification. Choose whether to **Set as the default classification**. Click **Save** to save your configurations. - Edit a classification – Click the edit (![Button: Edit](/en/cloud-governance-administrator-guide/configure-system-settings/images/image916.png "Button: Edit")) button under the **Action** column. In the **Edit the classification** window, edit the name or description. Choose whether to **Set as the default classification**. Click **Save** to save your configurations. - Delete a classification – Click the delete (![Button: Delete](/en/cloud-governance-administrator-guide/configure-system-settings/images/image917.png "Button: Delete")) button under the **Action** column to delete the classification. A pop-up window appears asking for your confirmation. Click **OK** to confirm the deletion. - **Blocked words** – You can select **Block specific words in group/team** **names and aliases** to customize your blocked words. Enter your custom blocked words in the text box, and these words are not allowed to be contained in the names and aliases of groups or teams. When a user enters a blocked word in a group/team name or group/team email address, they will see an error message with the blocked word. > ***Note**: Users who fulfill the following administrator roles can create groups or teams using blocked words and with their own naming conventions: - Microsoft 365 Global Administrator - Partner Tier 1 Support - Partner Tier 2 Support - User administrator - Directory writers - **Guest access** – Select one or more of the following options to manage the guest user access to the group/team. - **Allow guest users to be group/team owners** - **Allow guest users to have access to group/team content** – With this checkbox selected, the guest access option **Let guest group members access group content** in the Microsoft 365 admin center > **Org settings** > **Microsoft 365 Groups** will be automatically enabled. - **Allow guest users to be added to groups/teams** – With this checkbox selected, the guest access option **Let** **group owners add people outside your organization to Microsoft 365 Groups as guests** in the Microsoft 365 admin center > **Org settings** > **Microsoft 365 Groups** will be automatically enabled.

When you finish, click Save to save all your configurations.

Configure Impersonation Accounts

AvePoint Cloud Governance uses Microsoft Graph API as the default and recommended method for Microsoft 365 Groups and Microsoft Teams provisioning and management. However, you can choose to use Exchange Web Services API in the classic Cloud Governance admin center if you have the following requirements for group/team management:

- Create groups or teams in multiple domains. - Set the language of the welcome email that Microsoft sends to the group mailbox upon the group/team provisioning. - Send copies of conversations and events to group/team members’ inboxes. - Allow users outside your organization to send emails to groups/teams.

For more details, refer to Appendix H - About Microsoft Graph API (Recommended Method for Microsoft 365 Groups and Microsoft Teams Management) and Appendix I - About Exchange Web Services API.

With impersonation accounts configured, AvePoint Cloud Governance will use the credentials of the impersonation accounts to invoke the Exchange Web Services API and manage groups/teams. To configure impersonation accounts to enable Exchange Web Services API, click the Impersonation account card on the System settings page.

In the Impersonation account panel, turn on the toggle (Button: The toggle that is turned on.) for the tenant that you want to enable the impersonation account, and then configure the following settings:

*Note: To ensure your Microsoft 365 tenant can be retrieved, a Microsoft 365 (All permissions) app profile must be created in AvePoint Online Services > Management > App management.

- **Group/Team provisioning method** – Choose to invoke Microsoft Graph APIs or Exchange Web Services APIs to create groups or teams: - **Microsoft Graph API (recommended)** – Microsoft Graph APIs are the recommended approach unless you need the capabilities that require Exchange Web Services APIs outlined above. With this option selected, AvePoint Cloud Governance will invoke Microsoft Graph APIs to create groups/teams even if you have configured the above impersonation account. Note the following issues that will be caused by Microsoft Graph APIs limitation: - Multiple domains are not supported. AvePoint Cloud Governance will create groups and teams in your default domain. - AvePoint Cloud Governance cannot change the language of the welcome email that Microsoft sends to the group or team mailbox upon the group or team provisioning. The welcome email is in English. If the above scenarios are required, you can choose to invoke Exchange Web Services APIs to create and manage groups or teams to support the above scenarios. - **Exchange Web Services API** – With Exchange Web Services API selected as the group/team provisioning method, select the domain to be used to create groups/teams. With impersonation accounts of multiple domains configured for a tenant, the impersonation account used to invoke Exchange Web Services API will be selected based on the domain you set here. - **The domain set in the requester’s username** – Create a group/team with the domain that corresponds to the requester’s username. - **The domain set in the requester’s primary email address** – Create a group/team with the domain that corresponds to the requester’s primary email address. - **Impersonation account** – To add impersonation accounts, complete the following steps. Note that you can add multiple impersonation accounts for a tenant, but each domain can have only one impersonation account. 1. Click **Add** to open the **Add impersonation account** panel. 2. In the **Add impersonation account** panel, enter the username of a Microsoft 365 user, who has the permission to create groups/teams in Microsoft 365 with an Exchange Online product license assigned. After specifying a user, the domain that the Microsoft 365 user belongs to will be retrieved and displayed here. AvePoint recommends that you configure an impersonation account for each domain if your Microsoft 365 tenant has multiple domains. > ***Note**: If your organization has a restriction on who can create Microsoft 365 Groups within Microsoft 365, which can also be configured in **Settings** > **System settings** > **Microsoft 365 Groups/Microsoft Teams advanced** **settings**, the impersonation account must be a member of the security group that has permission to create Microsoft 365 Groups. For more information about the security group, refer to the Microsoft article [Manage who can create Microsoft 365 Groups](https://support.office.com/en-us/article/manage-who-can-create-office-365-groups-4c46c8cb-17d0-44b5-9776-005fced8e618?ui=en-US&rs=en-US&ad=US). **Default account** – Select a default impersonation account that will be used to invoke Exchange Web Services APIs to create groups/teams. If no impersonation account can be retrieved based on the domain that you set, this default account will be used to invoke Exchange Web Services API. Note the following: - To configure the impersonation account, make sure the custom Azure app that your tenant is using has the Office 365 Exchange Online application permission **full_access_as_app**. - Microsoft limits the number of Microsoft 365 Groups a user can create to 250 groups. The limit for the number of groups an administrator can create is the maximum number of groups a tenant can have. For details, refer to the Microsoft article [Group limits](https://docs.microsoft.com/en-us/office365/admin/create-groups/office-365-groups?view=o365-worldwide#group-limits).

When you finish, click Save to save your configurations.

Configure News and Updates

You can define the news and updates that are shown to end users in the portal. To configure news and updates, click the News & updates card on the System settings page, and complete the following configurations in the News & updates panel:

- **Language** – Select a language and turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image919.png "Button: The toggle that is turned on.")) to enable the language. You can also enable multiple languages. Click the edit (![Button: Edit](/en/cloud-governance-administrator-guide/configure-system-settings/images/image920.png "Button: Edit")) button and configure settings for the message displayed to end users. - **Section title displayed in portal** – Enter the title of the section displayed in the portal. - **Title** – Enter the title of the message. - **Body** – Customize the body for the message. When you finish, click **Save** to save your configurations. - **Default language** – Select a language as the default language displayed to end users. Only the languages that have been enabled (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image921.png "Button: The toggle that is turned on.")) are available to be selected. If a user's Cloud Governance end user portal display language is not one of the enabled options, the news and updates will be shown in the default language. - **Notify end users about news and updates** – Choose whether to notify end users about news and updates. With this option enabled, users can see a red dot on the News and updates (![Button: News and updates](/en/cloud-governance-administrator-guide/configure-system-settings/images/image922.png "Button: News and updates")) button when there is a new message.

When you finish, click Save to save your configurations.

Sync Metadata as Open Extensions

By default, workspace metadata is saved in the workspace-connected site property bag. Open extensions provide an efficient way of retrieving metadata for AvePoint Online Services Auto Discovery and Cloud Governance management processes. For more instructions about open extensions, refer to What are open extensions.

To optimize the performance of retrieving metadata, click the Open extensions configuration card on the System settings page. In the Open extensions configuration page, you can choose to Save metadata in the site property bag and as open extensions to the group resource, then click Save. Note the following if you choose to sync metadata as open extensions to the group resource:

- In AvePoint Online Services > **Scan** **profiles**, make sure the dynamic rule for the custom Groups/Teams/Viva Engage communities container contains **Group** **/** **Team** **/** **Viva Engage** **Community property** **> Cloud Governancemetadata**. For more instructions, refer to [Manage Scan Profiles](https://cdn.avepoint.com/assets/webhelp/avepoint-online-services/index.htm#!Documents/managescanprofiles.htm). - Each open extension can have up to 2 KB of data (including the extension definition itself). Any job syncing metadata larger than 2 KB will fail before writing the data to the group resource. You can download the job report in **Job monitor** to view job details.

If you want to sync existing workspace metadata as open extensions to the group resource and immediately start the sync process, complete the following steps:

  1. Click Add to open the Add metadata panel.

  2. Select one or more metadata and click Add to list.

  3. Note the following:

    • You can add up to 10 metadata to the list.

    • The table below lists the metadata types that can be synced to open extension and how metadata values are stored:

Metadata TypeSample Metadata ValueSample Extension Value
Yes/No (checkbox)Yes1
Yes/No (checkbox)No0
Choice (menu to choose from)ValueValue
Choice (checkbox)Value 1,Value 2Value 1;Value 2
Managed metadata (single value)Term 1Term 1
Managed metadata (multiple values)Term 1,Term 2Term 1;Term 2
Microsoft Entra property (text)ValueValue
Microsoft Entra property (user){User login name}{User login name}
  1. Click Trigger to start the sync process.

Enable Integration with Insights for Renewal Permission Index

Integration with AvePoint Insights will retrieve user and group permissions on demand for newly generated workspace renewal tasks. This integration will ensure the renewal task assignees are always reviewing the latest permissions changes when completing the workspace renewal tasks. To enable integration with Insights, click the Renewal permission index card on the System settings page.

For the tenants that you want to enable the site permission index for workspace renewals with Insights, turn on the toggle (Button: The toggle that is turned on.) for the tenants and click Save when you finish your configuration. With the option enabled, the renewal process will have an updated user experience and additional configuration options available.

Note the following if you want to enable the renewal permission index with Insights:

- Make sure to turn the audit log on in the Microsoft Purview compliance portal for a tenant where you want to enable site permission index integration. For more instructions, refer to [Turn auditing on or off](https://docs.microsoft.com/en-us/microsoft-365/compliance/turn-audit-log-search-on-or-off?view=o365-worldwide). - Make sure an authorized Insights app profile, an app profile for Microsoft 365 with all permissions granted to the app profile, or a custom app profile with all required permissions has been created for a tenant in AvePoint Online Services. Additionally, make sure the API permissions required by AvePoint Insights are contained in the Azure app in a tenant to enable site permission index integration. For details, refer to [Use a Custom Azure App](https://cdn.avepoint.com/assets/webhelp/insights-for-microsoft-365/index.htm#!Documents/useacustomazureapp.htm). - Only workspaces that have renewal profiles applied and with permission renewal and sharing link renewal enabled will be registered with AvePoint Insights. - Depending on the amount of workspaces that have permission renewal enabled, the first index job may take a long time to complete. The **Workspace report** will show the status of each workspace index status in the **Permission index status** column. - If a workspace renewal process was triggered before the workspace was registered with AvePoint Insights, the permission results in the renewal task would be accurate at the time the renewal task was originally generated. - Once the renewal permission index is disabled for a tenant, all ongoing private channel renewal tasks in classic team renewal profiles will be canceled. Private channel renewal is only available with the permission index enabled.

Manage Report Data Retention

By default, AvePoint Cloud Governance retains up to two years of report data displayed in the workspace management timeline and four years of request data displayed in the request report. You can also customize the retention period for report data. If you want to store historical report data older than the retention period, select a storage location to automatically archive the data.

To manage Report data retention management, click the Report data retention management card on the System settings page, and then complete the following configurations:

- **Workspace report** – Configure the retention period and storage location for report data displayed in the workspace management timeline. - **Retention period** – Specify the number of years of the retention period for report data. - Choose whether to **Archive data older than retention period to a storage location**. If you want to manage workspace report data retention, select the **Archive data older than** **retention** **period** **to a storage location** checkbox, and then select a storage location from the drop-down list. You can click **View details** to view the selected location details. For more information about how to configure the storage location, refer to [Configure Report Export Locations](../configure-system-settings/configure-report-export-locations.md). > ***Note**: For renewal tasks completed before February 18, 2022 (insider environment), March 6, 2022 (commercial environment), or March 13, 2022 (U.S. Government environment), the renewal details can only be archived as a JSON file. - **Request report and My tasks** – Configure the retention period and storage location for request data displayed in the request timeline, **Requests** and **My tasks** in AvePoint Cloud Governance Portal. - **Retention period** – Specify the number of years of the retention period for report data. - Choose whether to **Archive data older than retention period to a storage location**. If you want to manage request report data retention, select the **Archive data older than** **retention** **to a storage location** checkbox, and then select a storage location from the drop-down list. You can click **View details** to view the selected location details. For more information about how to configure the storage location, refer to [Configure Report Export Locations](../configure-system-settings/configure-report-export-locations.md). > ***Note**: For renewal tasks completed before February 18, 2022 (insider environment), March 6, 2022 (commercial environment), or March 13, 2022 (U.S. Government environment), the renewal details can only be archived as a JSON file.

When you finish, click Save to save your configurations.

Configure Report Permission Groups

To delegate out the management of workspaces to help balance the management workload, you can share the report in the Cloud Governance admin center to end users by configuring a report permission group and granting specific report permissions to the group. Users in the group can access the report and perform allowed management actions based on applied permissions. To create the group, click the Report permission group card on the System settings page.

To create a report permission group, click Create on the ribbon to open the Create group panel and configure the following settings:

  1. Name – Enter a name for the group.

  2. Description – Enter an optional description for the group.

  3. Group owner – Specify one or more users to be the group owner.

  4. User condition – Configure conditions to dynamically choose what users are included in the group by clicking Add condition. Then, complete the following steps in the Add condition panel:

    1. Select one of the following conditions:

      • Microsoft 365 users/groups – Microsoft 365 users or users in specific Microsoft 365 Groups will be included in the group.

      • Microsoft Entra property – Users whose Microsoft Entra property values match specific values will be included in the group.

    2. Then, configure the Allowed values for the corresponding condition:

      • If you select Microsoft 365 users/groups as the condition, enter the usernames or group names in the text box, and then select your desired one from the suggested values.

      • If you select Microsoft Entra property as the condition, select a Microsoft 365 tenant first. Select from the Built-in properties or Custom properties, and then enter property values in the text box. If you enter multiple values, make sure to separate each value with a semicolon.

    3. Click Save to save your configurations.

    4. You can add multiple conditions to the table. If you add multiple conditions, choose one of the following options to define the logic option for these conditions:

      • Match any single condition – If you choose this option, the users who conform to any of the conditions in the table will be included in the group.

      • Match all conditions – If you choose this option, the users who conform to all conditions in the table will be included in the group.

  5. Report permission – Assign report permissions to the group to determine what actions users can execute by clicking Add permission. Then, complete the following steps in the Add permission panel. Note that a group can have only one permission to a report.

    1. Report – Select a report that users can access.

    2. Report view – Click Add view to select built-in or published views that users can access in the Add view panel, and then click Save to save the configurations.

    3. Allowed action – Select the report actions that users in the group are allowed to execute in the report.

    4. Click Save to save the permissions.

  6. Click Save to save your configurations.

Enable Integration with Sensitivity Labels

You can enable the integration with sensitivity labels for site collections, Microsoft 365 Groups, and Microsoft Teams in your organization that are managed by Cloud Governance. Integration with sensitivity labels will allow the Create Team, Create Group, Create Site Collection, and Create Viva Engage Community services to leverage these labels when a business user submits the request form. To enable the sensitivity label integration, click the Sensitivity labels card on the System settings page.

For the tenants that you want to enable the integration with sensitivity labels, turn on the toggle (Button: The toggle that is turned on.) for the tenants and click Save when you finish your configuration. If you want to enable sensitivity labels, the Microsoft Entra ID Premium license is required in your tenant.

With the sensitivity labels enabled, note the following:

- All published sensitivity labels in your Microsoft 365 tenant will be available for selection when creating service requests and renewal profiles. - Once you enable using sensitivity labels, the external sharing settings in Cloud Governance policies and privacy settings in classic services will honor the sensitivity label settings and not be configurable in associated policies and services/requests. Specifying a Microsoft 365 tenant in the classic admin center site collection policy is not supported. If you have multiple tenants and only enable integration with sensitivity labels for some of them, it will not affect existing site collection policies or services applied for other tenants. If you want to edit those policies and keep external sharing configurations, we recommend that you disable the sensitivity label integration before editing to avoid the impact from sensitivity labels. It is recommended to use site collection external sharing profiles as you can specify what tenants you want to configure external sharing settings for. - To allow Cloud Governance to retrieve external user access and external sharing settings of labels, configure the Cloud Governance for Exchange app and assign it the Compliance Administrator role. Without the configurations, if there is any conflict between the external sharing settings/privacy settings in services requests/renewals and those of the applied sensitivity label, the settings of the sensitivity label will take precedence once applied to a workspace. - If there is a sensitivity label in your tenant that has a parent label, in a Cloud Governance service, the parent label cannot be retrieved to be selected and applied to a workspace, but a sensitivity label’s parent label name will be displayed in a service.

Configure Shared Mailbox Delegate Settings

You can define whether to automatically grant the "Send as" permission to shared mailbox members in shared mailbox related services, renewal, and settings. To configure shared mailbox delegate settings, click the Shared mailbox delegate settings card on the System settings page. Then, you can choose to turn on or off the Automatically grant the "Send as" permission to shared mailbox members toggle.

Click Save to save all your configurations.

Manage Site Information Card

The Site Information Card App allows business users to view governance details and initiate service requests directly within their Microsoft 365 workspace through a redesigned, in-context information card.

Note the following:

- The Site Information Card App is upgraded from the classic Cloud Governance Panel for better functionality. Key enhancements include: - Expanded availability to support the commercial production, Microsoft 365 US Government GCC, Microsoft 365 US Government GCC High, and 21Vianet environments. - Authentication now relies solely on app profiles; the service account is no longer required. - In‑context availability across sites, group team sites, and community sites. Due to the recent Microsoft changes regarding [Azure ACS retirement in Microsoft 365](https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/retirement-announcement-for-azure-acs), the classic Cloud Governance Portal has been fully retired and can no longer be logged into because token-based authentication is no longer supported. We recommend you upgrade the classic app to the modern Site Information Card App to avoid any access disruptions. - See information below for what you can do to utilize the Site Information Card App: - Install Site Information Card App – If your tenant has never installed this app or has not yet upgraded from the classic Cloud Governance Panel App, see the **Install Site Information Card App** section below to deploy and enable it across your sites. - Upgrade to new app version – If your tenant already has this app installed, see instructions on upgrading to a newly released app version in the **Upgrade to New App Version** section below. - The Site Information Card App is not supported on classic team sites or subsites.

To configure what information will be displayed on the Site Information Card App, click the Site Information Card management card on the System settings page. In the Site Information Card management panel, select the information to display for site collections, Microsoft 365 Groups, Microsoft Teams, and Viva Engage communities:

- **Start a request** – With this option selected, the **Service requests** tab will be displayed in the Site Information Card. Choose what services are displayed in the tab: - **All services** – All services can be displayed. - **Specific services** – Selected services can be displayed. Click **Add** to open the **Add service** panel. Select one or more services and click **Add to list**. The selected services will be shown on the table. - **Contacts** – With this option selected, the **Contacts** tab will be displayed in the Site Information Card. Choose the contacts to be displayed in the tab: - **Primary contact** - **Secondary contact** - **Properties** – With this option selected, the **Properties** tab will be displayed in the Site Information Card. Choose one or more properties to be displayed in the tab: - **Policy properties/applied profiles** - **Metadata** - **All metadata** – All metadata can be displayed. - **Specific metadata** – Selected metadata can be displayed. Click **Add** to open the **Add** **metadata** panel. Select one or more metadata and click **Add to list**. The selected metadata will be shown on the table. - **Timeline**

To display all information above in the Site Information Card, select Select all.

Click Save to save your configurations.

Install Site Information Card App

Complete the following steps to install the Site Information Card App:

  1. If your tenant has installed the classic Cloud Governance Panel App, uninstall it first before installing the upgraded Site Information Card App using the following steps. Otherwise, you can go to step 2 directly.

    1. Go to the More features page in the SharePoint admin center and select Open under Apps. The Manage apps page appears.

    2. Select the Cloud Governance Panel App and click Delete on the ribbon.

      *Note: Make sure that you delete the correct app with one of the following product ID:

      • A0B9484F-DB7D-48C1-A074-D702FFECA74F

      • 8142967A-1048-4DC0-A0B1-87E17AC181B1

      If you cannot find the product ID column from the table, click Apps > Add or remove fields in the upper-right corner of the table, select Product ID, and click Apply.

  2. Install the Site Information Card App and approve required permission.

    1. Download the app package via the following links based on the Cloud Governance environment you are using:

      *Note: The product ID of the downloaded app is 8142967A-1048-4DC0-A0B1-87E17AC181B1.

EnvironmentDownload linkVersionReleased Time
Commercial Production EnvironmentModernSitePanelExtension_Commercial.sppkg2.0.0.3January 2026
Microsoft 365 US Government GCC EnvironmentModernSitePanelExtension_GovProd_GCC.sppkg2.0.0.3January 2026
Microsoft 365 US Government GCC High EnvironmentModernSitePanelExtension_GovProd_GCCH.sppkg2.0.0.3January 2026
21Vianet Production EnvironmentModernSitePanelExtension_21v_Prod.sppkg2.0.0.3January 2026
PH Production GCC EnvironmentModernSitePanelExtension_PH_Prod_GCC.sppkg2.0.0.0June 2025
PH Production GCC High EnvironmentModernSitePanelExtension_PH_Prod_GCCH.sppkg2.0.0.0June 2025
2. (Optional) You can customize the Site Information Card icon using the steps below: 1. Prepare an icon in the .png format with recommended dimensions of 20*20 pixels. 2. Open the downloaded app package (.sppkg file) using a file compression tool. 3. Open the **ClientSideAssets** folder and replace the two files that begin with **logo** with the .png file you prepared. Make sure that the file names remain unchanged. 4. Save the modified package. 3. Go to the [More features](https://go.microsoft.com/fwlink/?linkid=2185077) page in the SharePoint admin center and select **Open** under **Apps**. The **Manage apps** page appears. 4. Click **Upload** on the ribbon, select the downloaded app package, and click **Open** to upload the package. 5. After the app is successfully uploaded, the **Enable app** panel appears. 6. Select **Enable this app and add it to all sites** and click **Enable app**. 7. The **Approve access so this app works as designed** panel appears, click **Go to API access page**. 8. In **Pending requests** > **Organization-wide**, select the **cloudgovernance_users_impersonation** permission and click **Approve** on the ribbon.

Upgrade to New App Version

1. Complete the following steps to upgrade to a new app version:
  1. Download the new app package using the download link in the Install Site Information Card App section above. You can optionally customize the Site Information Card icon with instructions in the section.

  2. Upload the new app package and approve required permission.

    1. Go to the More features page in the SharePoint admin center and select Open under Apps. The Manage apps page appears.

    2. Click Upload on the ribbon, select the new app package, and click Open to upload the package.

    3. A window appears reminding that a file with the same name already exists. Click Replace in the window.

    4. After the app is successfully uploaded, the Enable app panel appears.

    5. Select Enable this app and add it to all sites and click Enable app.

    6. The Approve access so this app works as designed panel appears, click Go to API access page.

    7. In Pending requests > Organization-wide, select the cloudgovernance_users_impersonation permission and click Approve on the ribbon.

Configure Site Collection Lock Messages

You can set custom site collection locked messages by configuring the header and/or footer, which will be displayed on modern pages in locked site collections. To customize site collection lock messages, click the Site collection lock messages card. Then, complete the following steps:

  1. Turn on the toggle (Button: The toggle that is turned on.) to Show custom site collection lock messages on locked site collections. Note that make sure the app catalog site collection has already been configured in a tenant. Once configured, AvePoint Cloud Governance will deploy a tenant level app, AvePoint Cloud Governance Customized Site Banner, to the app catalog site collection. For detailed instructions, see Use the site collection app catalog. Then, configure the following settings:

    • Header and footer messages – Customize the header and footer messages to your desired languages by performing the following steps:

      1. Click the edit (Button: Edit) button of your desired languages.

      2. In the Edit message panel, enter the custom content in the text box to customize the header and footer messages that will be displayed on your site collections. You can insert one or more of the following references to be included in the lock messages by clicking Insert reference: Lock reason, Lock time (UTC), Primary contact, Secondary contact, Administrator contact, and Locked by.

      3. Click Save to save the messages.

    • Default language – Select a default language. Only the languages that have been enabled (Button: The toggle that is turned on.) are available to be selected. When SharePoint’s display language is not among any of the eight languages, the header/footer messages will be shown in the default language.

    • Background color of header and footer – There is a default color with the hex triplet in the text box. You can enter the custom hex triplet in the text box, and the header/footer will be displayed in your custom color.

    • Choose whether to Show custom lock messages on the classic site pages. With the checkbox selected, note the following:

      • The footer message is not supported on the classic site pages. The footer message that you configured will be shown in the header as well.

      • The custom background color of the header is not supported on the classic site pages. The default background color is yellow.

  2. Click Save to save all your configurations.

Manage Webhooks

You can configure a webhook to listen for specific events in AvePoint Cloud Governance. AvePoint Cloud Governance will send a request with data to the webhook URL that you specify when an event happens.

For details on how to prepare a webhook URL, see the instructions in How to Integrate Webhooks Into ServiceNow and Add an incoming webhook to a Teams channel as examples.

To configure the webhooks, click the Webhook Management card on the System settings page. Click Create and then configure the following settings:

  1. Name ‒ Enter the name and for the webhook.

  2. Description ‒ Enter an optional description for the webhook.

  3. Webhook URL ‒ Enter the URL of your webhook. AvePoint Cloud Governance will send a request with data to this URL to trigger the webhook.

  4. HTTP header – Add one or more HTTP headers to be sent with the request. Enter a secret token and it will be sent with the request in the X-CloudGovernance-Token HTTP / HTTPS header. Your webhook endpoint can check the token to verify that the request is legitimate.

    To add an HTTP header, click Add custom header, and configure the following information in the Add custom header panel.

    • HTTP Header – Enter the HTTP header.

    • Header value – Enter the HTTP header value.

    • Choose whether to Encrypt sensitive data.

  5. Action execution method ‒ Select a method to execute the actions in AvePoint Cloud Governance.

    • Asynchronous ‒ When you select the asynchronous method, Cloud Governance will continue executing the actions after sending the request to the webhook URL.

    • Synchronous ‒ When you select the synchronous method, Cloud Governance will not continue executing the actions until the custom actions defined in the webhook URL have been completed.

  6. Trigger ‒ Select the AvePoint Cloud Governance events whose occurrence will trigger this webhook.

    • Request related events

      • When a request is submitted

      • When a request is completed

      • When a request is canceled

      • Limit the services that can trigger the webhooks – When you select at least one request-related event, you can choose whether to limit the services that can trigger the webhooks. With this option selected, you can limit Cloud Governance to only send request events for services that are added to the list.

    • Task related events

      • When an approval task is assigned

      • When a request is approved

      • When a request is rejected

      • When an error task is generated

      • When an error task is retried

      • When an error task is skipped

    • Renewal process related events

      • When a renewal task is completed

      • When a renewal process encounters exception

      • When a renewal task is overdue

    • Automated import process related events

      • When an import process with predefined governance details is completed

      • When an end user completes a confirm governance details task

    • Election process related events

      • When an election process is completed or a contact is manually specified

      • When all stages of an election process are overdue

After creating a webhook, you can test the validity of the webhook that you configured. To test the webhook, complete the following steps:

  1. In the Webhook Management list, select a webhook, and then click Test on the ribbon.

  2. In the Test panel, select an event type test your webhook.

  3. Click Test trigger a test for your webhook immediately.

You can also configure anomaly monitoring of the webhook that you configured. To configure anomaly monitoring for the webhook, complete the following steps:

  1. In the Webhook Management list, select a webhook, and then click Anomaly monitoring on the ribbon.

  2. In the Anomaly monitoring panel, specify the number of times for communication failures to automatically stop sending messages to the webhook URL.

  3. Choose whether to Send an email notification.

  4. Click Save to save the configurations.

After you configure a webhook, when the event occurs in Cloud Governance, your webhook endpoint will receive the event relevant data returned by Cloud Governance. Refer to the tables in the sections below for detailed information about the data.

When a Request is Submitted

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a request is submitted in Cloud Governance.StringRequestSubmitted
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:20:03Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to create a site collection.
ServiceTypeThe type of the service that is used to submit this request.StringCreate Site Collection
RequestIdThe ticket number of the request.Int322155
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
ServiceNameThe name of the service that is used to submit this request.StringCreate Site Collection Service
ServiceIdThe unique ID of the service that is used to submit this request.Guidb3e20d7d-e770-4382-a290-f157b346eb21

When a Request is Completed

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a submitted request is completed in Cloud Governance.StringRequestCompleted
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:20:03Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to create a site collection.
ServiceTypeThe type of the service that is used to submit this request.StringCreate Site Collection
RequestIdThe ticket number of the request.Int322155
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
ServiceNameThe name of the service that is used to submit this request.StringCreate Site Collection Service
ServiceIdThe unique ID of the service that is used to submit this request.Guidb3e20d7d-e770-4382-a290-f157b346eb21

When a Request is Canceled

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a submitted request is canceled in Cloud Governance.StringRequestCancelled
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:20:03Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to create a site collection.
ServiceTypeThe type of service that is used to submit this request.StringCreate Site Collection
RequestIdThe ticket number of the request.Int322155
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
ServiceNameThe name of the service that is used to submit this request.StringCreate Site Collection Service
ServiceIdThe unique ID of the service that is used to submit this request.Guidb3e20d7d-e770-4382-a290-f157b346eb21

When an Approval Task is Assigned

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when an approval task is assigned in Cloud Governance.StringTaskCreated
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:20:03Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to create a site collection.
ServiceTypeThe type of service that is used to submit this request.StringCreate Site Collection
RequestIdThe ticket number of the request.Int322155
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
MessageNot ApplicableString
AssigneeDisplayNameThe display name of the task assignee.StringAlex Wilber
AssigneeIdentityNameThe user principal name of the task assignee.StringAlexW@contoso.com
TaskIdThe unique ID of the task.Guidbe28f54-0f6f-48be-ad2c-515aed7272d5
TaskLinkThe link of the task.Stringhttps://myhub.avepointonlineservices.com /#/tasks/filters?batchId=abe28f54-0f6f-48be-ad2c-515aed7272d5

When a Request is Approved

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a submitted request is approved.StringTaskApproved
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to create a site collection.
ServiceTypeThe type of service that is used to submit this request.StringCreate Site Collection
RequestIdThe ticket number of the request.Int322215
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
MessageNot ApplicableString
AssigneeDisplayNameThe display name of the task assignee.StringAlex Wilber
AssigneeIdentityNameThe user principal name of the task assignee.StringAlexW@contoso.com
TaskIdThe unique ID of the task.Guidbe28f54-0f6f-48be-ad2c-515aed7272d5
TaskLinkThe link of the task.Stringhttps://myhub.avepointonlineservices.com /#/tasks/filters?batchId=abe28f54-0f6f-48be-ad2c-515aed7272d5
ApproverDisplayNameThe display name of the approver.StringAlex Wilber
ApproverIdentityNameThe user principal name of the approver.StringAlexW@contoso.com

When a Request is Rejected

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a request is rejected.StringTaskRejected
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to change the site collection contacts.
ServiceTypeThe type of service that is used to submit this request.StringChange Site Collection Contact or Administrator
RequestIdThe ticket number of the request.Int322155
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
MessageThe approver’s comment.StringI do not agree to change the site collection contacts.
AssigneeDisplayNameThe display name of the task assignee.StringAlex Wilber
AssigneeIdentityNameThe user principal name of the task assignee.StringAlexW@contoso.com
TaskIdThe unique ID of the task.Guidbe28f54-0f6f-48be-ad2c-515aed7272d5
TaskLinkThe link of the task.Stringhttps://myhub.avepointonlineservices.com/#/tasks/filters?batchId=abe28f54-0f6f-48be-ad2c-515aed7272d5
ApproverDisplayNameThe display name of the approver.StringAlex Wilber
ApproverIdentityNameThe user principal name of the approver.StringAlexW@contoso.com

When an Error Task is Generated

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when an error task is generated.StringErrorTaskCreated
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:20:03Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to create a site collection.
ServiceTypeThe type of service that is used to submit this request.StringCreate Site Collection
RequestIdThe ticket number of the request.Int322155
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
MessageThe error details of the error task.StringCannot find the assignee. The user does not exist or is disabled.
AssigneeDisplayNameThe display name of the task assignee.StringMegan Bowen
AssigneeIdentityNameThe user principal name of the task assignee.StringMeganB@contoso.com
TaskIdThe unique ID of the error task.Guidbe28f54-0f6f-48be-ad2c-515aed7272d5
TaskLinkThe link of the error task.Stringhttps://myhub.avepointonlineservices.com/#/tasks/filters?batchId=abe28f54-0f6f-48be-ad2c-515aed7272d5

When an Error Task is Retried

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when an error task is retried.StringTaskRetried
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to create a site collection.
ServiceTypeThe type of service that is used to submit this request.StringCreate Site Collection
RequestIdThe ticket number of the request.Int322155
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
MessageNot ApplicableString
AssigneeDisplayNameThe display name of the task assignee.StringAlex Wilber
AssigneeIdentityNameThe user principal name of the task assignee.StringAlexW@contoso.com
TaskIdThe unique ID of the task.Guidbe28f54-0f6f-48be-ad2c-515aed7272d5
TaskLinkThe link of the task.Stringhttps://myhub.avepointonlineservices.com/#/tasks/filters?batchId=abe28f54-0f6f-48be-ad2c-515aed7272d5
ApproverDisplayNameThe display name of the approver.StringAlex Wilber
ApproverIdentityNameThe user principal name of the approver.StringAlexW@contoso.com

When an Error Task is Skipped

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when an error task is skipped.StringTaskSkipped
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace that is requested to be managed.Stringhttps://contoso.com/sites/marketing
SummaryThe request summary.StringI submit this request to create a site collection.
ServiceTypeThe type of service that is used to submit this request.StringCreate Site Collection
RequestIdThe ticket number of the request.Int322155
RequestGuidThe unique ID of the request.Guide3b273a1-3838-4470-a0d4-f84f6c4a3dda
RequesterThe display name of the requester.StringMegan Bowen
RequesterIdentityNameThe user principal name of the requester.StringMeganB@contoso.com
MessageNot ApplicableString
AssigneeDisplayNameThe display name of the task assignee.StringAlex Wilber
AssigneeIdentityNameThe user principal name of the task assignee.StringAlexW@contoso.com
TaskIdThe unique ID of the task.Guidbe28f54-0f6f-48be-ad2c-515aed7272d5
TaskLinkThe link of the task.Stringhttps://myhub.avepointonlineservices.com/#/tasks/filters?batchId=abe28f54-0f6f-48be-ad2c-515aed7272d5
ApproverDisplayNameThe display name of the approver.StringAlex Wilber
ApproverIdentityNameThe user principal name of the approver.StringAlexW@contoso.com

When the Workspace Reaches the Inactivity Threshold

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a workspace reaches its inactivity threshold.StringLifecycleInactiveTaskCreated
TaskTypeThe type of the task.StringGroupInactivityThreshold
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
ObjectTypeThe type of the workspace.StringMicrosoft 365 Group
ObjectIdThe unique ID of the workspace.Guid379ff54e-b062-40ea-bceb-a6f13c50a054
ObjectTitleThe name of the workspace.StringMarketing
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com
TaskLinkThe link of the inactivity threshold task.String
ReachedTimeThe time that the workspace inactivity threshold reaches.DateTime2020-09-04T02:31:26Z
PolicyIdThe ID of the policy.Guid81bbf505-0718-4c6a-a25a-170a03346ea8
PolicyNameThe name of the policy.StringGroupPolicy
AssigneeThe username of the task assignee.StringMeganB@contoso.com

When the Workspace Lease Expires

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when the workspace lease expires.StringLifecycleLeaseTaskCreated
TaskTypeThe type of the task.StringGroupExpired
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
ObjectTypeThe type of the workspace.StringMicrosoft 365 Group
ObjectIdThe unique ID of the workspace.Guid379ff54e-b062-40ea-bceb-a6f13c50a054
ObjectTitleThe name of the workspace.StringMarketing
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com
TaskLinkThe link of the lease expiration task.String
ReachedTimeThe time that the workspace lease expires.DateTime2020-09-04T02:31:26Z
PolicyIdThe ID of the policy.Guid81bbf505-0718-4c6a-a25a-170a03346ea8
PolicyNameThe name of the policy.StringGroupPolicy
AssigneeThe username of the task assignee.StringMeganB@contoso.com

When a Renewal Task is Completed

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a renewal task is completed.StringRenewalSuccess
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
SummaryNot ApplicableString
RenewalProfileIdThe unique ID of the renewal profile.Guid66bfab5a-e8e4-42b6-9103-310bdb1de894
RenewalProfileNameThe name of the renewal profile.StringRenewal profile for groups
TaskLinkNot ApplicableString
ObjectTypeThe type of the workspace.StringMicrosoft 365 Group
ObjectIdThe unique ID of the workspace.Guide15ff8a8-3fa1-473e-bee6-f1ea40e3cccb
ObjectTitleThe name of the workspace.StringMarketing
PhaseStartTimeThe start time of the renewal process.DateTime2020-09-04T03:03:53Z
DueDateNot ApplicableDateTime
AssigneeDisplayNameNot ApplicableString
AssigneeIdentityNameNot ApplicableString
MessageNot ApplicableString
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com

When a Renewal Process Encounters an Exception

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a renewal process encounters an exception.StringRenewalException
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
SummaryNot ApplicableString
RenewalProfileIdThe unique ID of the renewal profile.Guidd0e829dc-6c0b-448d-b110-f78e47d84220
RenewalProfileNameThe name of the renewal profile.StringRenewal profile for teams
TaskLinkThe link of the renewal task.Stringhttps://myhub.avepointonlineservices.com/#/tasks/filters?ObjectId=1f5b4fe6-6485-420c-becb-335c0510bc91&Type=61
ObjectTypeThe type of the workspace.StringMicrosoft Team
ObjectIdThe unique ID of the workspace.Guid379ff54e-b062-40ea-bceb-a6f13c50a054
ObjectTitleThe name of the workspace.StringMarketing
PhaseStartTimeThe start time of the renewal process.DateTime2020-09-04T03:03:53Z
DueDateThe due date of the renewal process.DateTime2020-09-12T03:03:53Z
AssigneeDisplayNameThe display name of the renewal task assignee.StringMegan Bowen
AssigneeIdentityNameThe user principal name of the renewal task assignee.StringMeganB@contoso.com
MessageThe details of the renewal exception.StringThe following users cannot be found in your organization’s directory: AlexW@contoso.com
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com

When a Renewal Task is Overdue

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when a renewal task is overdue.StringRenewalOverdue
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
SummaryNot ApplicableString
RenewalProfileIdThe unique ID of the renewal profile.Guid66bfab5a-e8e4-42b6-9103-310bdb1de894
RenewalProfileNameThe name of the renewal profile.StringRenewal profile for groups
TaskLinkThe link of the renewal task.Stringhttps://myhub.avepointonlineservices.com/#/tasks/filters?ObjectId=1f5b4fe6-6485-420c-becb-335c0510bc91&Type=61
ObjectTypeThe type of the workspace.StringMicrosoft 365 Group
ObjectIdThe unique ID of the workspace.Guide15ff8a8-3fa1-473e-bee6-f1ea40e3cccb
ObjectTitleThe name of the workspace.StringMarketing
PhaseStartTimeThe start time of the renewal process.DateTime2020-09-04T03:03:53Z
DueDateThe due date for the task assignee to complete the renewal task.DateTime2020-09-12T03:03:53Z
AssigneeDisplayNameThe display name of the renewal task assignee.StringMegan Bowen
AssigneeIdentityNameThe user principal name of the renewal task assignee.StringMeganB@contoso.com
MessageNot ApplicableString
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com

When an Import Process with Predefined Governance Details is Completed

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when an import process with predefined governance details is completed.StringFullyAutoImportSuccess
TriggerTimeThe time that the renewal task is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
SummaryNot ApplicableString
AutoImportProfileIdThe unique ID of the import job.Guid7c8a50ba-31f8-4740-866f-69b8dbcb95a6
AutoImportProfileNameThe name of the import job.StringAutomatic import for groups
TaskLinkNot ApplicableString
ObjectTypeThe type of the workspace.StringMicrosoft 365 Group
ObjectIdThe unique ID of the workspace.Guid4ae8dea3-f79a-4de0-8392-84058f9ee37d
ObjectTitleThe name of the workspace.StringMarketing
MessageNot ApplicableString
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com

When an End User Completes a Confirm Governance Details Task

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when an end user completes a confirm governance details task.StringConfirmDetailSuccess
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
SummaryNot ApplicableString
AutoImportProfileIdThe unique ID of the import job.Guid7c8a50ba-31f8-4740-866f-69b8dbcb95a6
AutoImportProfileNameThe name of the import job.StringAutomatic import for groups
TaskLinkNot ApplicableString
ObjectTypeThe type of the workspace.StringMicrosoft 365 Group
ObjectIdThe unique ID of the workspace.Guid4ae8dea3-f79a-4de0-8392-84058f9ee37d
ObjectTitleThe name of the workspace.StringMarketing
MessageNot ApplicableString
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com

When an Election Process is Completed or a Contact is Manually Specified

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when an election process is completed or when a contact is manually specified.StringElectionCompleted
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
ObjectTypeThe type of the workspace.StringMicrosoft 365 Group
ObjectIdThe unique ID of the workspace.Guid4ae8dea3-f79a-4de0-8392-84058f9ee37d
ObjectTitleThe name of the workspace.StringMarketing
ServiceTypeThe type of service.GuidSpecify contact
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com
IsPrimaryContactDeactivedIf the primary workspace contact is deactivated.BooleanFALSE
OriginalPrimaryContactThe display name of the original primary workspace contact.StringMegan Bowen
OriginalPrimaryContactIdentityNameThe user principal name of the original primary workspace contact.StringMeganB@contoso.com
IsPrimaryContactChangedIf the primary workspace contact is changed.BooleanFALSE
NewPrimaryContactThe display name of the new primary workspace contact.StringAlex Wilber
NewPrimaryContactIdentityNameThe user principal name of the new primary workspace contact.StringAlexW@contoso.com
IsSecondaryContactDeactivedIf the secondary workspace contact is deactivated.BooleanTRUE
OriginalSecondaryContactThe display name of the original secondary workspace contact.StringAlex Wilber
OriginalSecondaryContactIdentityNameThe user principal name of the original secondary workspace contact.StringAlexW@contoso.com
IsSecondaryContactChangedIf the secondary workspace contact is changed.BooleanTRUE
NewSecondaryContactThe display name of the new secondary workspace contact.StringMegan Bowen
NewSecondaryContactIdentityNameThe user principal name of the new secondary workspace contact.StringMeganB@contoso.com

When All Stages of an Election Process are Overdue

PropertyDescriptionTypeSample Data
TriggerTypeThis webhook will be triggered when all stages of an election process are overdue.StringElectionOverdue
TriggerTimeThe time that the webhook is triggered.DateTime2020-09-04T02:31:26Z
ObjectUrlThe URL of the workspace.Stringhttps://contoso.com/sites/marketing
ObjectTypeThe type of the workspace.StringMicrosoft Team
ObjectIdThe unique ID of the workspace.Guid4ae8dea3-f79a-4de0-8392-84058f9ee37d
ObjectTitleThe name of the workspace.StringMarketing
ServiceTypeThe type of service.GuidSpecify contact
GroupEmailThe email address of the workspace.Stringmarketing@contoso.com
IsPrimaryContactDeactivedIf the primary workspace contact is deactivated.BooleanFALSE
OriginalPrimaryContactThe display name of the original primary workspace contact.StringMegan Bowen
OriginalPrimaryContactIdentityNameThe user principal name of the original primary workspace contact.StringMeganB@contoso.com
IsPrimaryContactChangedIf the primary workspace contact is changed.BooleanFALSE
NewPrimaryContactThe display name of the new primary workspace contact.StringAlex Wilber
NewPrimaryContactIdentityNameThe user principal name of the new primary workspace contact.StringAlexW@contoso.com
IsSecondaryContactDeactivedIf the secondary workspace contact is deactivated.BooleanTRUE
OriginalSecondaryContactThe display name of the original secondary workspace contact.StringAlex Wilber
OriginalSecondaryContactIdentityNameThe user principal name of the original secondary workspace contact.StringAlexW@contoso.com
IsSecondaryContactChangedIf the secondary workspace contact is changed.BooleanTRUE
NewSecondaryContactThe display name of the new secondary workspace contact.StringMegan Bowen
NewSecondaryContactIdentityNameThe user principal name of the new secondary workspace contact.StringMeganB@contoso.com

Configure Workspace Type Conversion

You can configure whether to automatically apply new profiles when converting an object type from Microsoft 365 Group to Team, or from Site collection to Microsoft 365 Group. To configure the workspace type conversion, click the Workspace type conversion card on the System settings page. In the Workspace type conversion panel, configure the following settings:

- If you want to enable the automatic map profiles from Microsoft 365 Group to Microsoft Teams, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image928.png "Button: The toggle that is turned on.")) to enable **Auto map profiles from Microsoft 365 Group to Microsoft Teams**. Then, choose to add the profile mappings from the following: - Contact election profile mapping Click **Add** to open the **Add contact election profile mapping** panel, select one or more Microsoft 365 Group profiles and choose the target team profiles to match to. Click **Add to list**. The selected mappings will be shown on the table. - External sharing profile mapping Click **Add** to open the **Add** **external** **election profile mapping** panel, select one or more Microsoft 365 Group profiles and choose the target team profiles to match to. Click **Add to list**. The selected mappings will be shown on the table. - Renewal profile mapping Click **Add** to open the **Add** **renewal** **profile mapping** panel, select one or more Microsoft 365 Group profiles and choose the target team profiles to match to. Click **Add to list**. The selected mappings will be shown on the table. - Storage management profile mapping Click **Add** to open the **Add** **storage management** **profile mapping** panel, select one or more Microsoft 365 Group profiles and choose the target team profiles to match to. Click **Add to list**. The selected mappings will be shown on the table. - If you want to enable the automatic map profiles from site collection to Microsoft 365 Group, turn on the toggle (![Button: The toggle that is turned on.](/en/cloud-governance-administrator-guide/configure-system-settings/images/image929.png "Button: The toggle that is turned on.")) to enable **Auto map profiles from** **site collection to** **Microsoft 365 Group**. Then, choose to add the profile mappings from the following: - Contact election profile mapping Click **Add** to open the **Add** **contact election profile mapping** panel, select one or more site collection profiles and choose the target Microsoft 365 Group profiles to match to. Click **Add to list**. The selected mappings will be shown on the table. - External sharing profile mapping Click **Add** to open the **Add** **external** **election profile mapping** panel, select one or more site collection profiles and choose the target Microsoft 365 Group profiles to match to. Click **Add to list**. The selected mappings will be shown on the table. - Renewal profile mapping Click **Add** to open the **Add** **renewal** **profile mapping** panel, select one or more site collection profiles and choose the target Microsoft 365 Group profiles to match to. Click **Add to list**. The selected mappings will be shown on the table. - Storage management profile mapping Click **Add** to open the **Add** **storage management** **profile mapping** panel, select one or more site collection profiles and choose the target Microsoft 365 Group profiles to match to. Click **Add to list**. The selected mappings will be shown on the table. - **Keep existing site storage limit** – You can choose to keep the existing site storage limit if you have specified a site storage for the selected profile.

Click Save to save your configuration.