Skip to content
Docs

Workspaces and storage

Workspaces divide your tenant into separate areas, by team, brand, market, or client, each with its own data scope, glossary, and members. Storage is where the files those workspaces produce are kept. Both live under Settings > Workspaces & Storage.

Prerequisites

Admin role at the tenant level to create workspaces. Adding or editing a storage backend needs the Editor role; deleting one needs Admin.

Workspaces

Workspaces form a hierarchy. A child workspace sits under a parent and narrows what the parent can see, which is what makes them useful for agencies handling many clients, or brands separating markets.

  • Display name: What people see in the workspace switcher

  • Description: What this workspace is for, so the switcher is self-explanatory as the list grows

  • Labels: Key-value pairs for grouping and filtering, useful once you have more than a handful

  • Position in the hierarchy: Which workspace it sits under, which determines what it can reach

Creating a workspace

  1. Go to Settings > Workspaces and click Create.

  2. Give it a display name and description.

  3. Choose its place in the hierarchy, top level, or under an existing workspace.

  4. Save, then bind the data sources it should reach and add members.

A new workspace starts with no data and no members. It becomes useful once you bind data sources and grant access.

What a workspace scopes

Scoped per workspace

Shared across the tenant

Which data sources can be queried

The connection credentials themselves

Workspace-tier glossary concepts

Standard and organizational glossary

Conversations and artifacts

Members (assigned per workspace)

Knowledge entries

AI provider configuration

Note

Moving or deleting a workspace affects everything inside it: conversations, artifacts, and workspace-tier glossary concepts. Check what it holds before restructuring.

Storage

Artifacts, uploaded files, and exports need somewhere to live. Settings > Storage configures that backend per workspace.

Three backends are supported:

  • Amazon S3: Bucket and region, with an optional endpoint URL for S3-compatible services

  • Google Cloud Storage: Bucket, authenticated with a service account

  • Azure Blob Storage: Storage account and container

Configuring a backend

  1. Go to Settings > Storage and open the Configure Storage panel.

  2. Pick the workspace, then the Storage Backend.

  3. Fill in the Configuration fields for that backend.

  4. Under Authentication, choose a Method and supply its credentials.

  5. Click Create Storage.

Configuration fields per backend:

Backend

Configuration fields

Amazon S3

Bucket (required), Region (defaults to us-east-1), Endpoint Url (optional, for S3-compatible services)

Google Cloud Storage

Bucket (required)

Azure Blob Storage

Account Name and Container Name (both required)

Authentication methods per backend:

Backend

Method

What it needs

Amazon S3

Access Keys

Access Key Id and Secret Access Key

Amazon S3

Assume Role

Role Arn, and optionally External Id plus access keys to assume from

Amazon S3

Instance Profile / Environment

Nothing. Authentication uses the environment

Google Cloud Storage

Service Account Key

Service Account Json, containing project_id, client_email, and private_key

Google Cloud Storage

Access Token

Access Token

Azure Blob Storage

Account Key

Account Key

Azure Blob Storage

SAS Token

Sas Token

Azure Blob Storage

Connection String

Connection String

Credentials are stored encrypted. When editing an existing backend, leaving a secret field blank keeps the value already stored, so you do not have to re-enter a key to change a bucket.

Note

This is object storage for the files Adverity Atlas produces. It is not a copy of your warehouse data, and your warehouse tables are never written to. See Data sources.

Health check

After configuring a backend, run the health check. It confirms the credentials work and the location is writable, which is worth doing at setup rather than discovering the problem the first time someone saves an artifact.

Warning

A workspace with no storage configured, or one whose credentials have stopped working, cannot accept file uploads or save artifacts. The Files tab says “Storage not configured” rather than failing at upload time.

Permissions

Roles are cumulative, so the role named is the lowest one that can take the action.

Action

Required role

Use a workspace you have access to

Viewer

Create or edit workspaces

Admin

Add or edit a storage backend

Editor

Delete a storage backend

Admin

What’s next?

Was this page helpful?