Organizations, members, and access
Intello is multi-tenant. Every monitored dependency, snapshot, change event, and alert preference belongs to exactly one organization. You pick your org implicitly by signing in—there’s no separate “org switcher” in normal product use unless your deployment adds one.
This page explains roles, invitations, and what members can’t do in Settings (especially org and billing).
Organization as security boundary
Behind the scenes, Intello always loads data for your org only. You can’t view another customer’s dependencies by guessing URLs in the app; the backend enforces org-scoped access on every request.
Roles
Product roles are coarse-grained:
- Admin — can mutate organization settings, billing, invitations, destructive member operations, and many integration settings.
- Member — can view monitoring data and participate in workflows (acknowledgements, triage) but cannot perform destructive org mutations.
Exact UI labels may vary, but destructive actions you should expect to be admin-gated include:
- Updating organization profile / billing contact details (where applicable)
- Inviting, removing, or changing roles of members
- Canceling or resending pending invitations
Invitations
Invitations flow through tokenized links:
- An admin creates an invitation from Settings → Organization / Members (wording varies).
- The recipient gets email with a link containing a token.
- They sign in (or sign up) and accept; Intello checks that the signed-in email matches the invite so someone else can’t steal the invite.
Service accounts and automation
Most teams only use human accounts in the UI. If you script against Intello, use a dedicated account with the minimum role you need; see Authentication.