Skip to content
Taskstand

Members and roles

Invite people to a project, pick the role that fits them, share single sections with a restricted member, and hand over, remove or leave a project.

Every project has members, and every member has one role in that project. The role decides what they see and what they can do: your team works on everything, a client adds and completes tasks without seeing your hours or rates, and a restricted member sees only the sections you share with them.

Roles are per project. Somebody can be a team member in one of your projects and a client in another.

The six roles

Role In short
Owner Manages everything, including members, settings, rates, budget and invoicing. Deletes the project, hands it over, links GitHub and Sentry and imports hours from Toggl.
Manager Runs the project with the owner: members, settings, rates, budget and invoicing. Deleting, handing over, linking GitHub or Sentry and importing from Toggl stay with the owner.
Team member Works on tasks and sections, logs time and sees all hours. No rates or budget.
Client Creates, edits and completes tasks and comments. Sees no hours, rates or budget.
Reader Reads along and comments. Can complete tasks assigned to them, nothing else.
Restricted Only sees the sections you share, with view or edit access per section.

A project always has exactly one owner: whoever created it, or whoever it was handed to.

What each role can do

This is the same table the project shows under What can each role do? on the Members page.

Owner Manager Team member Client Reader Restricted
Sees every ordinary section and task Yes Yes Yes Yes Yes No
Also sees financial sections Yes Yes No No No No
Comments on tasks Yes Yes Yes Yes Yes Yes
Completes tasks assigned to them Yes Yes Yes Yes Yes Yes
Creates and edits tasks Yes Yes Yes Yes No No
Manages sections and labels Yes Yes Yes No No No
Logs time and sees all hours Yes Yes Yes No No No
Picks the budget and kind of work of tasks and hours Yes Yes Yes No No No
Sees rates, budget and invoiced hours Yes Yes No No No No
Invoices hours Yes Yes No No No No
Members and project settings Yes Yes No No No No
Links GitHub and Sentry Yes No No No No No
Deletes the project or hands it over Yes No No No No No

A few things follow from this:

  • Clients, readers and restricted members see nothing about time. No timer, no hours, no estimates, no Hours page, no budgets.
  • Team members see the names of the budgets, not the money. With more than one budget they put tasks and hours in one, but how much a budget allows or has left, and every rate, stays with the owner and managers. See Time and invoicing.
  • The Code page (commits from a linked GitHub repository, issues from Sentry) is for the owner, managers and team members only. See GitHub.
  • A financial section is for the owner and managers only. Nobody else sees it or the tasks in it. See Projects.
  • A restricted member with edit access creates, edits and completes tasks, but only inside the sections shared with them. With view access they read and comment.
  • Money needs a paid plan as well. Rates, budgets and the invoiced state of hours only show when the plan of the project owner includes them. See Time and invoicing.

The Manager role needs Pro

You can only pick Manager when the project owner is on Pro or Business (or still in the free trial). On a smaller plan the role shows greyed out in the table and is missing from the role picker.

If the owner's plan drops below Pro later, a manager keeps the role but no longer runs the project and no longer sees rates, budget or money totals. They carry on as a team member. It comes back by itself when the plan does.

What a manager runs

A manager does nearly everything the owner does: the project settings, inviting members and changing their role, sharing sections with restricted members, budgets and rates, marking hours as invoiced and editing the hours of others. Four things stay with the owner:

  • deleting the project
  • handing the project to somebody else
  • linking GitHub and Sentry, because the key or installation of one person goes into that. A manager can remove a link.
  • importing hours from Toggl, because an import can make new projects and taking it back removes hours from several projects.

A manager does not change their own role or remove themselves from the project. To step out, they pick Leave project, so the owner hears about it.

What a manager does counts toward the owner's plan: inviting somebody takes a place in the owner's limit on people. When a manager runs into that limit, the message names the owner.

Invite someone

The owner and the managers of a project can invite people.

  1. Open the project and click the gear icon (Project settings).
  2. Go to the tab Members.
  3. Type the address under Invite by e-mail, pick a Role and click Invite.

Somebody who is already in another project of yours does not need their address typed: click in the field and a list of those people opens. Type part of a name or address to narrow it down, and pick with the mouse or with the arrow keys and Enter.

A manager only sees the people they already share another project of the owner with in that list. Anybody else they simply invite.

The line under the form explains the role you picked. The person gets an e-mail. If they already have an account, the button reads View the invitation; if not, it reads Create your account.

An invitation is a question

