Hexel Studio uses a three-level hierarchy to isolate resources and control access.Documentation Index
Fetch the complete documentation index at: https://hexelstudio.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Hierarchy
Organization
Your company or team. Contains all users, billing, and workspaces. Each organization is fully isolated from others.
Workspace
A project or team within your organization. Use workspaces to separate different products, teams, or use cases.
What lives where
| Resource | Scoped to |
|---|---|
| Users, roles, policies | Organization |
| Service users, API keys | Workspace + Environment |
| Agents, instances, sandboxes | Environment |
| Usage records, audit logs | Organization |
Data isolation
| Level | Isolation | Example |
|---|---|---|
| Organization | Complete | Company A cannot see Company B’s data |
| Workspace | Logical | Team Alpha’s agents are separate from Team Beta’s |
| Environment | Logical | Production agents are separate from development agents |
Authentication context
Your API key or OAuth client is scoped to a specific workspace and environment. All API calls are automatically routed to the correct context.Recommendations
| Practice | Why |
|---|---|
| One organization per company | Simplifies billing and user management |
| One workspace per project or team | Keeps resources organized |
| Separate environments for each stage | Prevents production and development from interfering |
| Separate API keys per environment | Limits blast radius if a key is compromised |

