How to collaborate with your team on a survey without sharing your password
When two or more people need to work on the same surveys, the most common workaround (sharing a single account's username and password) creates real problems: nobody knows who made which change, you can't revoke access for just one person without changing the password for everyone, and anyone with the password has the same level of access as the original owner. An organization with roles solves all three at once.
The three roles
Viewer can see surveys and results, but can't edit anything. Editor can create and modify surveys, view results, and manage distribution, but can't invite other people or change the organization's settings. Admin has the same permissions as Editor, plus the ability to invite and remove members and change their roles. The organization owner is the only role above Admin, and it can't be transferred or removed by another member.
How to invite someone
From the Organization section, you enter the person's email and pick their role before sending the invite. They receive an email with a link to accept it; if they don't have a SurvIQ account yet, accepting includes creating one.
Changing someone's role later
Any member's role (except the owner's) can be changed at any time from the same member list, with no need to resend an invite or have the person accept anything again — the change applies immediately.
Personal surveys vs. organization surveys
A survey created inside an organization is visible (based on role) to all its members. A personal survey, created outside any organization, stays private to the individual owner — moving a survey from personal to the organization, or the other way around, is an explicit decision, not something that happens automatically.
Folders to organize shared work
Within an organization, surveys can be grouped into folders (by client, by project, by quarter) and specific members assigned to each folder — useful when the organization has multiple teams working on different sets of surveys, without everyone needing to see everything.
Why this beats sharing a password
Each person logs in with their own account, so there's real traceability of who did what. Revoking access for someone leaving the team is instant (remove them from the organization, no password to change), and each person's access level matches exactly what they need to do, not the full level of the original account owner.