Team collaboration
Bring your colleagues in, set roles, and track what got done.
Team collaboration
Workspace members share workrooms, agents, and the credit pool. Roles control who can change what.
The 30-second version
Invite your team via Settings → Team. Each user has a role: owner, admin, member, or viewer. Members share the same workspace, agents, custom agents, export profile, and credit balance. The Activity page (an audit_log-backed view) shows every change — who created which workroom, who exported what, who edited an agent.
Why this matters
A 3–30 person agency runs on overlapping responsibility. The senior strategist drafts the proposal, a junior writes the weekly report, the founder approves anything client-facing. AtelyaOS is built around that — a shared workspace with roles, not separate per-user accounts.
The shared credit pool means you don't have to think about per-user budgets. The activity log means you don't have to ask "who edited Aurora's agent yesterday?" — you can see it.
How it works
Roles
Each user belongs to one workspace and has one role:
| Role | Can do |
|---|---|
owner | Everything. There is one owner per workspace. |
admin | Everything except changing the owner. Can manage billing and members. |
member | Create workrooms, run agents, export deliverables. |
viewer | Read-only access to workrooms and deliverables. |
member is the default for new invites. Only owner and admin can change billing, manage integrations, or invite/remove users.
Inviting your team
From Settings → Team, click Invite. Send an email invite; the recipient sets up their account and lands directly in your workspace. The number of seats you can fill is capped by your plan:
| Plan | Max users (max_users) |
|---|---|
| Free Trial | 1 |
| Solo | 1 |
| Starter | 2 |
| Pro | 5 |
| Growth | 15 |
| Agency | Unlimited |
See pricing for current rates.
[SCREENSHOT: team settings showing member list and invite button]
Shared resources
Inside a workspace, every member sees:
- All workrooms (subject to read permissions).
- All custom agents and their Style Memory profiles.
- The export profile.
- The credit balance and usage.
Workrooms are not per-user; they're per-workspace. Two members can open the same workroom and watch the Composer run.
Activity log
The Activity page surfaces a workspace-wide stream of events from audit_log — workroom created, agent edited, export downloaded, member invited, billing changed. Use it to:
- Audit who exported a particular deliverable.
- Trace why a custom agent's Style Memory changed.
- See the full history of a workroom in one place.
Each workroom also has a per-resource activity tab on its detail page.
Approvals
Per-task approval blocks exist in the workroom task model — when an agent's plan includes one, that task pauses until a member with the right role grants it. This is built into the agent task graph, not a separate "team approval workflow." A multi-step approval workflow per workroom (e.g. "two members must approve before export") is coming soon.
Common pitfalls
- Treating
vieweras "junior." Viewers can't run workrooms. If a junior writes drafts, they needmember. - Adding everyone as
admin. Admin can change billing. Reserve admin for the people who own the budget. - Hitting the seat cap mid-quarter. Solo and Starter cap members tightly. If you have 3+ writers, plan to be on Pro or higher.
- Looking for per-user credits. Credits are workspace-wide. If usage is uneven across the team, look at the Activity log to see who's spending and why.
What's next
- Multi-workspace — when one workspace isn't enough.
- Pricing plans — seat caps per tier.
- Saved-time dashboard — aggregate usage across the team.