GitHub and Linear/Jira access request
Why we ask
To run Pulse for a project, we need access to GitHub (commits, PRs) and Linear/Jira (work items list, status updates, releases, etc). Pulse turns this activity into one continuously updated view that is easy to follow, so managers and clients can spot slowdowns early and replace status calls with short, visual updates.
Why it's safe
- GitHub access is read-only. Pulse observes activity, it does not modify code or settings.
- Linear/Jira access allows modifying boards, but this is limited to you and project manager.
- Access is scoped to the specific project or repo, not the full organization.
- Access can be revoked at any time, with no lasting footprint.
Pulse value
- Pulse makes progress self-reporting, not manager-dependent.
- No more status calls or reports. You get a live view of what is happening, so you can focus on other things.
- Faster code does not mean faster delivery. Pulse tracks the whole lifecycle, from PR reviews and task progress to daily updates and releases, so slowdowns surface before they get expensive.
Step by step connection guides
- Step-by-step guide on how to get a Jira API key here.
- Step-by-step guide on how to get a Linear API key here.
- Step-by-step guide on how to get a GitHub token here.
For project managers
Send this message to the client in addition to or instead of this article:
We use Pulse to give you real-time visibility into your project team's progress, so you're never waiting on status updates and always know exactly where things stand.
It needs:
Read-only access to [repo/project] GitHub
Read and write access to Linear/Jira access token lets you and the PM update boards directly from Pulse.