Workspaces

Organize Your AI Projects with Workspaces

Organize AI Chatbots, tools, assistants, and sources by project, client, or department. Team collaboration, role-based access control, and complete isolation. Perfect for agencies, multi-location businesses, and growing teams.

1

Create a Workspace

Set up a new workspace for a project, client, department, or location.

2

Invite Team Members

Add collaborators with appropriate roles (Owner, Admin, Contributor, Reader, Guest).

3

Build AI Experiences

Create AI chatbots for customers, internal tools for teams, assistants, and upload sources—all within the workspace.

4

Collaborate & Deploy

Team members work together, iterate, and deploy AI experiences to production.

Core Features

Everything you need to manage teams, projects, and multi-location operations

Organized Project Structure

Create separate workspaces for different projects, departments, or clients. Keep everything organized and isolated.

  • Unlimited workspaces per account
  • Isolated environments for each project
  • Separate chatbots, tools, assistants per workspace
  • Independent source libraries per workspace
  • Clear separation between production and testing

Team Collaboration

Invite team members to workspaces with granular permissions. Work together on AI projects seamlessly.

  • Invite unlimited team members
  • Real-time collaboration on AI experiences
  • Shared access to sources and knowledge
  • Activity logs and change history
  • Team member activity tracking

Role-Based Access Control

Assign role-specific permissions with clear matrixes across all workspace entity types.

  • Owner/Admin/Contributor/Reader/Guest role model
  • Cross-entity matrix for chatbots, tools, assistants, prompts, personas
  • Role-capped transfer and delete controls
  • Feature-gate aware permission enforcement
  • Prevent unauthorized changes

Multi-Location Management

Perfect for multi-property businesses, franchises, and distributed teams managing multiple locations.

  • Workspace per location or region
  • Centralized knowledge with local overrides
  • Location-specific chatbots and tools
  • Hierarchical organization structure
  • Franchise-friendly management

Role-Based Access Control

Assign the right permissions to the right people

Owner

Permissions:
  • Full workspace access
  • Manage team members and settings
  • Create, edit, publish, and delete resources
  • Transfer resources across scopes
  • Delete workspace
Recommended For:
Workspace owners and accountable leaders

Admin

Permissions:
  • Full workspace access (except transfer)
  • Invite and remove team members
  • Change workspace settings
  • Create, edit, publish, and delete chatbots, tools, assistants
  • Manage sources and knowledge base
  • View billing and usage analytics
  • Export data and conversation logs
  • Cannot transfer resources by default
Recommended For:
Workspace owners, project leads, senior managers

Contributor

Permissions:
  • Create and edit chatbots, tools, assistants
  • Create and edit prompt/persona versions
  • Upload and manage sources
  • Run and iterate on workspace resources
  • Cannot delete resources
  • Cannot transfer resources
  • Cannot manage members or workspace settings
Recommended For:
Content creators, tool builders, operations team

Reader

Permissions:
  • Read access to workspace resources
  • Run access where supported
  • View sources and analytics
  • Cannot create or modify resources
  • Cannot delete or transfer resources
  • Cannot manage members or workspace settings
Recommended For:
Stakeholders, clients, auditors, reporting teams

Guest

Permissions:
  • Run-only access in limited entry points
  • No workspace management pages
  • No create, update, delete, or transfer permissions
  • No member-management permissions
Recommended For:
Highly restricted access scenarios

Cross-Entity Permission Matrix

Same workspace roles, different entity behaviors. Effective permission = role capability + entity capability (if present) + plan/feature gate.

RoleChatbotsToolsAssistantsPromptsPersonas
OwnerFull accessFull accessFull accessFull accessFull access
AdminView/run/edit/delete (no transfer)View/run/edit/delete (no transfer)View/run/edit/delete (no transfer)View/add/edit/deleteView/add/edit/delete
ContributorView/run/edit (no delete/transfer)View/run/edit (no delete/transfer)View/run/edit (no delete/transfer)View/add/edit (no delete)View/add/edit (no delete)
ReaderView/run onlyView/run onlyView/run onlyView onlyView only
GuestRun-only in limited entry pointsNo workspace management accessNo workspace management accessNo workspace management accessNo workspace management access
Need full gate-level details? Read the Workspace Permissions Matrix guide.

