MOCA365 comes with a customisable premade SharePoint communication site. From the self-service portal it is possible for end users to request and create workspaces that supports their needs.

Using the self-service portal makes it easier to answer the question: “Which tool when?” by only presenting the relevant options to the end user.

The self-service portal has integrated adoption material. It comes with a set of premade information, texts and videos which can be adjusted to your organisation.

It is easy to configure the creation wizards and guide the users safely through the process. User friendly e-mail notifications are predefined with best-practice adoption material.

MOCA365 delivers a variety of different email notifications. Most governance  tasks have a corresponding email notification. All notifications can be customised without code.

Examples of notifications: “New workspace is created”, “Owners are missing”, “A revision is needed”, “A guest user is added”, and more.

An out-of-the-box set of templates are part of the self-service portal. This makes it possible to start the solution without too much configuration. It is possible to modify the existing templates, delete them, and create new ones.

Examples of templates: Team settings, metadata for search refinement, auto-populate SharePoint site contents, predefinned tabs, predefined channels, document templates, ad-hoc workspace, organisational workspace, project workspace, and more.

• Detect new groups
• Detect deleted and archived groups
• Ensure owners (detects and ensures that there are two owners for all M365 groups)
• Guest-user-added detected
• Time-for-review detection
• Main governance job (which checks properties on Teams and SharePoint to notify if there has been any changes).

It is possible to configure metadata on workspaces. A typical way to use this functionality is to define metadata for certain types of workspaces and require the user to fill in the metadata when they request a new workspace.

A simple example is a workspace designed for customer projects. Metadata that could be requested as part of the creation process could be the project name, project description, or customer name.

MOCA365 supports different roles which can be managed in Azure AD.

This makes it possible to have roles with administrative privileges and to limit which workspaces should be visible for end users.

MOCA365 comes with two highly configurable web parts. For simple and normal scenarios, the web parts are predefined and do not have to be configured.

However, the web parts make it possible to support more complicated scenarios like bespoke user interface (forms), and bespoke listing of workspaces without making code changes. 

We often encounter organisations that for one reason or another cannot use dynamic groups but still want the membership of the M365 group to be managed by existing security or distribution groups.

In this scenario, the AD synchronised teams is very useful.

It is possible for IT to configure which settings should be monitored and/or enforced. This can be done at either the tenant or workspace level.

Settings that need to be enforced can be enforced at creation time or at a later stage.

From the admin interface, it is possible to modify metadata and ownership of the groups.