Team members
Invite colleagues and clients, choose what each of them can see, and how seats are counted on your plan.
Roles
Everyone in a workspace has one of four roles. Owners and admins reach every project. Members and clients reach only the projects they have been granted, and see nothing at all until they have at least one.
| Role | What they can do |
|---|---|
| Owner | Full access, including billing, ownership transfer, and deleting the workspace. |
| Admin | Manages projects, forms, and people. Cannot touch billing or delete the workspace. |
| Member | Works in the projects you grant them. Sees nothing outside those projects. |
| Client | Read-only access to the projects you grant them. Cannot change anything. |
Across the workspace as a whole, the roles break down like this:
| Owner | Admin | Member | Client | |
|---|---|---|---|---|
| See usage and the plan’s quota | Yes | Yes | Yes | No |
| Create projects | Yes | Yes | No | No |
| Invite, change and remove people | Yes | Yes | No | No |
| Issue and revoke API keys | Yes | Yes | No | No |
| Connect workspace integrations | Yes | Yes | No | No |
| Read the security log | Yes | Yes | No | No |
| Billing and changing the plan | Yes | No | No | No |
| Transfer a project to another workspace | Yes | No | No | No |
| Delete the workspace | Yes | No | No | No |
Inside a granted project, a member works as an Editor or a Viewer, whichever you chose. A client is always a Viewer: they can read and export submissions but cannot change anything. Renaming a project, deleting it and managing who can reach it stay with owners and admins, whatever a member's grant. Projects covers the two access levels.
Seats
Each plan includes a number of seats. Owners, admins and members use one; clients do not, so you can give every client a login without paying for it.
| Plan | Seats |
|---|---|
| Free | 1 |
| Pro | 3 |
| Agency | 10 |
A pending invitation for anyone but a client holds a seat until it is accepted, revoked or expires, so you cannot invite past your limit and only find out when someone clicks the link. The seat count sits at the top of the Team page.
- 1
Invite someone
Open Team in the sidebar. Only owners and admins see it. Under Invite somebody, enter their email address and choose a role.
- For a
memberorclient, tick at least one project under Projects they can reach, and for a member pick the access level. - You can only give a role at or below your own, so an admin cannot invite an owner.
- For a
- 2
They accept
We email them a link. They sign in, or create an account, with the same address the invitation was sent to; signed in as anyone else, the link refuses and says which address it expects. Unused invitations expire after seven days and can be revoked from the pending list before then.
- 3
Change access later
Change someone's role from the Team list, and change which projects they reach from each project's settings.
Promoting someone to owner or admin clears their project grants, because their access now comes from the workspace. Demote them later and you will need to grant projects again.
Removing people
Removing someone from the Team list takes away their workspace role and every project grant in one step. An admin cannot remove or change an owner.
A workspace always keeps at least one owner. The last owner cannot be demoted, removed or leave; promote someone else to owner first. Owners and admins who also belong to another workspace can leave from the bottom of the Team page. Members and clients do not see that page, so they ask an owner or admin to remove them.