Collaborate with a Mavim Partner in Mavim iMprove
This guide is for you as a "Customer Technical Contact" and takes you through the necessary steps in the Mavim Connect Center (MCC) and Mavim iMprove to grant external partner users access and set specific, granular content permissions.
Collaborate in Mavim iMprove
Managing access for your external partners is a two-part process. First, you'll grant them system access and a license through the Mavim Connect Center (MCC), and then you'll configure their specific content permissions within the iMprove database.
In Mavim Connect Center:
Access to iMprove is managed through the MCC and requires enabling guest access and license provisioning in the MCC.
License and Access
You need to request Mavim to set up the ability to invite guest users to your iMprove domain. This initial step is required to allow external accounts to access your iMprove instance.
Next, add every Partner user who needs iMprove access to your organization's Microsoft Entra AD, either as a user or a guest user. *
Then, use the MCC to provide a license to each Partner iMprove user.
Finally, ensure the new iMprove users are added to the relevant database(s) where they need to perform work.
NOTE THAT:
Administrators will have edit access to all content and settings in iMprove and will not be affected by any content permissions. Administrators can also set up permissions for other users and control other general settings for iMprove in that database.
Users will have read access to all content in the database, no access to settings and can be granted appropriate permissions to content by the Administrators
In Mavim iMprove:
Determine your strategy
You can determine how you want to engage your contributors. The tools you have at your disposal are:
Permissions:
These can be set up to a granular level using Groups – Roles and Users. Users are added to Groups, Roles (sets of permissions on topic level) are added to Groups. Permissions are Read / Edit / Restricted and can be set to Topic, but also to individual sets of metadata called Field sets. As an example, this makes it possible to provide a user access to edit one particular field set on certain topics, while only allowing read access to other field sets and other elements of the topics, like charts, description and relationships.
Approval permissions:
When you need more control over changes in your content or want to ensure cooperation between different teams on changes in your content you set up Approval permissions. See this article for instructions on
how to set it up:
https://knowledge.mavim.com/en/approval-flow-administrators
And how to use:
https://knowledge.mavim.com/en/approval-flow-contributors
https://knowledge.mavim.com/en/approval-flow-approver
Set up permissions - Example
We will show you how to set up permissions by way of an example:
You are working with a Microsoft Dynamics365 Implementation Partner and are running a D365 Implementation project supported by the Mavim Platform.
We distinguish 3 roles: the Customer Technical Contact sets up the permissions in the MCC and iMprove for the Partner Project Consultants and the Customer Contributor to work together on content in iMprove.
The Project Consultant needs Edit permissions on the field set Dynamics Process Attributes to be able to indicate whether processes are in or out of scope.
It is important that whatever the Project Consultant does is confirmed by you as a customer so you set up Approval permissions for the Customer Contributor.
Steps:
- Set up Group: Project Consultants
- Create Role: Scoping Permissions Edit Field Set – Dynamics Process Attributes
- Add Role and User to Group
- Set up Approval Permissions for the Customer Contributors
Result is:
When Project Consultant changes scope indicator on one of the processes:
The Customer Contributor needs to approve it: