A role named admin is only useful when its powers are defined. For a client-facing dashboard, write the actions each role may perform before connecting role names to interface controls.
Clerk supplies organisation membership and role concepts, while your application must connect them to its own records and operations. A correct organisation selector cannot compensate for an endpoint that ignores the resource's owner.
Map roles to meaningful dashboard actions
List actions such as view requests, edit requests, export customer data, invite members, change billing, and transfer ownership. Decide which roles need each action and whether any action also depends on record state or an ownership relationship.
Consult the current Clerk roles and permissions reference for supported configuration. Avoid assuming a provider's default roles express your product's exact business rules. Review the configured roles in the actual environment.
Design a fictional client-service dashboard
Suppose an agency manages service requests for two clients. Client staff can read and update requests in their own organisation. A client owner can also invite colleagues. An agency support role can diagnose a problem only through a separately controlled support workflow.
Create a permission table before implementing it. A viewer can read a request but cannot change its status. An operator can update a request but cannot grant another user owner powers. An owner can manage members under the agreed policy. Export permission should be explicit because exporting can expose more data than opening one record.
Store the organisation identity with organisation-owned resources and validate ownership when the server reads or changes them. For the provider's organisation context model, see the Clerk organisation overview. Treat that context as part of the decision, not permission to every requested identifier.
Verify the role matrix with negative cases
Use two fictional client organisations and one user who belongs to both with different roles. Test reading, editing, exporting, inviting, and changing access. Repeat through direct requests as well as the interface. Change the user's role and observe when the new decision takes effect.
Test background processing and file access separately. A request attachment or export job may use a different route from the main dashboard. Keep the same tenant and action boundary across those paths.
More roles create more combinations to document and review. Start with a small set that fits actual jobs, then add a role when evidence shows a distinct permission need. Avoid granting broad administrator powers merely to bypass a missing permission design.
The StackFlight product page provides related authenticated-SaaS context. This agency role model is illustrative and does not describe its current features.
Questions about Clerk organisation roles
Do default roles cover every dashboard?
No. Compare the actual configured powers with your required actions and check current provider capabilities before designing custom behaviour.
Should the frontend be the only role check?
No. Use it for clarity, then enforce the decision on the server where the resource is accessed or changed.
What should a review include?
Bring the action table, resource ownership fields, role-change behaviour, and failing tenant cases to a permissions review.