Skip to main content

Roles and Permissions

Access in VibeControls is role-based and enforced at the API gateway on every request. Roles are assigned per workspace under Permissions in the Workspace Modules group. VibeControls ships six product roles. Workspace owners and admins have every permission by default.

The six VibeControls roles​

RoleWhat it is forDefault home
VibeControls Control Plane OwnerFull control of the VibeControls estate, including agent credentials, security policy, and audit retention.Overview
VibeControls Platform EngineerRuns the agent fleet and the golden paths: machines, tunnels, templates, catalog, decks, and docs builds.Overview
VibeControls DeveloperBuilds and runs work inside vibes: agents, sessions, decks, tunnels, docs, and AI context for their projects.Vibes
VibeControls Security LeadOwns the security baseline (policies, scan runs, exceptions, and scorecard tiers) with read-only visibility into the fleet.Overview
VibeControls Operations EngineerRuns existing runbooks, sessions, and tunnels and restarts agents during incidents, without reshaping projects or policy.Overview
VibeControls AuditorReviews and exports VibeControls activity, security posture, and catalog evidence without changing anything.Audit Log

A user with several roles gets the most privileged view. The full resource-by-role table is in Permissions and Access Control.

What each role sees​

The sidebar is filtered in two layers:

  1. Permission filtering hides items the role cannot use at all. For example, Control Center needs read access to agents, targets, vibes, sessions or AI context; Catalog needs read access to catalogs, components or templates; Audit Log needs audit:read; Permissions needs rbac:read. There is no toggle for these.
  2. Persona defaults decide which of the remaining items are prominent. Everything else is folded behind N more…. The selector at the bottom of the sidebar (Everything) switches views, and the customize icon beside it pins items.
RoleProminent by default
Control Plane OwnerOverview, Control Center, Catalog, Automation, Infrastructure, Insights, Settings, plus Permissions, Vault, Billing, Auth, Groups and Teams, Connected Systems
Platform EngineerOverview, Control Center, Catalog, Automation, Infrastructure, Insights, Settings, Connected Systems
DeveloperOverview, Control Center, Catalog, Automation, Infrastructure
Security LeadOverview, Insights, and Targets & Agents
Operations EngineerOverview, Targets & Agents, Sessions, Infrastructure, Insights
AuditorOverview, Insights, Audit Log

Search, Security Settings, Notifications, and Support are visible to every role.

Getting started by role​

Control Plane Owner​

  1. Invite the team under Administration › Invite People and give each person the narrowest role that fits (see Permissions and Access Control).
  2. Check Billing › Plans and Billing › Usage and Quota so the workspace's limits match the fleet you plan to run (Plans and Quotas).
  3. Review the security baseline with your Security Lead, and set the workspace defaults under Settings (Settings).

Platform Engineer​

  1. Install the agent on the machines you manage and confirm they are online under Control Center › Targets & Agents (Installing the Agent).
  2. Publish templates, components and plugins under Catalog so developers start from a golden path.
  3. Set up shared tunnels and decks under Infrastructure and Automation (Port Forwarding and Tunnels, VibeDecks).

Developer​

  1. Open Control Center › Vibes, your home screen, and create a vibe for each project (Working with Vibes).
  2. Start a session in the vibe and open its terminal (Sessions and Terminals).
  3. Add notes, prompts and AI context so the assistant knows the project (AI Prompts and Assistant).

Security Lead​

  1. Open a vibe from Control Center › Vibes and use its Security tab to run scans and review findings, and its Scorecard tab to check the score against its thresholds (Scorecards).
  2. Set or tighten security policies and approve exceptions. Besides Control Plane Owner, yours is the only product role that can change them.
  3. Use Targets & Agents to see which machines are behind on the baseline. You can see the fleet but not change it.

Operations Engineer​

  1. Watch Insights › Health for agents that go offline (Health).
  2. During an incident, open the affected vibe's sessions from Sessions, run existing actions and deck buttons, and restart agents from Targets & Agents.
  3. Pause or resume tunnels under Infrastructure › Tunnels. You can operate them, but you cannot reshape projects or policy.

Auditor​

  1. Start on Insights › Audit Log, your home screen, and filter by action, resource type, status, agent or vibe.
  2. Review usage under Insights › Analytics (Analytics) and each vibe's Scorecard and Security tabs.
  3. Export the filtered log with the export button. Everything else is read-only for your role.

Permission messages you may see​

MessageMeaning
You don't have permission to create vibes (or agents, sessions), shown on the create buttonYour role lacks the create permission on that resource. Ask a Control Plane Owner or workspace admin.
You don't have permission to update agentsYour role can see agents but not change them (Security Lead and Auditor).
You don't have permission to view vibes. Contact your workspace administrator for access.Your role has no read access to that screen's resource.
Access DeniedYou opened a screen by URL that your role cannot use.
You don't have permission to do that. (toast)The gateway denied one request on the page. If it appears on a screen you can otherwise use, one widget on that screen needs a permission your role lacks; the rest of the screen still works.

Assigning roles​

  1. Open Permissions in the sidebar.
  2. Pick the member and add one or more of the VibeControls roles.
  3. Changes apply on the member's next request. They may need to reload the app.

Workspace membership itself is managed under Administration (Invite People, Workspaces) and Groups and Teams.

Next steps​