Administration
Team and roles
The three roles
| Viewer | Editor | Admin | |
|---|---|---|---|
| View forms and responses | Yes | Yes | Yes |
| Export responses | No | Yes | Yes |
| Create, edit and publish forms | No | Yes | Yes |
| Delete forms and responses | No | Yes | Yes |
| Manage option lists | View only | Create and import | Everything, plus delete |
| Invite and manage members | No | No | Yes |
| Webhooks and integrations | No | No | Yes |
| Organization settings and billing | No | No | Yes |
| Organization audit log | No | No | Yes |
Inviting someone
Team → Invite member takes an email and a role. They receive a link; accepting it adds them to the organization with that role. Pending invitations are listed on the Invitations tab and can be revoked, which stops the link working.
Someone can belong to several organizations with a different role in each. The workspace switcher in the sidebar moves between them, and everything on screen — forms, responses, records, option lists — belongs to whichever is active.
Changing a role or removing someone
Use the actions menu at the end of a member's row. The role they currently hold is ticked. Removing someone revokes their access immediately; forms and responses they created stay with the organization.
You cannot change your own role or remove yourself — that is how an organization ends up with no admin.
Choosing a role
Viewer for people who need to read results and nothing more — a funder, a programme lead, a colleague who reports on the numbers.
Editor for the people who build and run forms. This is the working default for most of a team.
Admin for the small number who manage the workspace itself. Admin includes webhooks, which can send every response you collect to an arbitrary address — worth remembering when deciding who needs it.
Super admin is a separate thing
Platform administration runs on its own axis. A super admin is not automatically an admin of any organization, and an organization admin has no platform access. See Platform administration.