Orgs and roles
Last updated 2026-06-14
Definition
Orgs and roles map the people on your team to what they may do. An organization groups your users, and a role on each user decides their permissions — an admin manages connectors and billing while an analyst reads metrics. Roles drive the capabilities Quri grants, so access matches the job rather than handing everyone the keys.
How to do this in Quri
- Open /app/settings for the workspace whose team you manage.
- Add the people who need access to the organization.
- Assign each person a role that matches what they should do.
- Confirm their access — roles resolve into the capabilities Quri grants.
Frequently asked
- How do roles work in Quri?
- A role on each user resolves into a set of capabilities — the specific things they may do. An admin role unlocks management actions; a read role unlocks viewing. Quri grants access from the role, not per user by hand.
- Can I give someone read access without letting them change things?
- Yes. That is the point of roles. A read-oriented role lets a person view metrics and reports while withholding the capabilities that change connectors, settings, or billing.