Members & Roles

ArcGlass governs access with role-based access control (RBAC). Every member has a role, each role maps to a defined set of capabilities, and data visibility is scoped by role — so people see and do exactly what their role allows, and no more.

Invite members

From Settings → Members, invite teammates by email and assign a role. The first person to sign in for your domain is the organization owner. Members can be removed or have their role changed at any time.

Roles

Roles fall into an escalating ladder plus two lateral roles:

• Viewer — read access to content in scope.
• Member — day-to-day use: run pipelines, edit content, act on results.
• Admin — manage sources, rules, integrations, and most settings.
• Owner — full control, including ownership transfer and deletion.
• Billing and People — lateral roles scoped to billing and member management respectively.

How permissions are enforced

There is one capability map for the whole product: routes and services are gated by the capability a role grants, not by ad-hoc role checks. Destructive actions require an explicit delete capability, and content lists and details apply a row-visibility filter based on the viewer's role. Identity always comes from the verified session — never from a value supplied by the caller.