Skip to content
Docs

Settings & Admin

Settings is where workspace and tenant admins configure everything that powers Adverity Atlas, people, workspaces, data governance, integrations, and activity. Feature pages link here for specific tasks; this page is the map.

It mirrors the five sections of the in-product Settings page.

People & Access

Who can use Adverity Atlas and how they authenticate.

  • Members and roles: Invite people on Members, assign per-workspace roles on Workspace Access, and issue API keys on Service Accounts

  • Single sign-on: Authenticate through your own SAML 2.0 identity provider

  • Approvals: Review and vote on actions that need sign-off

Workspaces & Storage

How your tenant is divided, and where its files live.

Data Governance

Which workspaces reach which data, and keeping shared data accountable.

  • Data governance: Bind org sources to workspaces on Data Sources, revoke artifact links on Public Shares, and resolve duplicates on Data Overlaps

Integrations

External services Adverity Atlas connects to.

  • Service configs: Shared OAuth client credentials for connectors that sign in through your own client

  • AI providers: Which LLM provider and models power chat and automations

  • Web research: The search provider the agent uses for web research

  • Webhooks: Send platform events to your own systems over HTTP

  • MCP servers: Register external tools the agent can call

  • Slack: Get approval requests and notifications as Slack direct messages

Slack

Important

Available on demand. The Slack app may not be enabled in your workspace by default. Contact your Adverity account manager to activate it.

Connect your Slack workspace so members receive their Adverity Atlas notifications as direct messages from the Adverity Atlas app, alongside the in-app notifications. The Slack card sits under Integrations on the Settings page, and only a tenant owner sees it, because the connection covers every member of the tenant.

  1. On the Slack card, click Add to Slack.

  2. Approve the app in Slack. You return to Settings with “Slack connected.”, and the card reads “Connected to” your Slack workspace name.

  3. Adverity Atlas then links members to Slack by email address: a member whose Adverity Atlas email matches a Slack account starts receiving direct messages. Bots, deactivated accounts, and guest accounts are never linked.

Notifications sent to Slack include approval requests and their outcome, conversations and artifacts shared with you, failed and auto-paused automations, failed data source syncs and degraded data source health, failed knowledge pipelines, and invitations. Each message links back with Open in Atlas, or with Open conversation and Open artifact for shared items. An approval request message shows the request’s details and when it expires.

To stop delivery, click Disconnect on the card and confirm “Disconnect Slack? Atlas will stop delivering notifications there.” Adverity Atlas removes the app from your Slack workspace and deletes its stored access.

Message

Cause

“The Slack app is not configured for this environment.”

Slack is not set up on this Adverity Atlas environment. Contact your Adverity account manager

“Slack authorization link expired or is invalid”

The approval in Slack took too long or the link was reused. Click Add to Slack again

“Slack authorization was cancelled: …”

The install was declined in Slack

“You no longer have permission to connect Slack.”

Your role changed while the install was in progress. Only a tenant owner can connect Slack

Activity

What has happened, and what it costs.

Permissions

Most Settings pages require Admin at the tenant level. Members can see their own access but cannot change tenant configuration. Individual pages note where a more specific permission applies, for example Approvals, which a Knowledge Manager can also reach.

Workspace access runs on five cumulative roles, Viewer, Analyst, Editor, Knowledge Manager, and Admin. See Members and roles for what each one covers.

What’s next?

Was this page helpful?