Lifecycle and permissions

Goals in Pulse use explicit status values on each layer of the OKR stack. Metrics have no status — only values over time.

Status by entity

Move entities to completed when the period ends or the outcome is achieved. Canceled / canceled marks work abandoned without counting as success.

Key Result health (on_track, at_risk, off_track) reflects progress confidence — update as metrics or manual values change.

Capability gates

Workspace capabilities control whether a surface appears:

If a sidebar link is missing, the capability may be off for your workspace plan or admin configuration.

Permissions pattern

API permissions follow {entity}:{create|read|update|delete} — for example objective:update, key_result:read.

In the app, edit controls combine:

• Workspace capability allows mutation
• Your role grants the specific action on that entity type

Workspace admins and owners typically manage the full OKR tree. Team members may have read-only access to workspace goals while still editing delivery on their teams.

Example rollout

1. Leadership defines 3–5 North Stars (active).
2. Teams create Objectives (planned → active) linked to a North Star.
3. Each objective gets Key Results with baseline, target, and measurement type.
4. Connect Metrics where values should update automatically.
5. Link Initiatives and projects to Key Results for delivery traceability.
6. Mark Key Results completed and Objectives completed at period end.

Next

• North Stars
• Objectives
• Key Results
• Metrics
• Initiatives — delivery roll-up