> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noxus.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces

> Organize teams, projects, and resources in isolated environments

## What is a Workspace?

A Workspace in Noxus is an isolated environment that contains a set of your AI resources, workflows, agents, knowledge bases, and team members. Workspaces provide organizational boundaries, resource isolation, and access control for teams and projects.

<Note>
  Think of a workspace as a container for everything related to a specific team, department, or project. Each workspace operates independently with its own resources, users, and settings.
</Note>

### Key Concepts

**Resource Separation** - Each workspace maintains its own flows, agents, knowledge bases, and data, completely isolated from other workspaces.

**Independent Configuration** - Workspaces have separate settings, integrations, model configurations, and API keys.

**Access Boundaries** - Users and permissions are scoped to individual workspaces, ensuring proper access control.

**Billing Isolation** - Usage and costs are tracked separately per workspace for clear accounting and charge-back.

### Use Cases

<CardGroup cols={2}>
  <Card title="Team Separation" icon="users">
    Isolate different teams (Marketing, Sales, Engineering) with their own resources and access
  </Card>

  <Card title="Environment Separation" icon="layers">
    Maintain separate workspaces for Development, Staging, and Production
  </Card>

  <Card title="Client Projects" icon="briefcase">
    Create dedicated workspaces for different clients or customer projects
  </Card>

  <Card title="Compliance Boundaries" icon="shield">
    Separate workspaces for different compliance requirements or data classifications
  </Card>
</CardGroup>

***

## Workspace Resources

Each workspace is an isolated container for the things you build and the access controls around them.

### AI tools (flows, agents, knowledge bases)

Everything you create is scoped to the workspace, including:

* Definitions and versions.
* Runs, history, and analytics.
* Scheduled triggers and deployments.

### Integrations

Connections to external services, including:

* OAuth connections (Google, Microsoft, etc.).
* API credentials and authentication settings.
* Integration-specific configuration.
* Usage tracking per integration.

### Users & Permissions

Workspace members and what they’re allowed to do, including:

* Invitations and member management.
* Role-based access control.
* Permission assignments.
* Activity and audit logs.

***

### Integrations

Manage connected external services:

<Tabs>
  <Tab title="OAuth Apps">
    * Google Workspace
    * Microsoft 365
    * Slack
    * GitHub
    * And more...
  </Tab>

  <Tab title="API Keys">
    * Custom API integrations
    * Database connections
    * Third-party services
    * Webhook endpoints
  </Tab>

  <Tab title="Credentials">
    * Secure credential storage
    * Rotation policies
    * Access audit logs
    * Sharing controls
  </Tab>
</Tabs>

***

## Managing Workspaces

A user can be on multiple Workspaces at the same time. They can use the Workspace Selector on the top of the sidenav to switch between them. On click, all views and resources update to the selected workspace.

<Note>
  Users can only switch to Workspace they have access to. Platform admins **can access** all workspaces in the platform, wven if not directly set as users on them.
</Note>

### Creating a Workspace - Option 1

<Steps>
  <Step title="Navigate to Workspace Selector">
    Click on the workspace name in the top of the sidenav
  </Step>

  <Step title="Create New Workspace">
    Select "Create New Workspace" from the dropdown
  </Step>

  <Step title="Configure Workspace">
    Set name, description, and color
  </Step>
</Steps>

### Creating a Workspace - Option 2

<Steps>
  <Step title="Navigate to Settings">
    Click on your name in the bottom of the sidenav and select Settings
  </Step>

  <Step title="Go to the Workspaces tab">
    Select "Workspaces" option from the sidenav
  </Step>

  <Step title="Click 'New workspace'">
    Click on the button on the top right of the page
  </Step>

  <Step title="Configure Workspace">
    Set name, description, and color
  </Step>
</Steps>

<Warning>
  Some billing plans limit how many workspaces a user can create. Enterprise plans include unlimited workspaces.
</Warning>

### Editing a Workspace

<Steps>
  <Step title="Navigate to Workspace Control">
    * From 'Workspace Control' on the bottom of the sidenav<br />
    * by clicking on a Workspace from the list of Workspaces in the Settings
  </Step>

  <Step title="Invite Team Members">
    Add users and assign roles.
  </Step>

  <Step title="Configure Integrations">
    Set up API keys, integrations, and defaults
  </Step>
</Steps>

Some actions depend on the role of a user.

### Workspace Roles

Different roles have varying levels of access within a workspace:

