Workspaces¶
The problem: in larger organizations, many teams work in Actian AI Analyst at the same time — finance, sales, marketing — and each wants its own models, AI analysts, and warehouse connections kept apart from the others. Until now the only way to get that isolation was to spin up a second organization, which splits your members, seats, and billing across Orgs and forces a re-login to move between them.
The solution: Workspaces. A Workspace is a self-contained area inside your organization that holds its own semantic layer (models, metrics, glossary), its own AI analysts, its own conversations, and its own data connections. An Admin decides, per member, which Workspaces each person can reach and what they can do there. Finance's warehouse simply doesn't exist for someone who only works in Marketing.
Unlike a second organization, Workspaces share one member list, one set of seats, and one bill — so you get isolation without the overhead.
Two principles to keep in mind:
- Workspaces fence reads and writes. A member who can't reach a Workspace sees none of its models, analysts, conversations, or connections — not just its edit controls. The boundary is hard in both directions.
- Everything a Workspace contains stays inside it. Models, analysts, glossary terms, saved artifacts, and conversations belong to one Workspace and are not shared across Workspaces.
The default workspace¶
Every organization starts with exactly one default workspace that holds everything you have today. As long as your organization has only that one Workspace, nothing about the product changes: there is no Workspace switcher, no extra columns, and no Workspace picker anywhere. The concept stays completely out of the way until an Admin creates a second Workspace.
The default workspace cannot be deleted. If you delete the Workspace a member was last using, they are moved to the default workspace.
Managing workspaces¶
Only Admins can create, rename, and delete Workspaces from Settings > Workspaces in Actian AI Analyst Studio.
Creating a workspace¶
- Go to Settings > Workspaces.
- Click Create workspace.
- Enter a name (unique within the organization) and click Create.
A new Workspace starts empty — its own blank semantic layer with no models, analysts, or connections yet. Attach the data connections it needs (see Data connections in a workspace below) and grant people access from the Members page.
Renaming a workspace¶
Click Rename next to a Workspace, enter the new name, and save. Renaming never affects what the Workspace contains or who can reach it.
Deleting a workspace¶
Click Delete next to a Workspace. Because a Workspace fences everything it contains, deleting one permanently destroys everything inside it — its models, metrics, glossary terms, AI analysts, conversations, saved artifacts, and any connections owned by that Workspace.
Warning
Deleting a workspace cannot be undone. Before you confirm, the dialog itemizes exactly what will be destroyed so there are no surprises. If you want to keep something, move it out first — or attach a shared connection to another Workspace so it survives.
Switching between workspaces¶
Once your organization has more than one Workspace, a Workspace switcher appears in the app, grouped under your organization in the sidebar. Switching changes your active Workspace immediately and takes you to its home — you'll see only that Workspace's models, analysts, conversations, and connections.
- People who can reach only one Workspace never see the switcher — the product looks exactly as it does today.
- Admins can switch freely between every Workspace in the organization without a re-login.
Data connections in a workspace¶
Data connections are managed at the organization level, but each connection is only visible in the Workspaces it is attached to. From a connection's detail page an Admin chooses which Workspaces may see and build on it, so a Finance warehouse can stay hidden from Marketing without maintaining the same credentials twice.
A Studio member can also create a private connection that belongs to a single Workspace. Only members of that Workspace can see or manage it; an Admin reaching in from elsewhere sees that the connection exists but never its credentials or contents.
See Connections for how to add and manage data connections.
Reaching a workspace and what you can do there¶
Access to a Workspace is granted per person from Settings > Members. Rather than a single organization-wide role, each person's permissions are the combination of their organization role and any per-Workspace roles they've been given:
- Explorer in a Workspace can converse with its AI analysts, explore data, and save artifacts, but every authoring control is locked.
- Studio in a Workspace can additionally build and edit that Workspace's semantic layer, analysts, and connections.
- Manager in a Workspace can do everything a Studio member can, plus add, re-role, and remove that Workspace's members — a delegated inviter for a single Workspace.
Admins reach every Workspace in the organization automatically, without needing a per-Workspace grant. See Members for how to grant, change, and remove Workspace access, including assigning a Workspace role at invite time.
What a member without access experiences¶
Access is additive: a person reaches only the Workspaces they've been granted, and sees nothing of the ones they haven't.
- Workspaces they can't reach don't appear in the switcher, and none of their models, analysts, conversations, or connections are visible or searchable.
- Within a Workspace where they hold only an Explorer role, authoring controls render in a view-only state, and asking Steward to make a change gets a polite in-chat refusal — the asset is left unchanged.
- Access can be set before first sign-in. You can grant a Workspace role to someone who has been invited or provisioned by your identity provider but has never logged in yet.
Auditing¶
Workspace management and access are fully audited. Creating, renaming, or deleting a Workspace, attaching or detaching a connection, and granting, changing, or removing a member's Workspace role all write entries to the audit log.