To Assign Roles to your users, you need to be an Azure AD Global Administrator. Users need a Role assigned to them in order to log in to Records365.
In order to log in and interact with Records365, users need to be assigned the designated Records365 roles in Azure Active Directory. Records365 doesn’t store users or passwords but instead leverages your corporate Azure Active Directory (Azure AD) as the identity provider. This allows the centralized management of all your users and applications directly in your Azure AD.
Records365 leverages 2 authentication protocols used in different scenarios:
Once the provisioning of your tenant is complete you are ready to get started with Records365. The first step is to give access to your users by assigning specific roles to them in Records365. To do this follow the steps below:
This configuration is required for the Records365 Connector Framework to authenticate with the Records365 Connectors API, which is necessary for any Connector to perform Records Management operations.
Even with this configuration, Users will need a Role assigned to them in order to log in to Records365.
Permissions are pre-defined for each Role and cannot be modified.
It is possible to assign multiple roles to the same user. In that case, the role with the highest set of permissions is applied - for example, a user with the Application Administrator and Records Visitor Role will have all the Application Administrator permissions.