Skip to content

Console and roles ​

Scope: current hosted production uses organization workspaces. Personal workspaces and owner self-review require a later control-plane upgrade; self-hosted installations depend on their actual version and identity configuration.

The console is served by the control plane. On the hosted control plane, it is at the address we give you.

Signing in ​

  • configured sign-in provider. "Sign in with Yi Labs" uses your configured sign-in provider: Google, GitHub or email. The same account works for every Yi Labs product. Account recovery and sign-in devices are handled in the configured sign-in provider. Guard has no passwords of its own.
  • Enterprise SSO. A project can be set up for your company's OIDC provider. Then "Sign in with SSO" appears too, and your identity provider's groups map to Guard roles.

A session lasts 15 minutes and is not extended. A minute before it ends, the top of the page says so. Afterwards, "Continue" signs you in again and brings you back to the same page. Unsaved policy edits are still there.

Organizations and projects ​

On "Organizations and projects":

  • Your own space. "Switch or create an organization" takes you to your configured sign-in provider, where you pick one of your organizations or create a new one. You can create your own even if today you are only a member of someone else's.
  • Inviting people. Invitations happen in the configured sign-in provider ("Manage organization and invitations"). Once someone accepts, they sign in to Guard with that organization.
  • New project. "Create project": the owner of the current organization names it. A new project starts in Observe mode, keeps events for 30 days, up to 100,000, and has no credentials yet. An organization can create up to 100 projects.
  • Switching. Use the project picker at the top. Permissions are worked out again for the new project, and one-time values on screen are cleared. Switching doesn't extend the session.

Changes to organization membership or ownership in the configured sign-in provider take effect at your next sign-in to Guard.

Roles ​

Roles are per project.

RoleConsole nameCan
ownerOwnerManage members, connections and SDK download tokens; edit, preview and publish policies; retire executors; manage the managed cloud
adminPolicy adminEdit, preview, submit and publish policies; roll back; retire executors; approve or reject action approvals; manage the managed cloud
reviewerReviewerApprove or reject candidate policies; approve or reject action approvals
viewerViewerRead everything in the project
  • The owner of the organization is the owner in Guard. That is managed in the configured sign-in provider and can't be changed here.
  • Everyone else starts as a viewer, unless the owner assigned a role to their email in advance.
  • A policy's author can't review it, and an owner can't approve actions in place of a reviewer. Every project needs at least two people.
  • The server checks every request. The console only hides buttons a role can't use.

Members ​

"Members" is for the owner only. For each person you can set:

  • The role (admin, reviewer or viewer).
  • The trusted subject, the identity Guard compares with action approvals, so that nobody approves their own actions. If you leave it empty, the email is used.

You can assign a role by email before the person has ever signed in. "Disable" stops a member from signing in to every project of the organization, and their sessions end at once. "Enable" lets them back in at their next sign-in.

Pages ​

PageWhat it shows
OverviewThe current policy and mode, executors online, events observed, approvals waiting
ConnectConnections, connection packages, "Check connection", SDK download tokens
AssetsAgents, tools, MCP servers and network destinations: registered, covered, and observed but not registered
ExecutorsEach executor's health, version, format v2 support, last heartbeat and loaded policy version
EventsEvent investigation (opens the previous console)
PolicyThe policy as YAML: edit, preview, save as a candidate
Policy workflowCandidates, previews, reviews, publishing, generating from observed behaviour, published versions and rollback
ApprovalsThe action approval queue
Organizations and projectsYour organizations and projects
MembersPeople, roles and trusted subjects
Audit logThe latest control operations: who did what, and whether it was allowed

The managed cloud adds "Gateways", "Hosted runs" and "Credentials". See Fully hosted gateway and runs.

Executor health ​

StatusMeaning
OnlineHeartbeat within the last 2 minutes
Lost contactNo heartbeat for 2 minutes
ErrorThe executor reports a problem: can't reach the control plane, a policy problem, or a rejected credential
StoppedThe executor shut down
Credential no longer validIts credential was revoked or expired
RetiredTaken out of service by an owner or admin. Its heartbeats are refused and it no longer counts for format v2 checks

Each executor's policy shows as "Current policy loaded", "Not confirmed" or "Running an older version".

Asset coverage ​

CoverageMeaning
CoveredRegistered, and an executor that is online has confirmed the current policy
PendingRegistered, not confirmed yet
Not coveredRegistered but not under Guard
Observed, not registeredSeen in events, never registered

Coverage counts only what reached Guard. A tool that bypasses Guard doesn't show up here. Check your tool, MCP and network configuration as well.

Expert view ​

Full hashes, IDs and raw codes are hidden by default. Turn on the expert view to see them.