Access control — overview

What Access Control is

VerOps uses role-based access control (RBAC) to decide what each member of your organization can see and do. Instead of a single "user" or "admin" switch, you grant people roles, and each role is a reusable bundle of fine-grained permissions. This lets you give exactly the right access — an on-call engineer who manages alerts but not billing, a stakeholder who can view dashboards but change nothing, and so on.

The model

Concept	What it is
Permission	A single capability, written as module.action — e.g. dashboards.view or alerts.manage.
Role	A named set of permissions (for example "Member" or a custom "On-call Engineer").
Assignment	People are given one or more roles. Their effective access is the union of all their roles' permissions.

View vs. manage

Most features expose two permissions: view (read — open the page, see the data) and manage (write — create, edit, delete). A few administrative areas (organization settings, billing, users, roles, API keys) are manage-only and reserved for administrators.

Built-in roles

Every organization starts with three system roles you can assign immediately:

Role	Access
Admin	Full access to everything, including settings, billing, users and roles.
Member	View and manage day-to-day features (dashboards, alerts, inventory, network, synthetics, RUM, APM, and more) — but not administrative settings.
Viewer	Read-only access across the product.

What you get

• Least-privilege access. Give people only what they need.
• Custom roles. Build roles that match how your team actually works.
• Multiple roles per person. Compose access from several roles.
• Consistent enforcement. Permissions are enforced across the product, not just hidden in the UI.

Note: Access Control lives under Settings → Roles and Permissions (managing roles) and Settings → User Management (assigning roles to people).