Start guide
Learn Pulse in minutes — workspace model, first tasks, and where to go next.
Start guide
Pulse connects goals, projects, and day-to-day work in one workspace. This guide orients you to the product model and the first tasks most teams perform after sign-in.
What Pulse is for
Pulse helps teams:
- Align on outcomes with North Stars, Objectives, and Key Results
- Plan initiatives and projects with dates, milestones, and status updates
- Deliver work through issues, cycles, and releases
- Intake needs from other teams through requests
- Connect tools such as GitLab and AI clients through integrations
If you are new to OKRs, read Goals and OKRs after this page. For the full entity map, see Concepts.
Before you begin
You need:
- An account on app.trypulse.tech
- Membership in at least one workspace
- Permission to create or edit work in a team (most members can create issues; managers configure teams)
Workspace admins invite members under Settings → Administration → Members.
Step 1 — Understand your workspace
A workspace is your organization's Pulse environment. Everything you create belongs to one workspace.
Inside a workspace you will see:
- Workspace navigation — cross-team lists such as Initiatives, Projects, Requests, and Reviews
- Your teams — each team has its own Issues, Cycles, Projects, and Releases
- Personal entries — Inbox, My issues, and favorites
Open the workspace switcher in the sidebar to change workspaces if you belong to more than one.
Step 2 — Join or create a team
Teams group people and work. Issues, cycles, and most delivery settings are team-scoped.
- Open Settings → Administration → Teams (workspace admins) or ask an admin to add you to a team.
- Find your team under Your teams in the sidebar.
- Open the team's Home page to see pinned resources and team documents.
See Teams for hierarchy, roles, and team settings.
Step 3 — Create your first issue
Issues are the unit of execution — bugs, tasks, and small projects of work.
- Under your team in the sidebar, click Issues.
- Press C or click New issue.
- Enter a title, pick a team, and set Status (for example
TodoorIn Progress). - Save.
Issues inherit workflow statuses, labels, and estimates from the team. See Create issues and Issues.
Step 4 — Represent planned work
For work larger than a single issue:
| If you are planning… | Create… | Learn more |
|---|---|---|
| A multi-project outcome | Initiative | Initiatives |
| A bounded deliverable with milestones | Project | Projects, Create projects |
| A time-boxed batch of issues | Cycle | Cycles |
| A shipped version | Release | Releases |
Follow Set up your team when standing up Initiatives, Projects, and Milestones for a new team.
Step 5 — Connect goals (optional)
If your workspace uses OKRs:
- Open North Stars or Objectives from the Workspace section (managers and admins).
- Create an Objective linked to a North Star.
- Add Key Results with baseline and target values.
- Link Initiatives to Key Results so delivery traces back to outcomes.
Start at Goals and OKRs.
Step 6 — Connect your tools (optional)
- MCP server — use Pulse from Claude Code, Cursor, Codex, or Claude Desktop. See MCP server.
- GitLab / development — link merge requests and development status to issues (when enabled for your workspace). Configure under team or workspace integration settings.
Common next steps
Concepts
How workspace, team, goal, and delivery entities relate.
Requests
Submit and triage work from other teams.
Templates
Standardize how issues, projects, and requests are created.
Issue properties
Status, priority, labels, and estimates.
Get help
- Search this site with ⌘K / Ctrl+K on the docs home
- Legal and privacy: Legal
Last updated on