Fix

Personal access tokens carry their owner's role in AI clients

A personal access token used to connect an AI client now sees what its owner sees, and stops working when its owner is deactivated.

A personal access token is meant to act as the person who created it. Through the REST API it always did. Used as the credential for an AI client over MCP, it was treated as an organization key instead, which reads across the whole workspace. So a member's own token could be used to read things a member cannot see in the app, such as profitability.

Now a personal token over MCP acts as its owner, with the role they hold at the moment of each request:

  • a member's token sees what that member sees;
  • a token whose owner has been deactivated or removed is refused;
  • a token created without the read scope is refused.

What has not changed. A personal token is still read-only over MCP, whatever scopes it has; to log time or change anything from an AI client, connect with OAuth. Organization API keys behave exactly as before. Nothing changes for the REST API.

If an AI client connected with a member's personal token starts answering "only available to managers and admins", that is this fix working.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free