Permissions answer two separate questions: which signed-in teammates may use the dashboard, and which callers may use a generated API route. Model both before inviting a large group or exposing an endpoint.
System and custom roles
Dashier includes Owner, Admin, Editor, and Viewer system roles, plus custom roles with explicit grants. In the current implementation, Owner and Admin have management-level access, Editors can work with records, and Viewers are read-only. Custom roles are evaluated against grants such as {source-slug}.read, {source-slug}.create, {source-slug}.update, and {source-slug}.delete.
Give each person the narrowest role that lets them work. Someone who only reviews records does not need deletion rights. Recheck access when responsibilities change or someone leaves the organization.
Project and source boundaries
Organizations contain projects, and projects contain sources. Membership plus project/source scopes limit where a teammate can work. Keep production-facing sources separate from unrelated test or internal records when the audiences differ.
API policy is separate
Endpoints begin switched off. Exposing a route is a separate, deliberate step from choosing its access mode; until then the API channel answers 403 for that method regardless of credentials. For each generated route and HTTP method, choose Public, Authenticated, or Role access. An API key’s read/write/admin scope is not a teammate’s dashboard role. A Public endpoint needs no credentials, so use it only for intentionally public data; a source being in a project does not by itself make a key mandatory.
Test access decisions
Write a small matrix of role, source, operation, and expected result. Include positive and negative cases: a Viewer can list but cannot update; a custom role with members.read may read Members but not write; an unauthenticated call to an Authenticated route should be rejected. Test dashboard and API paths, keep raw keys out of source control, and revoke keys no longer needed.
