Home > Configure Hub Settings
Export to PDFYou can update the AvePoint Cloud Governance Portal to integrate with hub functionality to provide more productivity features to your end users. End users will be able to view, access, organize, and manage workspaces, including Microsoft 365 Groups, Microsoft Teams, Viva Engage communities, and SharePoint sites in a more centralized and efficient way.
To update AvePoint Cloud Governance Portal to integrate with hubs functionality, enable hubs in the Hub settings first.

Before your end users can use hubs, you must create app profiles for MyHub and use a Microsoft 365 global administrator account to accept the permissions requested by hubs functionality. For details, refer to Manage App Profiles.
When you enable hubs for the first time, end users must sign out of the Cloud Governance Portal and sign in again to view hubs.
You can select a method for your end users to create Microsoft 365 Groups, Microsoft Teams, and SharePoint sites in hubs by completing the following steps:
Click Workspace management, and the Workspace management panel appears.
In the Workspace provisioning section, select one of the following options as the workspace provisioning method:
AvePoint Cloud Governance – Hub users will create Microsoft 365 Groups, Microsoft Teams, or SharePoint sites via AvePoint Cloud Governance service requests. When users choose to Create a workspace in a hub, they will be directed to the New request page to submit a Cloud Governance service request.
Native Microsoft 365 – Hub users will create Microsoft 365 Groups, Microsoft Teams, or SharePoint sites in native Microsoft 365 styles. When users choose to Create a workspace in a hub, a Create a workspace panel will appear, and users can provide the new workspace information in the panel.
When you finish, click Save to save your choice.
You can choose whether to allow your end users to delete workspaces when they access the workspace details via a hub.
To configure this setting, you can click the AvePoint Online Services > MyHub general settings link to configure this setting in the MyHub admin center. For details, refer to Spaces Report Settings.
You can choose whether to allow your end users to discover and manage specific types of workspaces in the default hubs and their customized hubs. If the discovery and management of specific types of workspaces is disabled, your end users will not be able to view or manage these types of workspaces in hubs. The Workspace discovery settings do not affect the discovery and management of workspaces in shared hubs.
Click Workspace discovery, and the Workspace discovery panel appears.
You can enable (
) or disable (
) the discovery and management for workspaces. It is disabled by default.
Microsoft 365 Groups/Microsoft Teams/Viva Engage Communities – With the discovery and management enabled, users can see all groups/teams/communities that they have access to.
SharePoint Sites – With the discovery and management enabled, users can see all sites in hubs, even those that they currently have no access to.
You can select the following checkbox to limit users’ access: Only allow users to see Microsoft 365 Groups, Microsoft Teams, and Viva Engage communities they are members or owners of, or site collections they have permissions to. Even if this option is not selected, private Microsoft Teams are hidden to users who are neither member nor owners.
Make sure to consent for the AvePoint Online Services app in Hub Settings > App profile management before Cloud Governance can synchronize the site collections that logged-in users have permissions.
If you disable the discovery and management for Microsoft 365 Groups/Microsoft Teams/Viva Engage Communities/SharePoint sites, users will not be able to see groups/teams/communities/site collections in Hubs.
When you finish, click Save to save your configuration.
If you disable the discovery and management for Microsoft 365 Groups, Microsoft Teams, and Viva Engage Communities in hubs, note the following:
By default, the All workspaces, Favorite workspaces, My workspaces, and Recent workspaces built-in hubs are visible and accessible to end users in their Hubs. In Hub display management, you can configure which built-in hubs will be shown to end users and select a hub as the default hub.
End users can also set a default hub in their Hubs, which will overwrite the default hub set in Hub settings.
To configure the Hub display management, follow the steps below:
Click Hub displaymanagement, and the Hub displaymanagement panel appears.
Turn on/off the toggle of a built-in hub to display or hide the hub from end users in the users’ Hubs.
In the Default hub drop-down list, select a hub as the default hub. If you want to create a shared hub as the default hub, click Create a shared hub. For details about configuring shared hubs, refer to Manage Shared Hubs.
All built-in hubs are available to be set as the default hub. A shared hub must be published to all users to be set as the default hub.
Click Save to save your configurations.
A shared hub is a pre-defined hub configured by the IT administrator, and it can be shared with all users or a specific set of users/groups. End users can use the shared hub directly, and they no longer need to create their own hubs using the same filter criteria.
To create a shared hub, follow the steps below:
In Hub settings, click Shared hub management and then click Create.
In the Create shared hub panel, enter a hub name and then configure filters to include workspaces in the hub by following the instructions below:
Workspace type – Select the workspace type that you want to include in the shared hub.
When the Microsoft Teams, Microsoft 365 Groups, or Viva Engage Communities workspace type is selected, you can configure the switch that controls whether to display private Teams, Microsoft 365 Groups, or Viva Engage communities to users who haven't been added as members, owners, or admins of the private workspaces. By default, this switch is disabled
Filter teams/groups/communities by properties – Refer to the table below to filter workspaces by properties:
| Filter Rule | Filter Result |
|---|---|
| Public | All public teams/groups/communities. |
| Private | Private teams/communities that end users are owners/community admins or members of.All private groups. |
| Favorite workspaces only | All teams/groups/communities/sites that end users have marked as favorite. |
| I’m a member of | All teams/groups/communities that end users are members of. |
| I’m an owner of | All teams/groups/communities that end users are owners/community admins of. |
| I’m neither a member nor owner of | All public teams/groups/communities that end users are neither members nor owners/community admins of.Private groups that end users are neither members nor owners/community admins of. |
| With permissions | All site collections that you have permissions. |
| Without permissions | All site collections that you have no permissions. |
Select the hub you want to edit and click Edit on the ribbon. In the panel, you can edit the hub as needed. For more instructions on how to configure the fields in the panel, refer to the Create Shared Hub section.
Select one or more hubs that you want to delete and click Delete on the ribbon. A pop-up window appears asking for your confirmation. Click Delete to confirm.
To publish hubs, select one or more hubs with the status of Unpublished and click Publish on the ribbon.
To unpublish hubs, select one or more hubs with the status of Published and click Unpublish on the ribbon.