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.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.
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
Team Separation
Isolate different teams (Marketing, Sales, Engineering) with their own resources and access
Environment Separation
Maintain separate workspaces for Development, Staging, and Production
Client Projects
Create dedicated workspaces for different clients or customer projects
Compliance Boundaries
Separate workspaces for different compliance requirements or data classifications
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:- OAuth Apps
- API Keys
- Credentials
- Google Workspace
- Microsoft 365
- Slack
- GitHub
- And more…
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.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.
Creating a Workspace - Option 1
Creating a Workspace - Option 2
Editing a Workspace
Navigate to Workspace Control
- From ‘Workspace Control’ on the bottom of the sidenav
- by clicking on a Workspace from the list of Workspaces in the Settings
Workspace Roles
Different roles have varying levels of access within a workspace:| Role | Description | Permissions |
|---|---|---|
| Admin (Owner) | Full administrative control | All permissions, can delete workspace |
| Admin | Administrative access | Manage users, settings, billing, but cannot delete workspace |
| Editor | Build and deploy | Create/edit flows, agents, and knowledge bases |
| Viewer | Read-only access | View workflows and results, no modifications |
You can also create custom workspace roles and define the permissions for each. To learn more, see Permissions & roles.
Multi-Workspace Patterns
Noxus provides the freedom for users to use Workspaces in multiple ways. Some recommended patterns include:- Development lifecycle
- Team separation
- Client segregation
Create separate workspaces for each environment:Development workspace
- Experimentation and testing
- Rapid iteration without risk
- Test data and mock integrations
- Team sandbox environment
- Pre-production testing
- Integration testing with real-ish data
- User acceptance testing
- Performance validation
- Live, customer-facing deployments
- Production data and integrations
- Monitored and secured
- Change control processes
This pattern ensures changes are thoroughly tested before reaching production, reducing risk and improving reliability.
Best Practices
- Workspace organization
- Security
- Resource management
- 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.
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
Importing Resources
Import exported resources into another workspace:- Import flow definitions
- Recreate agent configurations
- Import knowledge base settings
- Reconfigure integrations with new credentials