People, access and billing

Follow the four-step survey guide for the end-to-end path, including local testing, team review, fieldwork and export.

Account, Script and Run access

An Account stores its members and shared prepaid balance for QubeSurvey services, including AI usage. A Script separately stores its collaborators and project roles. Account membership, Script access and Run-progress reporting are separate permissions; the server checks the relevant permission for each action. An Account owner or administrator can manage billing and account-wide controls, but that role does not grant a project role on every Script.

Script roles are managed on the Script’s People view in the workspace. Owners can invite colleagues, change an existing member’s role and remove a member. Editors can change Script source; testers and viewers have narrower review access. Ask a Script owner about access to a particular Script.

Open Settings → Permissions and choose an Account to review its members and invitations. Account owners and administrators can create an invitation link: choose Viewer for Account access or Admin for Account membership and account-wide controls, then copy and share the link yourself. This action does not send email. The link expires after seven days. The invitee must sign in with the same verified email address. You can revoke a pending invitation on the same page. Neither Account role grants a role on an individual Script or project.

Run-progress roles

On Permissions, Account owners and administrators can see aggregate Run progress for the selected Account. Other Account members can see progress only when assigned a role. The current capability is View Run progress: Run names, status and aggregate attempt counts. An administrator can create a named role and assign it to all Runs in the Account or one Run, then revoke an assignment when access should end. These roles do not grant Script editing or access to responses, answers or participant contacts.

Owners and administrators can also change another member’s Account role or remove them from the Account. The owner role cannot be changed or removed here, and you cannot change your own membership. Removing Account access also revokes that member’s Run-progress assignments for the Account. Script and project roles are managed separately and remain in place; review them on each Script’s People view when removing a colleague from an Account.

Operations access

Operations is a system-wide page for explicitly assigned operators and auditors. Account and Script permissions do not grant this access. Auditors can review operational metadata; operators can manage workspace account status and credit allocations. An Account admin is not automatically a system operator.

Use Settings in the signed-in product bar for the selected Account’s Billing and Permissions. Connected apps manages hosted MCP access granted to external apps; using the local MCP from an editor does not require a hosted connection. See the MCP guide for connection details.

Creating a hosted Script

Signing in and having an Account are two different things. Signing in is your identity. An Account is the billing and ownership container that holds the prepaid balance, the people who can see its Scripts, and the Runs it pays for. A new identity has no Account until it creates one under Billing; the workspace says “No Account is available” until then. Creating an Account is free and does not require a payment.

Choose the Account that will own a new Script. A configured identity provider can allow new account registration without an invitation. After signing in, you can create your own billing Account and Script as its owner. Email sign-in links are limited to existing accounts and the exact address on a current project invitation. To work in someone else’s Script, its owner must add you with the required Script role. Existing collaborators keep their separate Script access. Older APIs may call a Script a project.

Prepaid balance and rates

Creating a Script, testing it in Script preview, and filing manual tickets do not use prepaid credit. Team members can test Script previews; responses collected through a Run use the response rate. Local authoring and interview testing with the QubeSurvey extension also work without a hosted Account. Add prepaid credit through Billing in the QubeSurvey workspace. Credit is shared across metered QubeSurvey services for the selected Account. Billing shows the available, reserved and total balance. Live credit purchases use Stripe; sandbox credit cannot fund live usage. Charges from a third-party provider used by your editor agent are separate.

For USD Accounts, accepted responses cost US$0.10 each. An accepted response is a finished interview whose answers are kept — whatever its ending is called. A screened-out or partial ending that keeps its data is charged exactly like a completion and appears in the export; an ending that keeps nothing is free and returns no data. Interviews that are still open or abandoned are not charged. The Keep data (charged) box in Run Settings is the control that decides this. When survey email delivery is enabled, invitations and reminders cost US$0.01 per message accepted by the email provider. Hosted Assistant tasks and AI service calls are billed at measured provider cost plus 50%; review the maximum charge before starting a task. Sign-in and billing notices are free and rate-limited. Answer exports are free.

Your profile

Open the profile menu to view your account and choose Light, Dark or Auto. Auto follows your device’s colour preference. The QUBE applications share the profile and theme foundation.

When you open a page that needs an Account and the link does not name one QUBE reloads the last Account you chose instead of asking again. A link that names an Account is always honoured, even if that Account is unavailable to you.