How do I add someone to my team?

Open Billing, click Manage team, invite the person's GitHub username, then assign them a seat after they sign in. Solo and Agency both include team management. You do not need to upgrade to Agency to invite a teammate. Joining the organisation and receiving a paid seat are separate steps.

Before you start

You must be an owner or admin of the organisation and have an unassigned seat. Use the teammate's actual GitHub username, not their email or an editable display name. Choose member unless they genuinely need administrative access.

An active paid Solo or Agency account gets a team automatically if it does not already own or administer one. Existing affected buyers get their team when they next open Codus Cloud while signed in. A newly created team includes the buyer's own seat: a two-seat Solo plan has room for the buyer and one teammate. Existing teams and their assignments are preserved.

Assigning existing capacity does not buy another seat. Buying capacity or enabling paid modules can charge the plan and must be reviewed separately.

Steps

1. Sign into Billing with the GitHub account that bought the seats. Click Manage team, select the correct organisation and open Pending invitations.
2. Enter the GitHub username, select the role and click invite.
3. Check that the intended @username appears in the pending list. Tell the teammate to sign in; do not assume an email invitation was delivered.
4. Ask them to open Codus Cloud and sign in using that exact GitHub account.
5. Once they appear as a member, find them in Seats and click Assign seat.
6. Ask them to sign into the desktop with the same GitHub account and confirm it opens.

If a step fails

• You bought Solo seats but cannot invite anyone: reopen Billing with the purchasing GitHub account, then choose Manage team. You can also open Team directly. If it still reports no admin access, contact support with the error. Buying Agency is not the fix for missing team access.
• The person is not listed: check the invited username and whether they completed sign-in. Do not create another account merely because their company email changed.
• No assignment is available: check plan capacity and the error shown. Do not revoke someone else's seat without confirming the effect.
• They joined but cannot use Codus: membership alone is not access. Check their seat or other valid grant and their signed-in account.
• A module is missing: modules have separate access rules, including promotions and grants. Read the activation price before confirming a paid addition.

Revoke seat removes that team's assignment. It does not cancel the organisation's plan or a teammate's separately owned subscription, and it does not prove every other source of that person's access has ended.

How do I know it worked?

The teammate appears with a seated badge, the assignment counter reflects it and their desktop opens under the invited GitHub account. A pending invitation alone is not a completed seat assignment.