# Administer Conclude > The Admin console page by page, and the five scopes at which Conclude controls access, for account owners and account admins. Canonical HTML page: https://conclude.io/doc/admin/ Last updated: 2026-11-02 --- This chapter is for account owners and account admins. You open the **Admin console** at the bottom of the Dashboard sidebar. To install Conclude for the first time, start with [Set up Conclude](https://conclude.io/doc/setup/). ## The Admin console This chapter follows the console's sidebar. The sidebar has **Solutions** at the top and five sections below it. A section opens to show its pages. The search icon at the top of the sidebar finds a page by its name or by what it holds, such as "invoices" for Billing. A billing admin who is not an account admin sees only Account and Billing. - [Solutions](https://conclude.io/doc/admin/solutions/) switches Connect, Apps, Agents and Integrations on or off, and installs Conclude on Slack and Microsoft Teams - [Organization](https://conclude.io/doc/admin/organization/) holds the account, billing, the workspaces, the Microsoft Teams integration account and organization-wide settings - [Users and access](https://conclude.io/doc/admin/users-and-access/) holds the users, roles and permissions, API keys, security and the audit log - [Agents](https://conclude.io/doc/admin/agents/), [Apps](https://conclude.io/doc/admin/apps/) and [Connect](https://conclude.io/doc/admin/connect/) hold the settings of each solution. A section is listed while its solution is on - [Reference](https://conclude.io/doc/admin/reference/) lists what Conclude asks Slack and Microsoft for, and the open source software it ships with The account owner also sees **Delete account** on the **Account** page. It does not appear inside the Microsoft Teams app. [Scripting](https://conclude.io/doc/reference/scripting/) is switched on per organization, and the console has no control for it. ## Scopes of control ![Five nested boxes for organization, workspace, channel, app roles and ticket, each with the setting that controls it](https://conclude.io/images/doc/figures/f14-scopes-of-control.svg) *Figure: Each scope has its own setting, from the roles in the Admin console down to a ticket's owner.* ### Organization Account admins are included in every permission. **Roles & permissions** has four Connect permissions: Connect channels, Create chats, Connect external channels and Manage bridges. It has one Apps permission, Manage apps. Each permission is listed only while its solution is on. You set each permission to Admins, Admins + specific users or Everyone. On Starter you cannot change the level. Pro offers Admins and Everyone. Enterprise adds Admins + specific users. ### Workspace A workspace is one Slack workspace or one Microsoft Teams tenant. Installing Conclude grants it the platform's authorization scopes. On Slack these are the [bot and user token scopes](https://conclude.io/doc/admin/reference/permissions-slack/). On Microsoft Teams they are the [resource-specific (RSC) scopes](https://conclude.io/doc/admin/reference/permissions-microsoft-teams/). Delegated Graph scopes are granted by each signed-in user or by a tenant admin. On Teams, the integration account is a generic Microsoft account. It posts when no user's credentials are available. ### Channel Connections and app installations are per channel. Teams RSC permissions reach only the team or chat where Conclude is installed. An app's **Who has access** setting on the [Roles tab](https://conclude.io/doc/apps/editor/roles/#access) offers two choices. The default is members of the install channel. The other is everyone on the team. ### App roles Each app defines an owner and members on the [Roles tab](https://conclude.io/doc/apps/editor/roles/). Admins and superusers can only be defined in YAML, in the [roles block](https://conclude.io/doc/reference/macros-and-roles/#roles-block). `${initiator}` is the ticket's creator. App roles are separate from account roles. An app admin is not an account admin. ### Ticket Each ticket is a thread in the app's channel. In channel mode, each ticket gets its own channel. A ticket's members are the people the app's roles invite. A ticket has at most one owner. Without an owner it is unassigned. Superusers hold rights only where a role expression names `${superusers}`. That is usually an attribute's `editors`. **Platform scopes are not Conclude permissions.** Slack and Microsoft grant the platform scopes. Those scopes don't decide who may do what inside Conclude. Roles & permissions and app roles decide that. ## Related pages - [Organization](https://conclude.io/doc/admin/organization/), [Security](https://conclude.io/doc/admin/users-and-access/security/), [Third-party licenses](https://conclude.io/doc/admin/reference/third-party-licenses/) - [Active users (Connect)](https://conclude.io/doc/admin/organization/billing/active-users-connect/) and [Active users (Apps)](https://conclude.io/doc/admin/organization/billing/active-users-apps/) explain what drives billing ## Pages in this section - [Account](https://conclude.io/doc/admin/organization/account/index.html.md): The Account page of the Admin console, which shows the organization’s details, its license and its usage, and where the account owner deletes the account. - [Active users (Connect)](https://conclude.io/doc/admin/organization/billing/active-users-connect/index.html.md): What counts as an active user in Conclude Connect for internal and external connections, and where admins see the count. - [Merge user accounts](https://conclude.io/doc/admin/users-and-access/users/merge-user-accounts/index.html.md): How account administrators merge a person’s separate Slack and Microsoft Teams accounts into one Conclude user, and when to hide an account instead. - [Slack permissions](https://conclude.io/doc/admin/reference/permissions-slack/index.html.md): Every Slack bot and user OAuth scope the Conclude app requests, what each scope allows and why Conclude needs it. - [Solutions](https://conclude.io/doc/admin/solutions/index.html.md): The Solutions page of the Admin console, where an admin switches Connect, Apps, Agents and Integrations on or off and installs Conclude on Slack and Microsoft Teams. - [Active users (Apps)](https://conclude.io/doc/admin/organization/billing/active-users-apps/index.html.md): What counts as an active user in Conclude Apps, in Channel mode, in Thread mode and for customer support, and where admins see the count. - [Hide user accounts](https://conclude.io/doc/admin/users-and-access/users/hide-user-accounts/index.html.md): How to hide, find and unhide user accounts in the Admin console, and when to hide an account instead of merging it. - [Microsoft Teams permissions](https://conclude.io/doc/admin/reference/permissions-microsoft-teams/index.html.md): The Microsoft Teams resource-specific consent permissions and Microsoft Graph delegated scopes Conclude requests, and what each one is used for. - [Roles & permissions](https://conclude.io/doc/admin/users-and-access/roles-and-permissions/index.html.md): The account roles and the Connect and Apps permissions, where an admin sets them, and which access levels each plan allows. - [API keys](https://conclude.io/doc/admin/users-and-access/api-keys/index.html.md): The API keys page of the Admin console, where an admin issues and revokes the keys that the organization’s own tools use with the Conclude API. In beta. - [Manage email domains](https://conclude.io/doc/admin/users-and-access/users/manage-email-domains/index.html.md): How account admins choose which email domains Conclude shows in the user directory and user pickers, and which users stay listed anyway. - [Third-party licenses](https://conclude.io/doc/admin/reference/third-party-licenses/index.html.md): Lists the third-party open source software distributed as part of the Conclude service, with the full text of each license. - [Workspaces](https://conclude.io/doc/admin/organization/workspaces/index.html.md): The Workspaces page of the Admin console, where an admin adds and removes Slack workspaces and Microsoft Teams tenants, picks the main workspace and sets a Teams workspace’s integration account. - [Agents](https://conclude.io/doc/admin/agents/index.html.md): The Agents section of the Admin console, with All agents, Deployment, Learning, Knowledge and Usage, and where each page is explained. - [Integration account](https://conclude.io/doc/admin/organization/integration-account/index.html.md): How to set up, check and repair the Microsoft Teams integration account that Conclude posts as when a user has no credentials in the tenant. - [Security](https://conclude.io/doc/admin/users-and-access/security/index.html.md): Certifications, hosting, data handling and platform permissions for admins reviewing Conclude, plus how an app’s secrets are stored and who can read them. - [Apps](https://conclude.io/doc/admin/apps/index.html.md): The Apps section of the Admin console, with Integrations, Templates and Functions, and where each page is explained. - [Audit log](https://conclude.io/doc/admin/users-and-access/audit-log/index.html.md): The Audit log page of the Admin console, which records changes to the organization and who made them. In beta. - [Settings](https://conclude.io/doc/admin/organization/settings/index.html.md): The Settings page of the Admin console, where account admins set the default Dashboard for everyone in the organization and decide where system alerts go. - [Connect](https://conclude.io/doc/admin/connect/index.html.md): The Connect section of the Admin console, with Sync settings and Message display, and where each setting is explained.