Setup Access

ROGER365.io only uses Microsoft industry standard technology. The ROGER365.io is an Enterprise Application within the Microsoft Entra ID. Via this Enterprise Application you can allow users to sign-in to ROGER365.io admin portal or not, and into which sections users can have an access to. It is strongly recommended to configure the ROGER365.io Enterprise Application within Microsoft Entra ID according to your own company policy.

Role reference can be found at this documentation page.

Disclaimer: The information in this document must be used as a guidance, please make sure you have good knowledge about your own Microsoft Office 365 and Microsoft Entra ID situation before continuing.

Azure / Microsoft Entra ID:

1. Create a security group at Microsoft Entra ID tenant. Save the Object Id of a freshly created security group, it will be needed later.
2. Assign selected users.
3. Navigate to Enterprise Applications, and choose “ROGER365.io” application.
4. Add created group to “ROGER365.io” application via “Users and groups” section from a Resource Menu. Group have to have “TeamsUser” role assigned.

Note: Assigning “Admin” role to a security group will grant Admin permissions to ROGER365.io admin portal for every member of a group!

ROGER365.IO admin portal:

1. Navigate to “Permissions” tab.
2. Press “+ Add Functional Permissions” button.
3. Paste Object Id of a security group into “Group ID” field, from Azure’s step 1.
4. Give a descriptive name to your group of Functional Permissions.
5. Set proper rights for chosen Functional permissions (sections of a portal).

Examples of usage is described at this documentation page.

Important Notes:

• General, Resource Accounts and Call Park pages are restricted only to Admin role.
• Any permission changes are effective usually after ~10 seconds (requires re-login to admin portal).
• You cannot combine user “Admin” permission with RBAC group permissions (restrictions) where a user is part of “Admin” permission will always have priority over RBAC group restrictions. Not respecting this will result with User having full access to admin portal.

‍