Organisation billing

How licences are owned

When you buy a package, the licence is recorded against the workspace tied to your customer account. That workspace is what other parts of Packagento call "the org": it is the unit that holds your licences, your projects, and the tokens those projects mint. Solo developers see a single workspace and never need to think about it; teams build on the same shape by inviting teammates into one customer's workspace.

Licence ownership is fixed at purchase time and stays with that workspace. There is no migration tool today; if you bought a licence on the wrong account, contact support before you cancel.

Who can purchase

Anyone signed in to a Packagento customer account can complete a checkout. The resulting licence is attributed to the purchaser's own workspace. If you need a teammate to buy on the team's behalf today, the simplest pattern is to have one teammate hold the workspace and invite the others into it.

Once a workspace exists, only members with the owner, admin, or billing role can request a refund or cancel a subscription against its licences. Developers and viewers can see the licence but cannot trigger a billing-side change.

Per-project scope

A licence belongs to one workspace, but you activate it onto a specific project to get a token. Only members of the workspace with owner, admin, or developer access can read that project's tokens; the billing and viewer roles can see project metadata but not the tokens themselves.

Adding a teammate to your workspace gives them visibility on every project in that workspace through their role. There is no separate "add to project" step for org developers; project-level guest roles exist for one-off cases where you want to grant access to a single project without making someone a workspace developer.

See Team and roles for the role matrix.

Invoices and the payment method

Each purchase produces a Stripe invoice addressed to the buyer who placed the order. Subscription renewals charge the payment method that the original purchase used, so renewals carry on for as long as that card stays valid in Stripe and the subscription remains active.

If the original purchaser leaves your team, plan ahead: their card is what Stripe will retry on the next cycle. The straightforward fix today is to cancel the subscription, have a remaining teammate re-purchase, and invite the rest of the team into that workspace.

What happens when someone leaves

Member removed from the workspace: any project tokens they personally minted are deactivated automatically; tokens minted by other teammates on the same projects keep working. The workspace's licences remain in place.
Member removed from a project: they lose their guest access to that project. They keep access to other projects in the same workspace if they remain a member of the workspace.

Multiple workspaces

You can be a member of more than one workspace at the same time: your own, plus any that other customers have invited you into. Each workspace has its own members, projects, and licences. The switcher at the top of the Org settings page lets you flip between the ones where you are an owner or admin; that selection scopes the view of members and invites below it.

Troubleshooting

"I want the invoice on a different account": today the invoice address follows the purchaser's account. For team purchases, decide which teammate places the order before you check out; contact support if you need an invoice reissued.
"A teammate can't install a package the workspace owns": they need at least developer access to the project the licence is activated on. Invite them into the workspace, or use a project-level guest invite for narrower access.
"My card was on a workspace I no longer use": subscriptions remain tied to the original Stripe customer. Cancel the subscription on the old workspace and start a new one from the workspace you want to keep going.

Billing or invoice questions? Get in touch through our contact form with your order or licence number.