Web UI

The Workloom web interface provides a management dashboard for your registry, workspaces, packages, and team. It runs as a Next.js application and is available at your deployment URL after authentication.

Dashboard

The home page shows an overview of your organization:

• Workspace count — total workspaces in the org
• Package count — total packages in the registry
• Recent activity — the 10 most recent audit log entries

Quick links take you to the full workspaces, packages, and audit log views.

Packages

Browsing the Registry

Navigate to Packages in the sidebar to browse all packages in your registry.

Filtering options:

• Search — filter by package name
• Scope — filter by package scope (e.g., @acme)
• Status — active, draft, deprecated, yanked
• Type — workflow, skill-collection, agent-collection

Each package card shows metadata including agent count, command count, skill count, stars, and creation date.

Package Detail

Click a package to see its full detail page:

• Header — scope, name, status badge, type badge, source URL link
• Metadata cards — stars, agents, commands, skills, trust class
• Workflow pipeline — visual representation of workflow steps (for workflow packages)
• Channels — current version on each release channel (stable, beta, canary)
• README — package documentation
• Version history — table of all versions with approval status, publish date, and scan results

Package Lifecycle

From the detail page, authorized users can transition package status:

Current Status	Available Actions
draft	Activate
active	Deprecate
deprecated	Reactivate, Yank

Version Approval

Each package version has its own approval workflow. From the version history table:

1. Submit — move a draft version to pending_review
2. Approve — (maintainer+) approve a pending version
3. Reject — (maintainer+) reject with an optional reason

See the Package Approval guide for details.

Security Scan Results

Click the scan icon next to a version to view its security scan results, including scanner version, pass/fail status, and any findings.

Add to Workspace

Click Add to Workspace on any package detail page to assign it to a workspace target. The dialog lets you:

1. Select a workspace
2. Choose a target within that workspace
3. Set a version constraint (e.g., ^1.0.0)
4. Choose a release channel

Workspaces

Workspace List

Navigate to Workspaces in the sidebar to see all workspaces.

Filtering options:

• Search — filter by workspace name
• Binding type — filter by repository binding type

Each row shows the workspace name, binding type, binding reference, current revision number, and creation date.

Workspace Detail

Click a workspace to see:

• Configuration — name, binding type, binding reference
• Revision — current revision number
• Target count — number of targets configured
• Policies — projection, telemetry, and CI policies
• Targets — each target with its providers and assigned packages

Action buttons:

• Edit Configuration — open the JSON config editor
• Manage Targets — add or remove targets
• Preview Render — see what the workspace would generate

Configuration Editor

The workspace editor (/workspaces/{id}/edit) provides a JSON textarea for editing the full workspace configuration:

• Name, binding type, binding reference
• Projection policy
• Telemetry policy
• CI policy
• Settings

Saving creates a new revision automatically. The editor validates JSON syntax before submission.

Target Management

The targets page (/workspaces/{id}/targets) lets you:

• Add targets — specify a target ID (logical name) and path (filesystem location in the bound repo)
• Remove targets — delete targets you no longer need

Targets map logical names to filesystem paths in a monorepo. For example, target backend might map to path apps/backend.

Diff Viewer

Compare any two workspace revisions at /workspaces/{id}/diff:

1. Select a from revision from the dropdown
2. Select a to revision from the dropdown
3. View changes color-coded by operation:
   • Green — additions (new fields/values)
   • Red — removals (deleted fields/values)
   • Orange — replacements (changed values, showing old → new)

Each change shows the JSON path, operation type, and affected values.

Audit Logs

Navigate to Audit Logs in the sidebar to see all organization activity.

Filtering options:

• Action — filter by action type (e.g., version.approve, workspace.update, member.invite)
• Resource type — filter by resource (e.g., package_version, workspace, organization_membership)

Each entry shows:

• Timestamp — when the action occurred
• Actor — who performed it (with user/service/system badge)
• Action — what happened (with badge)
• Resource type — what was affected
• Details — JSON payload with specifics

Use Load more to paginate through history (cursor-based, 50 entries per page).

Settings

Team Management

Navigate to Settings > Team to manage organization members:

• View members — see all members with name, email, role, and join date
• Invite — add new members by email with a role assignment
• Update role — change a member's role via the dropdown in the table
• Remove — remove a member from the organization

Available roles: owner, admin, maintainer, developer, viewer.

SSO Configuration

Navigate to Settings > SSO to configure single sign-on:

• Select an OIDC provider (Okta, Azure AD, Google Workspace)
• Enter the issuer URL and client credentials
• Toggle enforcement (when enforced, all users must authenticate via SSO)

See the Authentication & RBAC guide for details on role mapping with SSO.