Skip to main content

​
Inviting teammates

Owners and admins invite from the Team page in the sidebar. Enter an email, pick a role, and for members and clients pick the projects they should see. The invite email goes out immediately, and the project assignments fire automatically on their first sign-in. Nothing to configure after they accept. For owner and admin invites there’s no project picker. Those roles see every project in the org by definition.

​
What costs a seat

You pay for people who can edit. That’s the whole rule.
  • Owners and admins always hold a seat.
  • Members hold a seat only if they have manager access on at least one project. A member who is viewer everywhere is free.
  • Clients never hold a seat. Free and unlimited, always.
  • Pending invites to a billable role hold a seat while they’re pending, so invites can’t stack past your cap.
The count is live. Demote an editor to viewer, remove them, or revoke a pending invite and the seat frees immediately. There’s no waiting until the next billing cycle and no calling support. Agency staffing changes weekly, and the seat count follows it in real time. Seat caps by plan: Free includes 2 editor seats, Starter up to 5, Agency as many as you purchase. You buy and remove seats in the billing portal, and the change syncs to your org in seconds.

​
At the cap

Inviting one more editor than you’ve paid for blocks the invite with an exact message: how many seats you’re using, and a button to add one. Adding a seat in the Stripe portal takes about ten seconds to sync. Then the same invite goes through. Client and viewer invites are never blocked. The cap only ever applies to editors.

​
Funded seats: nobody gets kicked

Sometimes an org ends up with more editors than purchased seats. Maybe someone was added through a side door, maybe a seat was removed in the portal while editors were active. When that happens, nobody is removed and nobody loses their data. Instead, the newest editors become read-only until the org is back under its cap. They can still browse every dashboard they could before. Any edit they attempt returns a clear message: the org is using N of M paid seats, ask an owner to add one. The order is deterministic and visible. Owners are funded first, then editors by seniority, so “why them and not me” always has an answer. The Team and Usage pages badge exactly who is funded and who isn’t, and the affected person sees a banner on their own dashboard before they ever hit a blocked click. Two ways out, both instant:
  1. An owner adds a seat in the billing portal. The unfunded editor is back to editing on their next click.
  2. An owner frees a seat by demoting another editor to viewer or removing them.

​
The Usage page

Usage in the sidebar is the org-level answer to “where do my credits go and who’s using my seats.” Owners and admins see the credit pool, per-project and per-member usage, the named seat list in funding order, and the add-seats action. Members see the same numbers without the actions. Clients don’t see the page at all.