--- title: "Finalize Configuration" slug: "finalize-d365-configuration" description: "This article serves as a guide on how to finalize the Omnichannel integration. " updated: 2022-11-14T17:55:35Z published: 2022-11-14T17:55:35Z canonical: "docs.screenmeet.com/finalize-d365-configuration" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt > Use this file to discover all available pages before exploring further. # Finalize Configuration ## Finalize Configuration ScreenMeet Installation and Configuration with Microsoft Omnichannel is completed. As a final step in the process, assign appropriate ScreenMeet security roles to **users** or **teams**. ### Assign security roles ScreenMeet security roles are divided into two tiers: 1. **Operation based roles** - **ScreenMeet Agent** – grant permissions to create a session - **ScreenMeet Admin –** grant permissions to customize organizational settings on [http://console.screenmeet.com](http://console.screenmeet.com) - **ScreenMeet Supervisor** – grant permissions to view sessions for all agents in a business unit. A supervisor cannot create a session 1. **Product based roles** Grant agents permissions to individual ScreenMeet products - **ScreenMeet Cobrowse** - **ScreenMeet Live** - **ScreenMeet Support** - **ScreenMeet Replay** Note – starting version v3.2.5 each D365 user/team intending to use ScreenMeet products must be assigned at least one operation-based role and a product-based role. Example: If **Agent A** is Live agent and **Agent B** is Cobrowse agent, the security roles assignment will look like: **Agent A** Security Roles: 1. ScreenMeet Agent 2. ScreenMeet Live **Agent B** Security Roles: 1. ScreenMeet Agent 2. ScreenMeet Cobrowse For access to multiple products for agents, product-based security roles can be stacked and can be assigned to Teams or users directly. ![](https://cdn.document360.io/9da39725-20e5-434f-83a4-d630456099dc/Images/Documentation/image-1668448528534.png)