Teams
Teams in ORGN Studio — collaboration boundaries, members, billing, usage, and GitHub integration via id-orgn.
Teams define how people collaborate inside ORGN Studio. Every project belongs to a team, and all work — tasks, worktrees, sessions, context, and changes — lives within that team boundary.
If you work with multiple clients, products, or internal initiatives, teams keep those environments isolated. A repository imported into one team is not visible to members of another team unless they are explicitly added.
Platform access requires id-orgn sign-in (Studio shows the UNLOCK button; Sign in with GitHub is available at id-orgn). The ORGN GitHub App is an additional step for repository permissions. See SSO.
Team profile
Open Team Settings from the Studio settings sidebar.
Here you can:
- View the team name and creation date
- Edit the team name with Edit
The team name appears on project dashboards, session headers, and collaboration views. If you belong to multiple teams — for example, one for client work and another for internal R&D — the name clarifies which workspace you are in.
Renaming a team does not affect projects, repositories, or configuration inside it.
Members
The Members section lists everyone on the team with role and email.
Each entry shows:
- Display name and avatar
- Role (for example, Owner)
- Email address
Inviting members
Click Invite in the Members section, enter an email address, and send the invitation.
When the invitee accepts, they sign in through id-orgn (same SSO as existing members) and gain access to the team's projects. They can start worktrees, join sessions, and collaborate on tasks immediately.
Pending invitations
Sent-but-not-accepted invitations appear under Pending Invitations with email, sent date, and status. Revoke invalidates the invite link before acceptance.
Billing
The Team Billing page manages credit balance, plan, and top-ups.
Current plan
The page shows your active plan and summary:
- Billing model — usage-based on pay-as-you-go
- Team members — unlimited on standard pay-as-you-go
- Platform access — included
Canonical plan amounts are on orgn.com/pricing and Pricing. In-app plan cards may show legacy tiers (for example an inactive "Pro" tier) that lag the marketing site.
Treat orgn.com/pricing as source of truth for dollar amounts. Enterprise is $2,150/seat/month with 400 agent run hours/seat/month — contact sales via Enterprise, not self-serve upgrade buttons.
ORGN credits
Credits fund workspace runtime, worktrees, and agent activity. The billing page shows balance, used amount, and remaining credits.
Top up anytime or Redeem Voucher to add credits from a code.
Adding credits
- Add Credits — one-time credit pack purchase
- Redeem Voucher — apply a promotional or enterprise voucher code
Recent activity
Recent Activity logs credit events — purchases, redemptions, usage deductions per worktree or project — with timestamps and amounts. Open All Events for full history.
Usage
Team Usage monitors resource consumption over time.
Summary metrics (last 30 days)
- Agent runs — total agent executions
- Sessions — chat/session count across projects
- Total tokens — cumulative inference tokens
- Total cost — aggregate spend
Token consumption by project
Time-series chart of token usage per project (typically last 7 days). Use this to spot projects driving disproportionate inference spend.
Workspace runtime
Per-project table:
| Column | Meaning |
|---|---|
| Project | Name and identifier |
| Resources | CPU and memory (for example 4 CPU / 8 GB) |
| Hours | Runtime logged |
| $/HR | Hourly rate for that configuration |
| Cost | Period total |
A Total row summarizes compute spend across active projects.
Sandbox costs
Billing for sandbox execution environments. Populates after workspaces have been used; otherwise shows an empty state.
GitHub integration
The GitHub settings page manages ORGN GitHub App access for imports, pushes, and agent git operations. This grants repository permissions — separate from Sign in with GitHub at id-orgn, which creates your ORGN identity.
| Action | Purpose |
|---|---|
| App Permissions | Review which repositories the ORGN GitHub App can access |
| GitHub Settings | Open GitHub's app settings in a new tab |
Repository access is controlled on GitHub (org install, repo allowlist). The modal shows connected accounts, organizations, and permitted repositories.
id-orgn owns GitHub tokens
Flow today:
- Sign in with id-orgn — Studio UNLOCK or CDE Continue with id-orgn (PKCE OAuth). Sign in with GitHub is available on the id-orgn login page.
- Connect the ORGN GitHub App from Team/Account settings when you need private repo access for import, clone, or push.
- id-orgn stores and refreshes GitHub OAuth tokens; ORGN products request them through id-orgn internal APIs.
If GitHub App access is missing, import and git operations prompt you to connect — even if you already signed in with GitHub at id-orgn.
Sign in with GitHub at id-orgn proves who you are. The ORGN GitHub App grants which repositories ORGN can clone and push to. Both flow through id-orgn but serve different purposes.
Deleting a team
The Danger Zone permanently deletes the team and:
- All associated projects
- Tasks and worktrees
- Sessions and changes
- Shared configuration and billing history
This cannot be undone. Notify members and export anything needed before deletion.
How team boundaries affect access
Every project interaction requires:
- Valid id-orgn authentication
- Membership in the team that owns the project
Starting a worktree, running an agent, or applying file changes validates both conditions. Expired sessions require re-authentication through id-orgn before work continues.
This structure keeps collaboration predictable — teams scale safely, onboard contributors with appropriate access, and maintain separation between independent codebases or business units.
Related pages
- SSO — id-orgn PKCE across Studio, CDE, Gateway, Scanner
- Pricing — credits, markup, enterprise seats
- Enterprise — VPC, air-gap, procurement
- Glossary — Team, worktree, Session