Inviting your team

Adding people to a project by email, choosing the access level that fits what each needs to do, and why that level applies to this project only.

Overview

Members are the people with access to a project. You add them by email and choose what they can do.

Membership lives in Project Settings, one step aside from the project's own views — which is the most common reason people cannot find it (A1.5).

The one thing worth knowing before you start: you do not need to check whether someone already has an account. If they do, they gain access to this project. If they do not, they are invited to create one. The platform handles both cases.

What you'll learn

How to add someone to a project
What each access level grants, and which to default to
Why the level applies to this project only

Before you start

Nothing to prepare beyond the email address and name of each person you are adding. You need to be a Project Admin — an Editor can do the work of a subscription process but cannot manage membership.

Steps

In the project navigation, open Project Settings, then Members (A1.5).
Select Add Member.
Enter their email, first name and last name.
Choose the level — read the hint under each rather than assuming from the name.
Add them. They gain access, and are invited to create an account if they do not have one.

Choosing the level

Level	What it grants
Admin	Full access: manage project members, create, edit and manage companies
Editor	Create, edit and manage companies
Viewer	View the details of companies only

The practical difference between Admin and Editor is membership management. An Editor does the work of a subscription process but cannot decide who else has access.

Default to Editor for people doing the work. Reserve Admin for those who also manage access — which is fewer people than you might think. Use Viewer deliberately, for people who need visibility without the ability to change anything.

Remember the scope

A level applies to this project only. The same person can be an Editor here and a Viewer on the next project, and that is normal rather than a misconfiguration.

Common problems

"Looks like this user is already on the team." They are already a member. Adjust their existing membership rather than adding them again.

Somebody cannot see a control you expect them to have. Check their level. Controls are absent rather than disabled at lower levels, so "the button has gone" is usually the access model working correctly.

Someone needs access to several projects. Add them to each one. Membership is per project, so there is no single grant that covers them all.

You added a Viewer who needs to upload a document. Viewers cannot. Either they need Editor, or the work needs doing by someone who has it.

A1.4 — Roles and what each can see · what each level can actually do
A2.6 — Access control in practice · reasoning about visibility across a project