Concepts

Pulse organizes work in layers. Understanding those layers helps you choose the right object when planning, tracking, or asking for help.

The big picture

Workspace
├── Team
│   ├── North Star (workspace-level goals)
│   │   └── Objective
│   │       └── Key Result → Metric
│   ├── Initiative (often cross-team)
│   │   └── Project
│   │       └── Issue (+ sub-issues)
│   ├── Cycle (time-boxes issues)
│   ├── Release (ships issues)
│   └── Request (intake from others)
└── Documents & knowledge (attached to work)

Not every workspace uses every layer. Many teams start with Projects and Issues and add OKRs when ready.

Workspace

A workspace is an isolated environment for one organization (or business unit). Members, teams, labels, and work items do not cross workspace boundaries.

You use a workspace to:

• Share a single roster of teams and members
• Apply workspace-wide settings (security, integrations, templates)
• Run cross-team views of Initiatives, Projects, and Requests

Workspace navigation (sidebar) includes Initiatives, Projects, Requests, Reviews, Dashboards, and other surfaces that can span teams. Capability settings may hide entries your plan does not include.

Team

A team is a group of people with its own backlog, workflow, and settings. Teams can nest: a sub-team inherits visibility rules from its parent in the sidebar tree.

Team-scoped objects:

• Issues and their workflow statuses
• Cycles and releases
• Team labels, estimates, and templates
• Team home page and pinned resources

Team navigation includes Home, Triage (for requests assigned to the team), Issues, Cycles, Projects, Views, and Releases.

Permissions are evaluated per team. You may see a team in the sidebar because you can read its issues even if you are not a direct member.

Goals and OKRs

Pulse separates direction from delivery:

Objectives and Key Results answer "are we moving the needle?" Initiatives and projects answer "what are we building?"

Details: Goals and OKRs.

Initiatives and projects

Initiatives group related projects under a shared outcome. An initiative can span teams and carries progress and status updates (On Track, At Risk, Off Track).

Projects are bounded deliverables with start and target dates, milestones, and linked issues. A project usually belongs to one team but may connect to an initiative and to Key Results.

Issues are individual tasks. They live on a team board, belong to cycles and releases, and can nest as parent/sub-issues.

See Initiatives, Projects, and Issues.

Cycles and releases

Cycles time-box issue work for a team (similar to sprints). Teams enable cycles in settings; the sidebar shows Current and Upcoming cycles when active.

Releases group issues that ship together under a version or date. Releases are team-scoped and require the releases capability.

See Cycles and Releases.

Requests

Requests are how people ask a team for work — bugs, features, or other needs. They have their own workflow (Triage, Pending, Accepted, and so on) and can convert into issues or projects.

Request Triage under a team is the queue of requests waiting for that team's response. This is separate from issue status.

See Requests.

Issue properties

Issues carry structured fields:

• Status — position in the team workflow (Backlog → Done by default)
• Priority — urgency relative to other work
• Labels — team-defined tags for filtering and automation
• Estimate — optional sizing when enabled per team
• Assignee, due date, relations, and more

See Issue properties.

Views and filters

Views are saved filters over issues, projects, or initiatives — table, board, timeline, or stats layouts depending on context. Workspace and team sidebars include Views entries scoped to that context.

Filtering, sorting, and grouping are shared concepts across list pages. Saved views persist filter and display options.

Documents and knowledge

Pulse supports rich documents attached to initiatives, projects, issues, and team home pages. Documents version over time; the stable identity is the document root, not each edit session.

Document-heavy workflows are covered in a later docs phase; attach documents from entity detail pages in the app.

Pulse Agent and integrations

Pulse Agent (in the app) runs AI-assisted workflows on entities you can access. MCP server exposes Pulse to external AI clients — a different entry point with its own setup.

• In-app agent: settings under Settings → Pulse Agent when enabled
• External clients: MCP server

Do not confuse MCP installation docs with in-app agent administration; they serve different audiences.

Personal vs workspace vs team settings

When docs mention a path starting with Settings →, open settings from the workspace sidebar gear menu.

Where to go next