Team & Roles — who can do what

Invite teammates from the Team page — they sign in with a work email or wallet, no passwords to manage. Every teammate has one role:

The ladder

• Owner — everything, plus the only role that can promote, demote, or remove admins. There is exactly one owner and nobody can touch that account.
• Admin — everything operational: listings, campaigns, refunds, credentials, buying credits, and team management below admin (invite, remove, and re-role members and specialists). Admins can't grant admin or act on other admins — that's owner territory.
• Refunds — a specialist seat that processes the refund queue (approve/deny) and nothing else that's gated. Good for support staff.
• Minting — a specialist seat that runs promotional campaigns: beta waves, creator giveaway allowances, watch-drops, airdrops. No listing edits, no refunds, no credit purchases. Good for community managers.
• Member — day-to-day operator: create and edit listings, drops, and variants. Members can't process refunds, launch campaigns, or spend money.

The money rule

Anything that spends or moves money is gated: refund decisions need the refunds role or admin; campaign minting needs the minting role or admin; buying credit packs and viewing or rotating API credentials need admin or owner.

Your API key

The studio API key your backend uses has full operational access — it's your server's credential, not a person. It can never view or rotate credentials; that always requires an owner/admin signed into the dashboard.