Fix

The API shows a member's token what the app shows that member

A member's API token now reads the same projects, people and money as that member sees in the app, and time can no longer be logged against a project and task that do not belong together.

A personal access token, or a connected app, acts as the person who made it. For a plain member the API answered a few requests more generously than the app does for the same person. It now matches the app.

With a member's token:

  • Projects and tasks follow the workspace's "members only see assigned projects" setting, as the project picker does. A project the member is not assigned to is not listed, and asking for it by id answers 404, as do its tasks and assignments.
  • Other people are not listed. GET /users returns the member alone, and another person's id answers 404.
  • Rates on project assignments are blank.
  • Invoices and work roles answer 403, like the other manager-level endpoints.

Nothing changes for an organization key, or for a manager's, admin's or owner's token.

Logging or moving time now checks that the task belongs to the project, on every route, and answers 422 when it does not. Logging time to an archived project still works, as it does on the timesheet.

If an integration uses a member's token and relied on any of the above, give it an organization key or a manager's token.

← 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