| Role       | Description                   | Permissions                                           |
| :--------- | :---------------------------- | :---------------------------------------------------- |
| **Admin**  | Full workspace control        | All permissions including `workspace_admin`           |
| **Editor** | Build and deploy AI resources | Create/edit/delete flows, agents, and knowledge bases |
| **Reader** | Run and query resources       | `flows_run`, `agents_run`, `kbs_query`                |

<Note>
  You can create custom workspace roles with any combination of permissions. To learn more, see [Permissions & roles](/platform/concepts/permissions).
</Note>

***

## Multi-Workspace Patterns

Noxus provides the freedom for users to use Workspaces in multiple ways. Some recommended patterns include:

<Tabs>
  <Tab title="Development lifecycle">
    Create separate workspaces for each environment:

    **Development workspace**

    * Experimentation and testing
    * Rapid iteration without risk
    * Test data and mock integrations
    * Team sandbox environment

    **Staging workspace**

    * Pre-production testing
    * Integration testing with real-ish data
    * User acceptance testing
    * Performance validation

    **Production workspace**

    * Live, customer-facing deployments
    * Production data and integrations
    * Monitored and secured
    * Change control processes

    <Note>
      This pattern ensures changes are thoroughly tested before reaching production, reducing risk and improving reliability.
    </Note>
  </Tab>

  <Tab title="Team separation">
    Organize by team or department:

    **Marketing workspace**

    * Content generation workflows
    * Social media automation
    * Campaign analytics
    * Marketing team access only

    **Sales workspace**

    * Lead qualification agents
    * CRM integrations
    * Sales enablement workflows
    * Sales team access only

    **Customer support workspace**

    * Support chatbots
    * Ticket routing workflows
    * Knowledge base for support articles
    * Support team access only
  </Tab>

  <Tab title="Client segregation">
    For agencies or consultants managing multiple clients:

    **Client A workspace**

    * Client-specific workflows and agents
    * Client A's integrations and data
    * Isolated billing and usage tracking
    * Controlled access for client team

    **Client B workspace**

    * Separate resources for Client B
    * Independent configurations
    * Isolated data and processing
    * Client B team access

    <Warning>
      Always use separate workspaces for different clients to ensure data isolation, security, and compliance with client agreements.
    </Warning>
  </Tab>
</Tabs>

***

## Best Practices

<Tabs>
  <Tab title="Workspace organization">
    * **Use descriptive names**: Name workspaces clearly to indicate their purpose (e.g., "Acme Corp - Production", "Marketing - Dev").
    * **Separate environments**: Always maintain separate workspaces for development and production.
    * **Limit production access**: Restrict production workspace access to essential team members only.
    * **Document workspace purpose**: Use the description field to explain the workspace's purpose and any special configurations.
  </Tab>

  <Tab title="Security">
    * **Enable MFA**: Require multi-factor authentication for all workspace members.
    * **Review access regularly**: Audit user access quarterly and remove unnecessary permissions.
    * **Use service accounts**: Create service accounts for API access rather than using personal credentials.
    * **Rotate credentials**: Regularly rotate API keys and integration credentials.
  </Tab>

  <Tab title="Resource management">
    * **Consolidate when possible**: Don't create unnecessary workspaces; use permissions within a workspace when appropriate.
    * **Monitor usage**: Regularly review workspace usage and costs.
    * **Clean up unused resources**: Archive or delete workflows and agents that are no longer needed.
    * **Set naming conventions**: Establish consistent naming patterns for resources across workspaces.
  </Tab>
</Tabs>

***

## Workspace Migration

### Exporting Resources

Export flows, agents, and configurations from one workspace:

* Export individual flows as JSON
* Export knowledge base configurations
* Export agent definitions
* Document integration settings

<Warning>
  Knowledge Bases data will need to be reingested when they are imported into a Workspace. If the amount of files is too big, it might be impossible to export a Knowledge Base.
</Warning>

### Importing Resources

Import exported resources into another workspace:

* Import flow definitions
* Recreate agent configurations
* Import knowledge base settings
* Reconfigure integrations with new credentials

<Warning>
  Integrations and credentials must be reconfigured in the target workspace as they are not exportable for security reasons.
</Warning>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Users" icon="user" href="/core/concepts/users">
    Learn about user management and permissions
  </Card>

  <Card title="Flows" icon="workflow" href="/core/concepts/flows">
    Start building flows in your workspace
  </Card>

  <Card title="Agents" icon="bot" href="/core/concepts/agents">
    Create and develop AI agents for your team
  </Card>

  <Card title="Knowledge Bases" icon="folder" href="/core/concepts/knowledge-bases">
    Intelligent data repositories to enhance your tools
  </Card>
</CardGroup>