Team members share an account without sharing credentials. Each member signs in with their own credentials (Google, Microsoft, or email) and is given one of three roles. The account Owner is implicit — there’s only one Owner per account, and that’s you.Documentation Index
Fetch the complete documentation index at: https://docs.streampixel.io/llms.txt
Use this file to discover all available pages before exploring further.
Roles
| Role | Projects | Billing |
|---|---|---|
| Owner | Full access | Full access |
| Editor | Full access (upload, edit, manage) | Full access |
| Finance | View-only | Full access |
| Viewer | View-only | No access |
What each role can do
| Capability | Owner | Editor | Finance | Viewer |
|---|---|---|---|---|
| View project settings | Yes | Yes | Yes | Yes |
| View analytics & sessions | Yes | Yes | Yes | Yes |
| Upload a new build | Yes | Yes | No | No |
| Edit project settings | Yes | Yes | No | No |
| Add / remove custom domains | Yes | Yes | No | No |
| Configure webhooks | Yes | Yes | No | No |
| Generate own API key | Yes | Yes | Yes | Yes |
| View billing & invoices | Yes | Yes | Yes | No |
| Change subscription / payment | Yes | Yes | Yes | No |
| Invite / remove members | Yes | No | No | No |
Only the Owner can invite, remove, or change a member’s role.
Per-project access
Each member has a list of projects they can see. Projects outside that list don’t appear in their dashboard. Use this to share specific work with contractors, agencies, or QA teams without exposing your full portfolio.Invite a team member
Click Invite member
Enter their email. They’ll sign up or sign in using the exact email you invited.
Invitees must sign in with the exact email you invited, using the same method (Google / Microsoft / email password) they originally registered with. Different addresses or different sign-in methods won’t be matched to the invitation.
Edit role or project access
Find the member in the Team list, click Edit, change the role or project list, save. Changes take effect on their next dashboard page load.Remove a member
Click Remove next to the member’s name. They lose dashboard access immediately and all their API keys stop working. Past actions (build uploads, settings changes) stay attributed to them in audit logs.Best practices
- Default new members to Viewer; elevate only when needed.
- Keep each member’s project list minimal.
- For CI/automation, generate an API key from a dedicated Editor account, not a human teammate’s.
Troubleshooting
| Problem | Fix |
|---|---|
| Invitee can’t sign in | Confirm they’re using the exact email you invited and the same method (Google / Microsoft / email password) they registered with. |
| Invitee sees no projects | Edit the member and tick at least one project. |
| Viewer can’t change a setting | Expected — promote to Editor. |
| Finance member can’t upload a build | Expected — Finance is billing-only. Promote to Editor. |
Next
API keys
Each member generates their own keys, scoped to their role and project list.
Billing
Editors and Finance members can manage subscription and payment.