Pulse has two orthogonal axes:
- Mode — how you interact with the app (Engineer vs. Normal). Engineer is the default; switch any time.
- Role — what you can see and do in the workspace (Member vs. Manager vs. Admin). An Admin sets this.
Roles at a glance
| Role |
Own timesheet |
Team data |
Workspace settings |
View other members |
| Member |
✅ Read + write |
— |
— |
— |
| Manager |
✅ Read + write |
✅ Aggregated only (totals by category / project) |
— |
— |
| Admin |
✅ Read + write |
✅ (as manager) |
✅ Members, categories, tools, projects, teams, API tokens |
✅ Read-only "view as member" — cannot modify |
Member (default)
Every signed-up user starts as a Member. Members:
- See, write, and edit their own timesheet entries.
- See workspace categories and tools (so they can label entries).
- Switch between Engineer and Normal mode any time.
- Can connect their AI coding tool via MCP — using a token an Admin issues, or via OAuth through a client an Admin registered.
- Cannot see other members' entries or workspace settings.
Manager (EM / PM)
Managers have all Member capabilities plus:
- A team rollup view showing aggregate time for the team(s) they manage — totals by category and by project, never per-person rows.
- The same scoping applies in the MCP:
pulse_get_team_rollup returns aggregates only. There is no flag to bypass it.
Managers are assigned by an Admin in Settings → Members and tied to specific teams.
Admin
Admins have full workspace control:
- Manage members — invite, remove, change role, assign to teams.