Feature · Admin

Design system

See every shared component and state in both themes.

Last changed

Generated from commit 1d7dbff ·

How it works

Admin overview

Admin overview links every administrator tool: benchmarks and evaluation, people and access, models and routing, governance and spend, and, for platform operators, platform operations.

Benchmarks

Benchmarks has two tabs: Provider benchmarks compares model providers and CLIs on the same cases; Crewshal harness shows harness runs. Paid runs need consent from an owner or admin.

Design system

Design system shows the tokens, components and states that every screen uses, in the light and dark themes.

Avatar lab

Avatar lab shows the worker avatars. Use it to check them and to capture the avatar kit. Find it in the command palette.

Who can open it

Only owners and admins. Others see "Admin access required".

From the help article The Admin area, checked against the product on .

What you can do

The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.

  • listApprovals

    Viewer

    Lists approvals.

    Types: ListApprovalsRequest returns ListResponse<ApprovalDto>

  • listEscalations

    Viewer

    Lists escalations.

    Types: ListEscalationsRequest returns PageResponse<EscalationDto>

  • listOrgDeliveryProofs

    Viewer

    Lists org delivery proofs.

    Types: ListOrgDeliveryProofsRequest returns ListOrgDeliveryProofsResponse

  • listSignals

    Viewer

    Lists signals.

    Types: ListSignalsRequest returns ListSignalsResult

  • decideApproval

    ApproverNo API tokens

    Decides the approval.

    Types: DecideApprovalRequest returns ApprovalDto

  • resolveEscalation

    MemberNo API tokens

    Resolves the escalation.

    Types: ResolveEscalationRequest returns EscalationDto

  • getWorkItem

    Viewer

    Gets the work item.

    Types: GetWorkItemRequest returns GetWorkItemResponse

  • getSpendSummary

    Viewer

    Gets the spend summary.

    Types: GetSpendSummaryRequest returns SpendSummaryResponse

  • queryWork

    Viewer

    Queries work.

    Types: QueryWorkRequest returns QueryWorkResponse<WorkItemSummary>

  • getDepartment

    Viewer

    Gets the department.

    Types: GetDepartmentRequest returns GetDepartmentResponse

  • getWorker

    Viewer

    Gets the worker.

    Types: GetWorkerRequest returns GetWorkerResponse

  • getWorkerDrill

    Viewer

    Gets the worker drill.

    Types: GetWorkerDrillRequest returns GetWorkerDrillResponse

  • getOrgConfig

    Viewer

    Gets org config.

    Types: GetOrgConfigRequest returns OrgConfigView

  • diagnosticBundle

    Viewer

    Diagnostic bundle.

    Types: DiagnosticBundleRequest returns DiagnosticBundleDto

  • observeWhy

    Viewer

    Shows the why.

    Types: ObserveWhyRequest returns ObserveWhyDto

  • observeEntity

    Viewer

    Shows the entity.

    Types: ObserveEntityRequest returns ObserveEntityDto

  • getWorkItemTrace

    Viewer

    Gets work item trace.

    Types: GetWorkItemTraceRequest returns GetWorkItemTraceResponse

  • getWorkItemActions

    Viewer

    Gets work item actions.

    Types: GetWorkItemActionsRequest returns ListResponse<ActionDto>

  • getContextManifest

    Viewer

    Gets the context manifest.

    Types: GetContextManifestRequest returns GetContextManifestResponse

  • listDeliveryProofs

    Viewer

    Lists delivery proofs.

    Types: ListDeliveryProofsRequest returns ListDeliveryProofsResponse

  • decideSignal

    Member

    Decides the signal.

    Types: DecideSignalRequest returns SignalDto

  • getSignal

    Viewer

    Gets the signal.

    Types: GetSignalRequest returns GetSignalResult

Screens

What it records

The feature writes these events to the audit log, the permanent record of what happened.

  • Policy changed
  • Budget reserved
  • Checkpoint saved
  • Context retrieved
  • Escalation raised
  • Escalation resolved
  • Integration changed
  • Memory recalled
  • Model called
  • Policy evaluated
  • Release recorded
  • Signal decided

Generated from code at commit 1d7dbff ·

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.