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. Admin). An Admin sets this.
Roles at a glance
| Role |
Own timesheet |
Workspace settings |
View other members |
| Member |
✅ Read + write |
— |
— |
| Admin |
✅ Read + write |
✅ Members, categories, tools, projects, OAuth clients |
✅ Read-only "view as member" — cannot modify |
ℹ️ Manager role and Teams aren't available in this release. There's no way to assign a Manager, and the Teams settings screen has no entry point — you can't create a team or assign members to one. Both may return in a future release.
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 — create and revoke their own API token from the account menu (top right) → API tokens, or connect via OAuth through a client an Admin has registered.
- Cannot see other members' entries or workspace settings.
Admin
Admins have full workspace control:
- Manage members — invite, remove, change role.
- Edit categories, tools, and projects.
- Register OAuth clients for AI-tool connections, workspace-wide (Settings → Developers → OAuth clients) — Admin-only. Personal API tokens are self-service for every role; Admins manage theirs at the same Settings → Developers screen.
- Use "view as member" to read any member's timesheet for support / audit. Read-only — an Admin cannot modify another member's entries via UI, API, or MCP.
Every workspace must have at least one Admin. The first sign-up of a workspace is automatically Admin. Pulse blocks you from demoting the last Admin.