Concepts

How workspace, team, issue, and related Pulse objects fit together.

Pulse is built around a few core concepts that work together. Understanding how they relate makes it easier to pick the right object, from a single bug to a company-wide initiative.

Basic concepts

Issues

Issues are the unit of execution. They represent bugs, features, tasks, or stories a team needs to track.

An issue belongs to a single team, or is Personal. It can be assigned, labeled, prioritized, added to a project, planned into a cycle, and discussed in comments. Most day-to-day work in Pulse starts with an issue.

Read more on creating issues.

Workflows

As you work on issues, they move through a workspace workflow — an ordered set of issue statuses. Those statuses group lists and become column headers on boards. Every team uses the same workflow: Backlog, Todo, In Progress, QA, Release, Done. Review it from Settings → Your teams → <team> → Issue statuses.

Incoming work that still needs a response is a request, not an issue status named Triage.

Read more on issue status.

Teams

Teams are the primary delivery unit. Each team owns a backlog of issues, plus cycles, releases, labels, templates, and team documents.

Teams you belong to appear in Your teams. Click a team name for Home, Triage, Issues, Cycles, Projects, Views, and Releases. Triage, Cycles, and Releases only appear when that capability is on. You do not have to join every team you can open issues on.

Read more on teams.

Workspace

A workspace is the isolated environment for one organization. Members, teams, and work do not cross workspaces. You can belong to more than one and switch with the sidebar switcher (O then W).

When you log into Pulse, you are logging into a specific workspace. Capability settings can hide sidebar entries your workspace does not include.

Organizing work

Projects

Projects group issues around a bounded deliverable. They hold issues, optional documents, and milestones. A project can live on one or more teams, or be Personal, and may roll up to an initiative.

Status is the lifecycle (Idea, In Progress, Completed, and the rest). Health is On Track, At Risk, or Off Track, from the latest status update. They are different fields.

Read more on projects.

Milestones

Milestones further organize issues inside one project. Define stages of completion for that project, assign issues to them, and watch progress from the overview and Timeline. Milestones are not shared across projects.

Read more on project milestones.

Initiatives

Initiatives sit above projects and represent a strategic workstream. An initiative groups related projects, can span teams, and answers why the work exists — not only what is shipping.

Status is the lifecycle: Proposed, Planned, Active, Completed, or Canceled. Health is On Track, At Risk, or Off Track, from the latest initiative update. An active initiative can still be At Risk.

Read more on initiatives.

Cycles

Cycles are a team's repeating time-box for issues. They help the team decide what to work on in the near term. Enable them per team from Settings → Your teams → <team> → Cycles. A child team with no cycle policy of its own follows its parent.

Cycles are not releases. An issue can belong to both.

Read more on cycles.

Releases

A release is a named ship-batch of issues in a team pipeline. Cycles plan when work happens; a release describes what ships together. If Releases is missing from the team sidebar, ask a workspace admin to enable it.

Read more on releases.

Requests

A request is intake to a target team — a bug, feature, or other need. It is not an issue until someone links delivery work. Request Triage under a team is the queue waiting for that team's response. That is separate from issue status.

Read more on requests.

Views

Views are saved filters, sort, and display options over the same underlying work. They do not change the work. Open Views in the Workspace section, or under a team for team-scoped views.

Read more on views.

Documents and knowledge

A document is an editable page: team docs, wiki folders, or a page attached to an issue, project, or initiative. Knowledge is the set of sources Pulse Agent may retrieve. Editing a document does not automatically add it to agent knowledge.

Read more on documents.

Goals and OKRs

North Stars

North Stars are the few organization-wide strategic themes. Team objectives roll up here. If North Stars is missing from the sidebar, ask a workspace admin to enable it.

Read more on North Stars.

Objectives

An objective is a team-owned strategic goal under a North Star. Lifecycle status is planned, active, completed, or canceled. Progress is computed from Key Results — you do not write it.

Read more on objectives.

Key Results

A key result is a measurable outcome under exactly one objective. Health is on track, at risk, off track, or completed. Linking a metric can sync the current value.

Read more on key results.

Metrics

A metric is a time-series KPI. Recording a value can update linked Key Results. Metrics can also stand alone.

Read more on metrics.

Pulse Agent and MCP

Pulse Agent is the in-app AI at Agent (/agent, G then J). Enable it from Settings → AI & Agents. It cannot bypass your permissions.

The MCP server exposes Pulse to external AI clients such as Claude Code, Cursor, Codex, or Claude Desktop. That is a different entry point from in-app Agent.

Read more on Pulse Agent and the MCP server.

Personal, workspace, and team

Personal settings follow the signed-in account — profile, notifications, security, connected accounts, and some preferences. Interface theme and Open links in the desktop app apply across workspaces.

Workspace settings are shared: members, security, Administration, and feature capabilities. Language, Default home view, and App sidebar on Preferences are per workspace, not a personal default that follows you.

Team settings live under Settings → Your teams → <team> — members, labels, templates, cycles, issue statuses, and related delivery controls. Issue statuses themselves are workspace-wide.

Read more on Preferences and Teams.

How these concepts fit together

  • Issues track individual pieces of work
  • Teams own the backlogs those issues move through
  • Cycles help teams plan short-term work; releases group what ships together
  • Projects organize related issues around a deliverable
  • Initiatives organize related projects around a broader goal
  • Requests are intake, not issues
  • North Stars, Objectives, Key Results, and Metrics connect strategy to delivery
  • Views help people navigate all of the above
  • Documents are pages you edit; knowledge is what Pulse Agent may retrieve

Last updated on