> For the complete documentation index, see [llms.txt](https://docs.dorg.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dorg.pro/install-dorg/install-a-new-dorg/post-install-configurations.md). # Post-install Configurations ## Register the DNS records At the end of the installation, the installed provided you a set of DNS record you have to register into the DNS of the domain you choosed to attach the Dorg to. In particular, they are: * 1 TXT record for domain validation * 4 CNAME record for the exposure of Dorg API, Console, Keycloak and Grafana endpoints. ## Grant Dorg permissions Ask you Azure Administrator to grant the Dorg Permissions in the Entra ID App Registrations called **DorgGraphAuth, DorgKeycloakEntraBroker** and **DorgMetricsCollector**. This is in Entra ID > Manage > App Registrations > All Applications tab > (app registration name) > Manage > API Permissions, and click on "Grant admin consent for Dorg". ### Configure Teams meeting transcript access To let the Dorg work with **Teams meeting transcripts**, a one-time configuration is required on the Microsoft Teams side. It authorizes the Dorg application to access the online meetings it is invited to (the transcript content itself is then read using the account of the user talking to the Dorg, so the Dorg only sees transcripts that user can already see). {% hint style="info" %} This step is performed by a **Teams Administrator** or **Global Administrator**, on a machine with the **MicrosoftTeams** PowerShell module. It is intentionally **not** run by the installer. {% endhint %} At the end of the installation, the installer prints these commands with your Dorg's **Client ID** (the **DorgGraphAuth** app registration) already filled in. Run them in PowerShell: ```powershell # 1) Install the MicrosoftTeams module (only the first time) Install-Module MicrosoftTeams -Scope CurrentUser -Force # 2) Sign in as a Teams / Global Administrator Connect-MicrosoftTeams # 3) Authorize the Dorg application and grant the policy globally New-CsApplicationAccessPolicy -Identity DorgPolicy -AppIds "" -Description "Dorg meeting transcript" Grant-CsApplicationAccessPolicy -PolicyName DorgPolicy -Global ``` Replace `` with the Client ID shown by the installer. {% hint style="warning" %} If a policy named **DorgPolicy** already exists in your tenant (for example another Dorg was installed before), do **not** recreate it, add this Client ID to the existing policy instead: ```powershell $existing = (Get-CsApplicationAccessPolicy -Identity DorgPolicy).AppIds Set-CsApplicationAccessPolicy -Identity DorgPolicy -AppIds ($existing + "" | Select-Object -Unique) ``` {% endhint %} Make sure the **admin consent** for the **DorgGraphAuth** permissions has been granted (see *Grant Dorg permissions* above) as it now includes *OnlineMeetings.Read.All* and *OnlineMeetingTranscript.Read.All*. Meeting transcription must also be enabled in your Teams meeting policies for transcripts to exist. ## Wait for DNS propagation Wait until DNS are properly propagated and Azure FrontDoor detects the DNS and setup the proper SSL certificates. {% hint style="warning" %} After setting the DNS, the propagation of the configuration on Azure FrontDoor may take up to **1 hour**, so be patient. {% endhint %} To know if all is set up, try accessing this URL:\ [`https://auth./admin/`](https://auth.maya-dorg.epsolsrl.com/admin/)\ example:\ [`https://auth.my-dorg.mycompany.com/admin/`](https://auth.maya-dorg.epsolsrl.com/admin/) In case you see an SSL certificate error page, just wait up to 1 hour for proper setup propagation, and re-check if you correctly set the DNS records.\ \ When you can see the Keycloak login page and no SSL errors in the browser, you can move to the next step. ## Authorize your Dorg user Open this URL in your browser: `https://api./api/MicrosoftDorgAuth/authorize` and complete the login with the Dorg user account. ## Configure your Dorg Open the Admin Console with this URL in your browser: `https://console./` And login with your personal Microsoft account. As a first user that access the Admin Console, you will be automatically enrolled in the **Onboarders** group. In the Console you now have to configure the following: ### Dorg user information Click on "Dorg and Skills" in the left menu, then "Configure Dorg".\ Fill all the required information. Avoid to change Dorg Name, Surname and Email. Then click Save.\ \ You'll have to set the **HOS (Human Oversight Supervisor)**: the person responsible for Dorg behavior and operations.\ For initial operation, you can set yourself as HOS, until the real HOS will connect with Dorg and can be selected here. ### Test the Dorg You can now contact your Dorg user via **Microsoft Teams**. You will be required to complete an authentication flow by logging in with your Microsoft Entra ID account. After authentication, if everything is working correctly, the Dorg should respond to your greeting message. ### Enroll users in Groups The Dorg comes with the following pre-defined user groups: * **Onboarders**: users who install and initialize the Dorg * **Team Members**: all the employees that belongs the same department of the Dorg user. * **Colleagues**: all the Company employees. * **Teachers**: a person that have the role to interact with Dorg to provide additional knowledge and competencies. * **Guests**: all users outside the Company registered as Guests in Entra ID * **Externals**: reserved for future use. Only users in Onboarding group and the HOS can access to the Console. To add a user to a group: 1. The user must start a conversation with the Dorg in Teams 2. The user must complete the authentication flow After this, the user will appear in the Console user list and can be assigned to groups. All users in Entra ID can interact with the Dorg, even without group assignment. However, without a group, their capabilities will be limited. ### Assign permssions on Tools for Groups Click on **Dorg and Skills > Tool Configuration**. Here you can configure, for each group, which Tools users are allowed to use. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dorg.pro/install-dorg/install-a-new-dorg/post-install-configurations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.