Skip to main content
An organization is your team’s workspace — it owns all studies, AI tests, personas, templates, billing, and API keys. Users can belong to multiple organizations and switch between them, which is how agencies keep client work separated.

Inviting members

Owners and admins can invite teammates by email from the organization settings. Members sign in with email/password or Google, and can secure their account with multi-factor authentication (TOTP authenticator apps). The number of seats is set by your plan. If Google sign-in fails, Versive shows a general sign-in error. Retry signing in; if the problem continues, contact support.

Organization roles

Only owners and admins can add, change, or remove members.

Single sign-on (SAML)

Enterprise organizations can sign in through their own identity provider (Okta, Microsoft Entra ID, Google Workspace, and other SAML 2.0 providers).
  • How it works — enter your work email on the login page, or choose Continue with SSO. If your email domain is set up for single sign-on, Versive sends you to your identity provider and back; no Versive password is needed. Sign-in starts from the Versive login page; to add Versive to your identity provider’s app dashboard, add it as a bookmark to the login page.
  • Membership — people who sign in through SSO for the first time join your organization automatically with the default role your organization chose (Creator unless configured otherwise). Existing members who switch to SSO keep their role. Who can sign in is decided by who your IT team assigns to Versive in your identity provider. To remove someone, remove them in both places: in your identity provider, so they can’t sign in again, and from your organization in Versive, which ends their access right away (removing them in the identity provider doesn’t end a session they already have). People removed only in Versive rejoin on their next SSO sign-in.
  • Invitations — people at your SSO domain aren’t invited: they join by signing in, and an owner or admin can change their role on the Team page afterwards. Invite people outside your SSO domain, such as contractors, as usual.
  • Setup — your IT team creates a SAML app for Versive in the identity provider and shares its metadata URL; Versive registers it against your email domain. SSO is part of the Enterprise plan: talk to sales to add it, or contact [email protected] to set it up if you’re already on Enterprise.

Organization settings

Organization settings are split across tabs:
  • Team — your organization name, the logo shown in your workspace, and members.
  • Plans — your subscription and billing.
  • Settings — study defaults, embed domains, AI apps, and uploaded file downloads, covered below.
  • API — organization-scoped keys for the public API, available to enterprise organizations.

Study defaults

Every study carries its own settings — the branding participants see, the languages they can take it in, and how many responses it accepts. Rather than set up each new study by hand, owners and admins can set what new studies start from under Organization > Settings > Study defaults: The card has the same colors and Accessibility check as a study’s Branding tab: it warns when the text is hard to read on the background, or the primary color does not stand out from it. Saving still works. Three things are worth knowing about how these are applied:
  • They are copied in at creation, not linked. A study takes a snapshot of the defaults the moment it is created and owns its settings from then on, so changing a default later leaves existing studies alone. To change a study that already exists, edit its own Branding, Languages, or quota settings. To restyle every study at once, use Apply to existing studies.
  • An explicit choice always wins. Only settings the creator left unset are filled in from the defaults. This holds however the study is created — the dashboard, the API, the AI agent, or the Figma plugin. A study from the Figma plugin keeps the plugin’s language, since its questions are written in it. Studies duplicated or created from a template keep the source’s settings and are not touched at all.
  • They are defaults, not locks. Anyone who can edit a study can still change these values on that study — for example, raise its response limit — and the change affects that study only.
Apply to existing studies writes the saved logo and colors into every study of the organization, after a confirmation that shows how many studies will change and the values they will get. A blank default leaves each study’s own value alone, archived studies are skipped, and the change cannot be undone. Save your edits on the card first; the button applies what is saved. It doesn’t change a study’s title, languages, or response limit.

Embed domains

The domain allow-list required before a study can be embedded with the Embed SDK. Studies cannot be embedded anywhere until at least one domain is added.

AI apps

Apps connected through the MCP server, such as ChatGPT, Claude, and Cursor, can read each response’s metadata: the URL parameters on the participant’s link and fields from uploaded contact lists or the API, such as email. Agents use it to split results by segment and to follow up with participants. The participant’s session token (the vid on invite links) is never shared. This is off by default. Owners and admins turn it on with Share participant metadata under Organization > Settings > AI apps. While it’s off, connected apps receive no participant metadata at all. The setting doesn’t change what the assistant inside Versive can see.

Uploaded file downloads

Uploaded files are the images and videos participants upload, the screens uploaded to AI tests, persona source files, and the images, videos, and PDFs uploaded to questions. Figma prototypes, embedded websites, and AI test screens from Figma or website tests aren’t uploaded files, so they keep their links. When Allow downloading uploaded files is off, Versive offers no download for these files. People can still see them in Versive. Persona source files show by name only, and so do uploads in a file type that can carry code, such as SVG, or that the browser can’t draw, such as HEIC in Chrome. This is on by default. Owners and admins can change it under Organization > Settings > Uploaded files. While it’s off: Recordings (including audio and video files imported as interviews), clips, transcripts, the responses CSV, and insights, report, and AI test exports don’t change. The setting removes Versive’s ways to download these files. It has limits:
  • Anything shown in a browser can still be saved by the person looking at it.
  • Question media on a live study stays visible to anyone with the study link.
  • Members can still open question media from any signed-in browser.
  • A direct file link handed out before the setting was turned off works until it expires, up to 24 hours later. Get interview media links to uploaded files stop working right away.
  • Public sharing links keep working. Anyone with the link can see the participant uploads on a shared interview, the screens on shared AI test results, and the question media on shared study insights, without signing in. Revoke the link to stop that.

Two permission layers

Organization roles set what someone can do globally. Access to specific folders and studies is refined by a second layer — folder & study roles. A user’s effective access to a study is the combination of both.