Assistant access
How to connect Claude, ChatGPT, Claude Code or Cursor over MCP, the four scopes, what an assistant can't do, and how HR turns access on, off and revokes it.
People can use the HR system from their own assistant: Claude, ChatGPT, Claude Code, Cursor or any other client that speaks MCP. The assistant acts as the person who connected it. It sees what they see in the app, does only what they allowed, and every call lands in the audit log.
Turning it on
Section titled “Turning it on”Assistant access is off until HR turns it on in Company settings, under AI assistants. A connected assistant sends what it reads to the company that runs the assistant, which may be outside the EU, so check that fits your privacy notice first.
Turning it off stops every key and connection at once. Turning it back on restores them. The switch is written to the audit log.
Connecting an assistant
Section titled “Connecting an assistant”Each person opens AI assistant in the menu. Every assistant connects to one address:
https://<your company address>/mcpThe MCP server, over HTTP. OAuth 2.1 with dynamic client registration, PKCE and refresh tokens, or a bearer key. The metadata is at /.well-known/oauth-protected-resource/mcp.
In Claude, open Settings, then Connectors, and add a custom connector with the address above. Claude sends you to a consent screen, where you sign in with your second factor and tick what it may do.
In ChatGPT, add a connector with the address above. ChatGPT sends you to the same consent screen, where you sign in with your second factor and tick what it may do.
claude mcp add --transport http hr https://<your company address>/mcpThe first call opens the consent screen in your browser.
For a client that takes a bearer token, make a key on the AI assistant screen and paste it in. The key is shown once. It lasts 90 days by default and a year at most.
The screen lists your keys and connected apps with when each was last used, and you can revoke any of them. HR sees every live key and connection in the company and can revoke them too.
Scopes
Section titled “Scopes”A connection carries only the scopes chosen for it, and never more than the person’s role allows.
| Scope | Allows | Who can grant it |
|---|---|---|
read |
See what you can see in the app: your balances and requests, who’s off in your team, the directory you can browse, policies and holidays | Everyone |
self |
Book and cancel your own leave, update your own contact details | Everyone |
decide |
Approve or deny leave for the people you decide for. Each decision is prepared first and only happens when you confirm it in the chat | Managers and HR |
sensitive |
Read ID, bank, tax, health and pay details, and the pay transparency figures. Every read is audited | HR, on their own connection |
A scope is capped at your role. If you stop managing people, a key you made as a manager loses decide straight away, and a leaver’s keys stop working when their record ends.
What an assistant can’t do
Section titled “What an assistant can’t do”Ending employment, changing pay, deleting a record and changing who can sign in are done by a person in the app. If an assistant asks for one, it gets the steps and a link to the screen.
What’s logged
Section titled “What’s logged”Each tool call goes to the audit log with the person, the time, the tool, and whether it was allowed. The full list of tools is in MCP tools.