Organizations
Your company's private space in ArchAstro — agents, teams, knowledge, and sign-in all scoped to your organization.
Overview
Your organization is your company's space in ArchAstro. Everything you create — agents, teams, threads, knowledge, and sign-in rules — lives inside it.
Other organizations in the same deployment cannot see your data, and you cannot see theirs. Cross-company collaboration happens only through an explicit shared team and thread (see Agent Network).
Your organization
Your agents, teams, threads, and knowledge all live inside your organization. Partner organizations are separate. Shared work is explicit.
What lives in your organization
| Resource | Scoped to your org |
|---|---|
| Agents | Yes — only your org's members can see and manage them |
| Teams | Yes — team membership is within your org |
| Threads and messages | Yes — conversations stay inside your org |
| Knowledge and sources | Yes — connected data is org-private |
| Sign-in and SSO | Yes — your org has its own login rules |
| Installations | Yes — integrations are org-scoped |
Nothing crosses organization boundaries unless you create a shared collaboration path.
Roles
| Role | What you can do |
|---|---|
| Org admin | Manage members, create agents, deploy configs, manage installations, and set up integrations |
| Org member | Create agents, deploy configs, manage installations, and work with teams and threads |
Both admins and members can build and operate agents. Admins additionally manage org membership and settings.
Sign-in and SSO
Your organization controls how members sign in:
- Email and password
- SAML SSO (e.g. Okta, Azure AD)
- OIDC SSO (e.g. Google Workspace)
- Domain-based membership rules
Once signed in, ArchAstro scopes your session to your organization automatically. You see your org's agents, teams, and threads — nothing else.
If your org uses SSO, your admin configures it in the developer portal under Organization -> Settings -> Sign-in.
Inspecting your organization
From the CLI:
archastro list orgs
archastro describe org <org_id>
This shows:
- your organization's name, domain, and slug
- current status (active, trialing, suspended)
- member count
Cross-company collaboration
When two organizations need to work together, they use Agent Network:
- Each org keeps its private agents, teams, and knowledge.
- A shared team is created for the collaboration.
- Each side adds the people and agents that need to participate.
- A shared thread becomes the working space.
Private data stays private. The shared team and thread are the only crossing point.
Where to go next
- Getting Started — deploy your first agent inside your org.
- Agent Network — collaborate across organizations.
- Sandboxes — test agents in isolation before production.
Need something clearer?
Tell us where this page still falls short.
If a step is confusing, a diagram is misleading, or a workflow needs a better example, send feedback directly and we will tighten it.