Inviting your team

You can give a colleague access in two different ways: bring them into the whole workspace, or give them access to just one project. Which one you pick decides what they can see.

Invite someone to the workspace

1. Open your workspace settings and go to the People page.
2. Click Invite.
3. Enter their email address.
4. Pick an account role: Member or Admin.
5. Send the invite.

They’ll get an email to join. Until they accept, they show up on the People page marked Pending, and you can’t yet add them to a project from there.

Joining the workspace does not, by itself, put anyone on a project. Once they’ve accepted, add them to the specific projects they should work on.

Give someone access to a single project instead

Use this when a colleague only needs one project, not the run of the whole workspace. It also works for people who aren’t part of your workspace at all, as long as they already have a Workover account somewhere.

1. Open the project and go to its Project settings.
2. Under Members, type their email address into the “Add member by email” field and click Add.

The person needs an existing Workover account before you can add them this way, there’s no invite-by-email step at the project level. If they don’t have one yet, either invite them to a workspace first (see above) or have them sign up, then add them to the project by email.

They’re added with the Member role by default. If you want them to manage the project itself, go to the workspace’s People page, find them in the list, and change their role for that project from the dropdown next to it.

You can also start from the People page: find the person’s row and use Add to project to add them to any project they’re not already on. This only appears for people already listed there (accepted account members, or people who already have access to another project in your account) and for people who aren’t still pending an invite.

Roles and what each can do

Roles work at two separate levels: an account role that applies to the workspace as a whole, and a project role that applies to one project at a time. A person can hold a different role on each project they’re part of.

Account roles

• Owner — set automatically for whoever created the workspace. You can’t assign this when inviting someone, and an Owner can’t be demoted or removed from the account.
• Admin — can invite people to the account, change other members’ account roles, and remove them from the account (an Owner is the only person an Admin can’t touch).
• Member — the default role for anyone invited without picking Admin. A Member has no management rights over the People list and can’t invite, change roles, or remove anyone.

An account role on its own doesn’t open any project. A Member or Admin still needs to be added to each project they should work in.

Project roles

• Owner — assigned automatically to whoever creates the project. Every project always keeps at least one Owner, so the last one on a project can’t be removed or changed to another role.
• Admin — can add, remove, and change the role of anyone on that project, and can change its connection settings (things like the linked site or repository).
• Member — the default role for anyone added to a project. Can open, create, edit, and comment on the project’s documents, and can rename the project, but can’t manage who else has access or change its connection settings.

An Owner or Admin of the account itself can also manage membership on any project in that account, even one they haven’t personally been added to.

Removing access

Removing someone from the workspace and removing them from a project are separate actions. On the People page, use the person’s menu to remove them from the account; use the remove control next to a specific project to take away just that project’s access. Removing someone from the workspace does not automatically take them off any project they were added to individually, so check both if you want them fully cut off.