Teams & Collaboration

Teams define how people collaborate inside Origin. Every project belongs to a team, and all work, tasks, trials, 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 to it.

Team Profile

The Team Settings page begins with the Team Profile section.

Here you can:

• View the team name and when it was created
• Edit the team name using the Edit button

The team name appears across 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 makes it immediately clear which workspace you are operating in.

Updating the team name is useful during rebranding, restructuring, or when shifting a team's scope from one product line to another. Renaming does not affect projects, repositories, or any existing configuration inside the team.

Members

The Members section lists everyone currently on the team, along with their assigned role and email address.

Each member entry shows:

• Their display name and avatar
• Their role (e.g., Owner)
• Their email address

Inviting Members

To add someone to the team, click the Invite button in the Members section. Enter their email address and send the invitation.

Once accepted, the new member gains access to the team's projects. This is commonly used when onboarding a new engineer to an active codebase, after accepting the invite, they can immediately see team projects, start trials, and collaborate on tasks.

Pending Invitations

Invitations that have been sent but not yet accepted appear under Pending Invitations. Each entry shows:

• The invited email address
• The date the invitation was sent
• Its current status (Pending)

You can Revoke any pending invitation directly from this view if access is no longer needed before the person joins. Revoking immediately invalidates the invite link.

Billing

The Team Billing page manages your credit balance, active plan, and upgrade options.

Current Plan

The top of the page shows your active plan, currently Pay as you go, along with a summary of:

• Billing Model: Usage-based
• Team Members: Unlimited
• Platform Access: Included

Origin Credits

Credits are the currency used to run workspaces, trials, and agent tasks inside Origin. Once a team is selected, the credits section shows your current balance, how many have been used, and how many remain.

Credits are consumed per trial created and per workspace run. You can top up at any time or redeem a voucher code to add credits to your team balance.

Available Plans

You can compare and switch between plans directly from the billing page without leaving the interface.

Adding Credits

Regardless of plan, you can top up your credit balance at any time:

• Add Credits: Purchase a one-time credit pack for new runs, workspaces, and trials
• Redeem Voucher: Enter a voucher code to add credits to your current team balance

Recent Activity

The Recent Activity section logs the latest credit events for your team, including purchases, redemptions, and usage deductions per trial or project. Each entry shows the event type, a reference ID, the timestamp, and the credit amount consumed or added. Click All Events to see the full history.

Usage

The Team Usage page lets you monitor resource consumption across your team in detail.

Summary Metrics

At the top, four metrics give you a quick snapshot of team activity over the last 30 days:

• Agent Runs: Total number of agent executions
• Sessions: Total sessions opened across all projects
• Total Tokens: Cumulative token usage across all projects
• Total Cost: Aggregate spend for the period

These numbers update as work happens and give team leads and security reviewers a fast read on overall activity.

Token Consumption by Project

This section shows a time-series chart of token usage broken down by project over the last 7 days. Each project appears as a separate line or color in the chart.

This is useful for identifying which projects are driving the most inference activity, for example, if one repository is consuming a disproportionate share of tokens, you can investigate whether agent tasks are running efficiently or whether context is being over-loaded.

Workspace Runtime

The Workspace Runtime table breaks down compute usage per project with the following columns:

• Project: The project name and identifier
• Resources: CPU and memory allocated (e.g., 4 CPU / 8 GB)
• Hours: Total runtime hours logged
• $/HR: Hourly rate for that resource configuration
• Cost: Total cost for the period

The table includes a Total row summarizing cost across all active projects. This gives infrastructure and finance stakeholders a clear view of compute spend without needing access to separate billing dashboards.

Sandbox Costs

The Sandbox Costs section shows billing details specific to sandbox execution environments. This section populates once workspaces have been actively used. Until then, it displays an empty state indicating no sandbox cost data is available yet.

Deleting a Team

The Danger Zone at the bottom of Team Settings includes the option to permanently delete the team.

Deleting a team removes:

• All associated projects
• Tasks and trials
• Sessions and changes
• Shared team configuration and billing history

This action cannot be undone. Before deleting, ensure that no active work needs to be preserved and that all members have been notified.

In practice, team deletion is typically used when a client engagement has ended, a sandbox team was created for temporary testing, or a workspace is no longer needed.

How Team Boundaries Affect Access

Team membership is required to access any project inside Origin.

For any project interaction to succeed:

1. You must be authenticated.
2. You must belong to the team that owns the project.

Every action, starting a trial, running an agent, applying file changes, is validated against your current team membership. If either condition is not met, the action cannot proceed.

This structure keeps collaboration predictable. Teams can scale safely, onboard contributors with the right level of access, and maintain strict separation between independent codebases or organizational units.