Teams and workspaces
A workspace is the container for a set of surveys, contacts and settings. Your account can hold several, and people are invited into a workspace rather than into the account as a whole.
How many you get
Section titled “How many you get”| Plan | Workspaces | Staff seats | Client seats |
|---|---|---|---|
| Free | 1 | 1 | — |
| Solo | 1 | 1 | — |
| Team | 3 | 5 | 2 |
| Growth | 10 | 10 | 20 |
| Pro | 25 | 25 | 50 |
| Enterprise | Custom | Custom | Custom |
Staff seats are for people who build and send surveys. Client seats are read-only and exist for agencies sharing results with the client the work is for — a Viewer consumes a client seat, every other role consumes a staff seat.
Free and Solo have a single workspace; creating additional ones starts at Team.
Inviting someone
Section titled “Inviting someone”Go to /workspace-users and choose Invite Members. Enter an email address, pick a role, and choose Send Invitation.
The roles offered are:
- Admin — full access. Only an Owner can invite an Admin.
- Editor — create and edit surveys.
- Viewer — read-only, and the one that uses a client seat.
The invitee gets an email — “You’ve been invited to join {workspace} on SurveyRock” — with a link that is valid for seven days. They must accept using the address the invitation was sent to; signing in with a different address will not attach them to the workspace. You can resend or cancel a pending invitation at any time.
Pending invitations count against your seats, so a seat is held from the moment you invite rather than from the moment they accept. If you are at the limit you will see “Seat limit reached. Please upgrade your plan to invite more members.”
What each role can do
Section titled “What each role can do”| Role | Surveys | Sending | Results | Can see PII | Delete surveys | Account admin |
|---|---|---|---|---|---|---|
| Owner | Full | Full | Full | Yes | Yes | Members, settings, branding, billing |
| Admin | Full | Full | Full | Yes | Yes | Members, settings, branding — not billing |
| Editor | Full | Full | Full | No | No | None |
| Viewer | View only | No | View only | No | No | None |
| No access | None | None | None | No | No | None |
Two distinctions catch people out. Admin cannot access billing — that stays with the Owner. And Editor cannot see personally identifiable information in responses, and cannot delete surveys, which is usually what you want for someone building surveys rather than running the account.
Custom roles, permission groups and directory sync are Enterprise features.
Archiving and restoring a workspace
Section titled “Archiving and restoring a workspace”Archiving takes a workspace out of the way without deleting anything. Every survey in an archived workspace stops accepting responses, so archive a workspace only when you genuinely want collection to stop — this is the part people are surprised by.
Archived workspaces are at /workspaces?status=archived. The three-dot menu on each row offers Restore.
Two guards apply: you cannot archive your last active workspace, and a restore is refused if it would take you over your plan’s workspace limit.
Removing someone, and transferring ownership
Section titled “Removing someone, and transferring ownership”Removing a member reassigns their surveys rather than orphaning them, so nothing disappears when somebody leaves.
To transfer ownership, go to Workspace Settings → Danger Zone → Transfer Ownership, pick an eligible member, and confirm with your password.
You cannot delete your account while you still own a workspace — transfer ownership first, or the deletion is refused.
Things to know
Section titled “Things to know”Survey activity history appears as included on Team and above in the plan comparison, but the feature still shows a “Coming Soon” badge in the product. It is not available yet.
There is no in-product view of team activity — who changed a role, who was invited, who removed whom. Those actions are recorded, but viewing them is not self-serve today. Contact us if you need that record.
Data Retention Defaults in Workspace Settings describes itself as applying “in this workspace”. It is actually account-scoped, so changing it affects every workspace on the account. Worth knowing if you run several.
An occasional “No active workspace context found” error can appear when following a deep link into a workspace on a fresh session. Opening the workspace from /workspaces first clears it. We are working on this one.