Member access

Organisation projects are shared. By default every member can access all of them, which is usually what you want. When it is not, an individual project can be switched to restricted access with an explicit list of who is allowed in.

Owners and admins always have access to every project in their organisation, and that cannot be removed. Restrictions apply to regular members only.

Add a member

In Settings → Organisations, open the organisation and use Members → Add. You need to be an owner or admin. The person receives an invitation by email.

Role	Can do
Member	Log time to the organisation projects they have access to
Admin	Everything a member can, plus managing members and projects. Always has access to every project

Money is a separate question: what each role can see of rates, budgets and margin is covered in who sees what.

Restrict a project

Access is configured per project, not per organisation.

1. Open the project in Settings → Projects and scroll to Member access.
2. Turn Restrict on. The member list appears.
3. Flip the switch next to each person who should have access. Owners and admins stay locked on.
4. Save changes. Access is stored alongside the project's name and repositories in a single save.

Leaving Restrict off keeps the default, where every member of the organisation can access the project.

Two things worth knowing

Losing access does not delete anything. If a member is removed from a project they previously logged time to, their existing entries are preserved and shown to them as read-only.

Moving a project between organisations clears its access list. Members of the new organisation get access by default, and you restrict it again afterwards.