Designing seller roles and permissions
How to build Owner, Manager, Seller, Booster, Finance, Support, and Viewer access without leaking tenant data.
Start with presets, then allow custom roles
Preset roles make onboarding fast, but real teams differ. The owner may want one operator to manage only Brawl Stars conversations, another booster to see assigned Valorant orders, and finance staff to see payouts without buyer messages.
Permissions should be independent actions such as view cost, edit stock, send offer, publish pricing, complete order, or manage devices.
Add scopes
A permission can be limited by game, service, region, assigned orders, own conversations, inventory location, or category. Empty scopes should have an explicit meaning rather than accidentally granting everything.
The backend derives workspace identity from the authenticated membership and never trusts a workspace ID from the browser by itself.
Audit sensitive actions
Price publishing, live automation, financial adjustment, delivery, role changes, and support access need complete audit records. Some workspaces may require second approval for selected actions.
Support impersonation should be consent-based, time-limited, scoped, and visible to the customer.