Nobody becomes a member without saying yes themselves. The invitation waits on the Invitations page of the person you invited, and they answer it there with Accept or Decline. When several are waiting, the button Accept all 3 (with the real number) takes them in one go.

  • Invitations appears in the sidebar, with a count, as long as something is waiting. After signing in, somebody with a waiting invitation lands on that page.
  • To answer, the e-mail address of the account has to be verified. That way nobody can answer an invitation meant for someone else. An unverified account still sees what is waiting, with a button Resend verification email.
  • Somebody without an account who creates one through the invitation link is a member straight away: creating the account for this invitation is the answer.
  • The invitation is for the address you typed. It only works for the account with that e-mail address.

Somebody you already work with

Somebody who is already a member of another project of yours joins straight away, without an invitation. You already work together, so there is nothing to ask. The button then reads Add instead of Invite, and a line under the form says so. They get a notification in the app, whatever their notification settings say.

Two exceptions. While an invitation for this project is still open for that person, they are invited again instead of added, and they are not in the list. And an archived project takes no new members: reopen it first.

  • Any project of yours counts, a finished or archived one as well. A project of somebody else where you both happen to be members does not.
  • Their e-mail address has to be verified. Otherwise they get an ordinary invitation.
  • They get a message that you added them, with a link to the project. Rather not be in it? They can leave the project themselves, see Leave a project.
  • The limit on people still applies, and so does the plan for the Manager role.

Waiting invitations

Open invitations are listed under the members, with the role and the date until which they are valid. An invitation is valid for 14 days.

  • Send again mails a new link and starts a new period. The link in the earlier mail stops working.
  • Revoke withdraws the invitation. The link in their mail stops working.
  • When an invitation runs out, you get a message and can send it again from the same page.

Inviting somebody who is already a member is refused.

Share a section with a restricted member

A restricted member sees the name of the project and only what you share. Sharing works per section.

  1. Invite the person with the role Restricted first.
  2. On the project page, click ... next to the section name (Section options) and choose Share....
  3. In Share section, pick for each restricted member No access, Can view or Can edit.

Access to a section covers all its tasks and subtasks, including tasks added later. A section that is shared shows a small people icon next to its name, and the Members page shows per restricted member how many sections they can reach.

A restricted member never sees the names of other sections, the member list, the project status, rates, budget, invoicing or anyone's hours.

A financial section cannot be shared: it stays with the owner and managers.

Changing a restricted member to another role removes their shared sections: every other role already sees the whole project.

Change a role

On the Members page, pick another role in the dropdown next to the person. It takes effect straight away. The owner's role is not in the list; to change that, hand the project over. Your own role shows without a dropdown too.

Hand a project over

Only the owner can make another member the owner:

  1. Open Members in the project settings.
  2. Click ... next to the person and choose Make owner.

What happens:

  • From then on the new owner can delete the project, hand it over and link it to GitHub or Sentry. You stay on as Manager and keep running it with them, as long as the new owner's plan includes managers.
  • The project moves onto the plan of the new owner. It has to fit within their limits on projects and people, or the handover is refused.
  • If their plan does not include rates and budgets, those go out of sight for everyone on the project. What is filled in stays.
  • If the new owner already uses the same task key in another project, the key of this project changes, and older references in commit messages stop matching.

Remove a member

On the Members page, click ... next to the person and choose Remove from project. Their access goes, their shared sections go, and tasks assigned to them are left to nobody. The hours they logged stay on the project, because they may still have to be invoiced.

The owner cannot be removed, and neither can you yourself: that is what Leave project is for.

Leave a project

Every member except the owner can leave a project on their own. Click ... (More) at the top right of the project and choose Leave project.

  • You lose access to its tasks, and tasks assigned to you are left to nobody.
  • A timer you had running on that project is stopped. Your logged hours stay.
  • The owner gets a message that you left.
  • This also works on a completed or archived project.

The owner cannot leave. Hand the project over to somebody else first.

How people count toward the limit

The number of people in the plan of the project owner is counted across all their running projects together, not per project.

  • The owner counts too.
  • Somebody in four of your projects takes one place.
  • Every role counts, Reader and Restricted included.
  • An open invitation already takes the place it is about to fill. Revoking it gives the place back.
  • Archived projects give their people back.

When the limit is reached, inviting is refused with a message that names the way out. The numbers per plan are in Plans and limits.

Archived projects

On a project with the status Archived, members cannot be invited, removed or given another role. Reopen the project in its settings first. Leaving an archived project is always possible.

Last changed on 6 October 2026

Back to the manual