Organizations & Workspaces

Understanding Axellero Studio's organizational structure is essential for effectively managing your projects and teams.

Platform Hierarchy

Studio uses a three-tier structure to organize work:

Level	Scope	Contains	Typical Use Cases
Organizations	Company/Team	Multiple workspaces, organization settings, member management, billing	Companies, departments, client accounts for agencies
Workspaces	Project/Environment	Multiple applications, workspace configurations, collaboration settings	Individual projects, dev/staging/prod environments, client work areas
Applications	Individual Studio Project	AI agents, workflows, integrations, database entities	Specific automation projects, microservices, business applications

Organizations are the top-level containers that provide:

Feature	Description	Status
Member Management	Organization-wide user access control	Available
Billing & Subscriptions	Centralized payment and usage tracking	Coming Soon
Global Settings	Organization-wide configurations	Coming Soon
Workspace Governance	Control over workspace creation and management	Available

Workspaces provide project-level organization with:

Feature	Description	Status
Environment Management	Separate dev, staging, production environments	Available
Team Collaboration	Project-specific team access and permissions	Available
Resource Sharing	Shared integrations, connectors, and configurations	Available
Project Settings	Workspace-specific configurations and policies	Coming Soon

Applications are individual Studio projects containing:

Component	Purpose	Management
AI Agents	Conversational intelligence and automation	Agent configuration, conversation flows, training data
Workflows	Process automation and data transformation	Visual workflow design, node configuration, execution monitoring
Integrations	External system connections	Connector setup, authentication, data mapping
Database Entities	Data models and schema design	Entity relationships, field definitions, validation rules
Application Settings	App-specific configuration	Authentication, permissions, API access, deployment options

Level	Best Practices	Avoid
Organizations	Separate by legal entity, major business unit, or client	Mixing unrelated teams or projects in one organization
Workspaces	Group by project, product line, or environment	Creating too many single-application workspaces
Applications	One distinct business function or service per application	Mixing unrelated functionality in one application

Role Level	Organization Access	Workspace Access	Application Access
Owner	Full admin rights, billing management	All workspaces, creation/deletion rights	All applications, full configuration
Admin	Member management, settings configuration	Workspace administration, member management	Application configuration, deployment
Developer	Read access to organization settings	Development and testing access	Build, test, and modify applications
Viewer	Organization overview only	Read-only workspace access	View applications and execution logs

Join or Create Organization: Start with the appropriate organizational container
Set Up Workspace: Create a workspace for your project
Create Application: Set up your first Studio application
Configure Settings: Set up organization and workspace preferences

This structure provides flexibility for teams of all sizes while maintaining clear boundaries and access controls.