Teams

A team gives every member Codz Pro and the team one page on codz.com with its members and the usage they sync to it. You create it, buy seats, and invite people with a link.

A team buys Pro ($20) or Max ($200) for each seat, per person per month, for up to 100 seats. Every account also has a personal account, Personal, which is where your synced usage goes until you choose a team.

Create a team

Open Teams and choose Create team. Settings, Billing & Invoices and Pricing lead to the same setup:

1. Enter a Team name and Team URL. Codz suggests an address from the name and checks availability. The URL is codz.com/orgs/your-team.
2. Choose how many Pro and Max seats to buy, including one for yourself, pick Your seat, and review payment. Web Pro subscribers review the prorated upgrade before confirming; other accounts pay in Stripe Checkout. Apple-billed Pro stays active until you cancel it with Apple.
3. Once seats are active, optionally enter teammates’ email addresses, choose Member or Admin and a Pro or Max Seat, and send invitations. Skip for now or Finish setup opens the team page.

You become the owner. Payment is required to complete setup; invitations can wait. If Checkout is canceled, your team is saved and Continue setup resumes payment from Teams. Pending confirmation never enables invitations or asks you to pay again.

Buy seats

In the Billing section of the team’s page:

1. Enter the number of Pro and Max seats and click Purchase seats.
2. Pay in Stripe Checkout.

Back on the page, Codz confirms: Team seats are active. Every member now has Pro.

Every active member holds a Pro or a Max seat, you included, and each pending invitation reserves one of its plan. In Members, Move to Max or Move to Pro on a member’s or invitation’s row moves it to a free seat of the other plan. The Billing section shows how many seats are used, how many pending invitations hold, and when the subscription renews. Billing covers changing seats and the billing portal.

Invite people

Open Members in the dashboard sidebar or Settings ▸ Members on macOS, then select the team. This selection does not change where your usage syncs. Owners and admins choose Invite members:

1. Enter up to 100 email addresses separated by commas or new lines, choose Member or Admin, and click Send invitations.
2. Click Copy link and send the link to your teammate. Codz also emails it to that address when it can.

The link is shown only once and expires in 14 days. It works only for the email address you invited. Each address has its own result and delivery status. Successful invitations remain valid if another address fails. Resend invitation invalidates the previous link and returns a new link with a fresh 14-day expiry. A live invitation keeps its reserved seat; renewing an expired invitation requires an available seat. Revoke invitation stops a link working.

Your teammate opens the link, signs in with the invited address and clicks Accept invitation. If they are signed in with another address, the page offers Switch account.

If the page says “No seats of this plan are available. Add seats first.”, add seats of that plan in Billing and invite again.

Roles

Usage on the Mac and web shares the same access rules. Owners and admins get reporting coverage, budget pacing, adoption groups, plan fit and an alphabetical member table. A member sees their own contributions and anonymous peer dots only after at least five people report. Viewing a team does not change the destination selected for usage reporting.

A quiet seat is not automatically unused: the plan-fit note describes the windows Codz measured and their coverage. Linked merged work requires a confirmed merge; repository paths and pull request titles stay on the Mac. Team administrators can opt into a separate weekly email digest in Settings.

A team has one owner, and any number of admins and members. Invitations make admins or members; ownership only moves by transfer.

Owners and admins use a member’s row menu to choose Make Member or Make Admin. You cannot change your own role. The owner can choose Transfer ownership for another active member: that person becomes the owner and the previous owner becomes an admin.

Manage the directory

Search names or email addresses, filter by role or status, and click a column heading to sort. Owners and admins see Active, Pending invitations, Expired invitations, Suspended, Former members and directory-created Awaiting seat memberships. Export CSV exports the filtered rows. Ordinary members see the active directory and can leave through their own row.

Suspend ends team access immediately and frees the occupied seat. Reactivate requires available capacity and preserves the role. Remove and Leave team retain a former membership, its original join date and historical usage. Restore requires an available seat and defaults to Member; an admin can explicitly choose Admin. Confirmations explain these changes before they happen. Records deleted before this feature cannot be reconstructed.

The owner and the protected billing payer cannot be suspended or removed. Transfer ownership or cancel the payer’s team subscription first. Directory-managed memberships show the reason that changes are unavailable; provisioning and lifecycle changes stay with the directory provider.

Creating a team or managing billing from macOS opens the existing website flows.

Seats and Pro

Every active member has Codz Pro while the team subscription is active. On the Mac, Settings ▸ Account reads Codz Pro, through your team; on codz.com it reads Pro · via team.

• Changing seats. Update seats changes the Pro and Max counts in place. A change that adds seats is prorated immediately; one that only removes seats takes effect at the next renewal and isn’t credited. Neither plan can go below the members holding it: move or remove members first.
• More members than seats. Existing members keep access, but new invitations are blocked until you add seats.
• A payment problem. Every member loses the team’s Pro until it is fixed, unless they pay for Pro themselves. Owners and admins see The team subscription needs attention on the team’s page, with Fix billing.
• Leaving. A member who is suspended, leaves or is removed loses the team’s Pro, and if their sync pointed at the team, it goes back to Personal.

Suspension and removal do not change purchased seat quantity. Change billing explicitly on the team’s page.

A team seat and a personal Pro subscription are separate: joining a team doesn’t cancel a personal one.

Team usage and monthly targets

Open Usage on the web or Mac, then choose a team scope. Owners and admins see all team contributions; members see only their own. Viewing a scope does not change the reporting team.

An active paid team seat requires reporting metadata from connected providers. Codz automatically selects a sole eligible paid team, preserves an eligible existing destination, or asks you to choose when multiple teams are available. Personal cannot be chosen while team reporting is required. Enrollment backfills all available personal and unassigned history. Previously shared team activity remains attributed to that team after departure or a reporting change.

Overview leads with the team’s token budget against an even pace, then tokens by day, Charges and API value (never added together), models, plan windows and the alphabetical members table. Choose a period and filters, export CSV, or select a day to open Activity. Activity distinguishes identified requests from turn summaries and account events. Coverage and unavailable fields explain gaps in collection.

Owners and admins can set recurring monthly targets for the whole team or active individuals under Budgets, in tokens or API value. API value targets count what providers stated plus list-price estimates. Missing costs remain incomplete. Targets warn at 75%, 90% and 100% without blocking requests. Team warnings go to owners and admins; member warnings also go to that member. Members see their own targets.

Manage team provides team settings, seats and billing, with a link to the Members directory for invitations and lifecycle actions. Stripe checkout and billing portals open in the browser. Teams billed through a member's personal Stripe customer retain the payer-only billing restriction.

Activity metadata and daily history remain until account or team deletion. Prompts, answers, credentials and local file paths stay private. Offline collection remains on the Mac for later retries.

Leave or delete a team

• Leave. Any member except the owner can click Leave in their own row of the Members table. The owner transfers ownership first. Whoever pays for a team from their own account, after upgrading to it from Pro, can’t leave or be removed while its subscription bills them.
• Remove. Owners and admins click Remove in a member’s row. The owner can’t be removed.
• Delete. Only the owner can delete a team, from Delete team at the foot of its page, by typing its Team URL to confirm. Deleting it cancels any team subscription immediately and deletes the usage stored for the team. Members whose sync pointed at it go back to Personal.

Questions

Does the owner need a seat?

Yes. The owner is a member, and every active member holds a seat.

Can I invite before buying seats?

No. An invitation reserves a seat, so buy seats first.

Where do I rename the team?

Owners and admins change the Team name and Team URL under General on the team’s page. Changing the Team URL changes the team’s address.