Organisations and roles

Owners hold ultimate organisation authority — typically founders or business owners who care about billing identity and long-term control. Admins operationalise that control: invites, seat hygiene, plan changes, and token packs.

Editors are the default makers. They draft in Document Studio, analyse PDFs, generate brand assets, leave comments, and participate in workflows. They should not need billing permissions to be productive.

Viewers are for stakeholders who must see work without reshaping it: executives on a narrative, trainees watching an SOP, clients invited carefully when membership is the right tool instead of a share link.

If someone needs permanent collaborative editing, make them an editor. If they need a one-off read of a draft, prefer a watermarked share link. Role inflation is how access control dies.

Shared AI usage only feels safe when spending is gated. Editors can consume tokens by running AI tools according to organisation norms; owners and admins decide whether to top up or upgrade when allowance runs low.

Failed calls use zero tokens, and editing stays free — so role design is about authority and blast radius, not about charging people to type. The audit trail still shows which members’ tools drove consumption.

Admins should pair role reviews with usage reviews. A contractor editor who generates hundreds of logo variants may be valuable — or may need a better brief. Roles give them access; the trail gives you signal.

Never share owner credentials to “make billing easier.” Invite an admin. Credential sharing collapses the audit and security story the marketplace is trying to keep clean.

Organisation libraries keep documents and design assets in shared space so work survives membership changes better than personal inboxes. When a contractor leaves, revoke their role; keep the files.

Collaboration features — comments, live presence, versions, approvals, signatures, share links — inherit organisation membership. That is why CasperWasp emphasises orgs instead of anonymous file drops.

Seat and plan limits follow your subscription. Admins should remove dormant members and avoid granting editor to spectators. Clean rosters make both security and shared usage calmer.

Design Studio and Document Studio share the organisation so a letterhead and a proposal live beside each other. Roles apply across that marketplace surface rather than inventing per-app permission exoticism for everyday teams.

Create an organisation, invite the smallest set of people who must collaborate, and assign editors liberally but admins sparingly. Add viewers only when read-only membership beats share links.

Document your internal rule: who may purchase token packs, who may invite externals, who may send signature requests on high-risk agreements. The product provides gates; the team provides policy.

Use register to start, then grow into pricing decisions as usage patterns appear in the audit trail. You do not need a token calculator to begin — you need clear roles and a willingness to inspect tokens consumed later.

As you scale, revisit roles quarterly. Promotions, vendor changes, and campaign hires are when access rot appears.