SKILL-014 Billing and monetization Locked skill

Billing owner model

Billing belongs to the organization, not a user. Authorize billing actions through an org-scoped permission, and never let the last billing owner lock the account out.

01

What this skill helps you build

Decide who in an organization may change the plan, payment method, invoices, and tax details — and authorize every billing action through that permission.

The production takeaway

Billing belongs to the organization, not a user. Authorize billing actions through an org-scoped permission, and never let the last billing owner lock the account out.

02

Inside this skill

The full skill expands these implementation areas with decisions, edge cases, prompts, tests, and framework-specific code.

Billing and monetization
What this helps you build

A clear, enforced answer to "who can touch billing?" Within an organization, only certain members may change the subscription, update the card, view invoices, or edit tax info — an

🔒
Billing and monetization
When to use this

As soon as organizations have more than one member and you take money. Specifically: A workspace has admins who manage members but shouldn't all control spend. Finance/procurement,

🔒
Billing and monetization
The core idea

Billing is an organization level capability , and the right to manage it is a specific permission carried on a member's relationship to the org — not a property of the user, and no

🔒
03

Unlock the full implementation

Paid access includes the complete skill body, implementation prompt, common mistakes, production checklist, and code examples where this skill includes them.