Common Use Cases

See how different organizations use workspaces

Agency Managing Multiple Clients

Marketing agency with 15 clients

Implementation:
  • Create one workspace per client
  • Client-specific chatbots and branding
  • Isolated source libraries (no data mixing)
  • Invite client stakeholders as Readers
  • Dedicated team members per workspace

Hotel Group with Multiple Properties

Hotel chain with 50+ properties across 3 regions

Implementation:
  • Regional workspaces (North, South, West)
  • Property-specific chatbots under each region
  • Centralized brand sources + local overrides
  • Regional managers as Admins
  • Property staff as Contributors for their location

Enterprise with Departments

Large company with Sales, Support, HR, Engineering

Implementation:
  • Department-specific workspaces
  • Sales workspace: Lead qualification chatbots
  • Support workspace: Customer help assistants
  • HR workspace: Employee onboarding tools
  • Cross-department collaboration when needed

SaaS Company with Environments

SaaS product with dev, staging, production

Implementation:
  • Separate workspaces for each environment
  • Development workspace: Testing and iteration
  • Staging workspace: Pre-production validation
  • Production workspace: Live customer-facing AI
  • Controlled promotion between environments

Why Workspaces Matter

The organizational benefits of workspace-based architecture

Reduced Chaos

No more mixing client projects or confusing which chatbot belongs to which campaign.

Faster Onboarding

New team members get access to specific workspaces only, not everything at once.

Better Security

Client A cannot see Client B's data. Department-specific knowledge stays isolated.

Scalable Growth

Add 10 new clients or 100 new locations without organizational overhead.

Audit-Ready

See who created what, when changes were made, and who has access to what.

Billing Clarity

Track usage per workspace for accurate client billing or cost allocation.

Technical Details

Enterprise-grade workspace infrastructure

Isolation & Security

  • Complete data isolation between workspaces
  • Sources cannot be shared across workspaces
  • Role-based access control (RBAC)
  • Activity logs per workspace
  • API keys scoped to workspaces

Collaboration

  • Real-time multi-user editing
  • Change history and version tracking
  • Team member presence indicators
  • Comment and annotation system
  • Notification system for updates

Management

  • Unlimited workspaces (plan-dependent)
  • Workspace-level settings and branding
  • Transfer ownership between users
  • Archive or delete workspaces
  • Duplicate workspace as template

Analytics & Reporting

  • Per-workspace usage analytics
  • Conversation volume per workspace
  • Team member activity tracking
  • Cost allocation reports
  • Export workspace data

Frequently Asked Questions

Everything you need to know

How many workspaces can I create?

You can create unlimited workspaces on our Pro and Max plans. The Plus plan is limited to one workspace. All plans include a 7-day free trial.

Can I move projects between workspaces?

Currently, projects (chatbots, tools) are scoped to a specific workspace for security reasons. You would need to recreate them in the new workspace.

How do permissions work?

We use role-based permission matrixes across entity types. Roles include Owner, Admin, Contributor, Reader, and Guest. Effective permissions are computed from role capability + entity capability (where applicable) + plan/feature gates.

Is billing separate per workspace?

No, billing is centralized at the Organization level. One subscription covers all your workspaces and usage.

Can I invite external clients?

Yes. Most teams invite clients as Readers so they can review progress and analytics without changing configurations.

Can Admin transfer chatbots, tools, or assistants between scopes?

By default, transfer is role-capped. Admin can manage most actions, but transfer is restricted unless explicitly granted.

Where can I find the full permission matrix?

See the Workspace Permissions Matrix in Help Center for role-by-role coverage across chatbots, tools, assistants, prompts, and personas.

Still have questions?

Contact our support team

Ready to Organize Your AI Projects?

Start with workspaces today. Keep projects isolated, teams organized, and scale effortlessly.