An AI visibility study often involves several people: a developer runs collection, an analyst reviews the answers, and someone else manages the subscription. ProtoScrape workspaces let those people use separate logins while sharing one account’s Google SERP, Google AI Mode, ChatGPT and Perplexity jobs.
Open Team & access to name your workspace and invite teammates. Each person keeps their personal workspace and can switch between the workspaces they belong to. Credits, results, keys, spending limits and subscriptions belong to the selected workspace. Joining another account does not move credits or create a second introductory allocation.
Choose the access each person needs
| Role | What they can do |
|---|---|
| Owner | Manage data collection, keys, spending controls, webhooks, billing and all team roles. |
| Admin | Manage collection, keys, spending controls and webhooks. Invite or manage developers and viewers. Billing remains separate. |
| Developer | Collect data, manage shared jobs, batches and schedules, and use assigned keys. |
| Viewer | Read and export shared results and usage. Assigned API keys are read-only. |
| Billing | Review usage and credit activity, buy a plan and manage the subscription. Prompts, results and API keys are not available to this role. |
Only the owner can grant or remove admin and billing roles. The owner cannot be removed, reassigned or leave their owned workspace through team controls. Developers and viewers can rotate or revoke their assigned keys; an owner or admin sets the key’s permissions and credit limits.
Invite a teammate with their verified email
Enter the teammate’s email, select a role and create an invitation. Copy the link while it is displayed and send it privately to that person. ProtoScrape does not send an invitation email automatically.
The invitation expires after seven days. The recipient signs in with the invited, verified email, reviews the workspace and role, then explicitly accepts. A link alone cannot grant access to a different email. You can revoke pending invitations from Team & access.
Workspaces support up to 20 members, including the owner and seats reserved by pending invitations. Each login can belong to up to 20 workspaces, including its personal workspace. These are initial product limits, not a throughput guarantee.
Assign a key for an application
In API keys, an owner or admin chooses the member responsible for a key. Give applications separate names, expiry dates, permitted submission engines and daily or monthly credit caps.
There can be up to 50 active keys in a workspace. A key stays attached to its original workspace and member. Your Node.js, Python, Go or PHP client only needs that key; it does not need a workspace selector or a separate team credential. See the SDK installation guide.
Data access is shared within a workspace for owners, admins, developers and viewers. A key’s engine restrictions limit what it can submit; they do not hide other engines’ existing results. Nested projects and separate project budgets are not available in this release.
Remove access without losing accounting history
Removing a member or changing their role revokes their existing keys. Pending work created through that membership cannot start new jobs, and affected schedules pause when checked. Rejoining does not restore those keys or automations: assign new keys and recreate the collections that should continue.
Jobs already admitted may finish. Successful jobs charge the workspace once; failed, cancelled and expired jobs release their reservations and use zero credits. Removing a teammate does not erase invoices, completed work or accounting records.
Owners and admins can see the latest 50 access changes in Team & access, with an audit retention of 90 days. Use the history to review invitations, role changes and removals.
Keep support and billing clear
Support conversations remain private to the person signed in, even when they switch workspaces. Include the workspace ID and a job or invoice reference when requesting help; never include secrets.
Billing controls apply to the selected workspace. Review that workspace before opening a hosted checkout or subscription portal. Existing hosted payment sessions have their own expiry, so removing a billing role does not recall a session that was already opened.
Shared workspaces do not change collection coverage or operating limits. Check the engine catalog and API documentation, service status and the workspace’s available credits before starting a study.