One platform.
A workspace per squad.
Big engineering orgs don’t run on a single shared task pool. AGENA Workspaces split your org into per-squad scopes — Backend, Frontend, Mobile, Payments — each with its own tasks, repos, members, AI agents and run history. Invite-code joins, role-based titles, audit trail.
Click the switcher in the sidebar to swap context. Settings page lets workspace owners manage members, titles and the 6-character invite code.
6VL265How it works
- 1Sign up — your default workspace is auto-createdNew orgs land on a guided onboarding step that lets you pick: continue with the default, create another (Backend, Mobile, Payments), or join an existing workspace via an invite code from a teammate.
- 2Invite teammates with a 6-character codeEvery workspace owns a unique short code (no ambiguous chars like 0/O/1/I). Share it in Slack or email — recipients paste it during signup or in /dashboard/workspaces and join instantly.
- 3Assign per-workspace titlesSame person, different title per squad: "Senior Developer" in Backend, "Reviewer" in Payments. Titles surface on tasks and reviews; they’re free-text so non-engineering teams can use whatever your HR system uses.
- 4Tasks + repos scope down automaticallyWhen you import a Jira sprint, Sentry error, or Azure DevOps work item into Workspace X, that task lives there. Members of Workspace Y don’t see it; org owners still get the cross-workspace dashboard.
- 5Audit + rotate codes when people leaveCodes are persistent until rotated. One click on /dashboard/workspaces regenerates the code; old code stops working immediately. Member removals and joins are tracked.
Why workspaces beat one big shared org
FAQ
Do existing organizations need to do anything?
No. The migration auto-creates one default workspace per existing org and backfills every task, repo and member to it. Existing users see no change in behavior — they just get the new switcher in the sidebar with a single workspace inside.
Can I be in multiple workspaces?
Yes — and even in workspaces from different organizations if you’ve been invited. The switcher lets you flip between them; tasks, repos and AI run history follow your active workspace.
How does the 6-character invite code work?
Each workspace owns one. Share it (Slack, email, in person) and the recipient pastes it during signup or in /dashboard/workspaces. We avoid ambiguous characters (0/O/1/I) so no one mistypes it.
What happens if a teammate leaves?
Workspace owners can remove them with one click; the underlying user account stays. If you’re worried about the invite code being public, click "Regenerate code" — the old one stops working immediately.
How do permissions per title work?
Org-level permissions (owner / admin / member / viewer) still apply. The "title" field is a per-workspace free-text label that surfaces on tasks, reviews and the team page — useful for HR labels ("Senior Backend Developer", "QA Lead") that the existing role enum doesn’t carry.