Team roles and permissions for AI visibility work
Proofsource team roles decide who can only look, who can start fixes, who approves them and who spends credits. Invite people by email or a join link, pick a built-in role or a custom one, limit members to certain brands or categories, and give each person a credit allowance. An activity log with export records what changed. Built for marketing teams, enterprises and agencies.
| Person | Role | Brands | Credit allowance |
|---|---|---|---|
| maya@driffle.ai | Owner | All | No limit |
| sam@driffle.ai | Admin | All | No limit |
| lee@driffle.ai | Content editor (custom) | Driffle | 500 a month |
| cfo@driffle.ai | Viewer | All | None |
Team roles and permissions, in short
The facts, ready to quote.
- Roles
- Owner, Admin, Member, Viewer, Product Viewer and Client login, plus custom roles with per-person credit allowances and requests
- Scoping
- Limit a member to chosen brands or categories
- Approvals
- Only approvers can say Yes to publish when approvals are on
- Joining
- Email invite, invite link, auto-join by domain and join requests
- Audit
- Activity log with export
- Seats
- Invite the whole team; no per-seat charge
Role-based access for AI visibility, explained
Role-based access control (RBAC) means each person in a workspace gets a role that decides what they can see and change. In an AI visibility tool this matters more than it first seems: the same workspace holds read-only reports for executives, edits to tracked questions, fixes that publish to your website, and work that spends credits.
Proofsource separates those powers. Viewers and client logins can read everything they are given and change nothing, and every write control in the app checks the same rule, so there is no button that slips through. Members edit, approvers say Yes to publish, and owners handle billing and the workspace itself. Custom roles add credit allowances per person, with a request flow when someone needs more.
Access can be narrowed further with brand and category grants, client groups for agencies, and a public approve-by-link page so a stakeholder without an account can approve a fix. Destructive actions ask for confirmation, some by typing the name, and an exportable activity log keeps a record.
How it works
Invite your team, give each person a role, limit them to brands, set who approves fixes and who spends credits, and keep an activity log.
Invite people
Send an email invite or share a join link. Invites unfurl as an invitation card in chat apps, and people with your work domain can join or request to join.
Pick a role
Owner, Admin, Member, Viewer, Product Viewer or Client login, or a custom role you define.
Scope access
Limit a person to certain brands or categories, or to a client group in agency mode.
Set credit allowances
Give a person or role a credit allowance. When they need more, they request it.
Choose approvers
Turn on approvals and only approvers can publish fixes. Others can still view and prepare them.
Review the log
The activity log shows who changed what, and exports for your records.
See it in the product
Screens from the Proofsource app, drawn with sample data for an example brand.
Approve this fix for Driffle: add a comparison table to driffle.ai/vs-otter.
| When | Who | What |
|---|---|---|
| Today 9:14 AM | sam@driffle.ai | Changed lee@driffle.ai to Content editor |
| Yesterday 4:02 PM | maya@driffle.ai | Approved fix on /vs-otter |
| Oct 30, 11:47 AM | lee@driffle.ai | Added 4 questions to Sales meetings |
Every capability, live today
12 shipped capabilities behind team roles and permissions, each in the product now.
People settings
Admins invite teammates, list members, change roles and remove people themselves, without a support ticket.
Join screens
Accept an invite, preview a join link, join or request a workspace, and read what each role can do.
Invite link and join requests
A workspace invite link, auto-join for your domain, and join requests for admins to accept. Invite links unfurl as an invitation in chat apps.
Teams
Group people into teams in Settings, People.
Custom roles and allowances
Create your own roles, set credit allowances on a role or per person, let people request more, and see how many people hold each role.
Brand and category grants
Limit a member to certain categories or brands.
One permission rule
One place decides who may do what inside your workspace.
Read-only for viewers
Viewers and client logins cannot change anything; every write control reads the same rule, with a plain notice instead of a broken button.
Approver gate
When approvals are on, only approvers can say Yes to publish a fix.
Approve by link
A public task page lets someone without an account approve or request changes.
Activity log
A customer activity log of changes, with export.
Confirm before deleting
Destructive actions ask for confirmation, some by typing the name.
Who it is for
Least access by default
Executives get Viewer, regional teams get their brands only, and the activity log satisfies internal review.
Edit without spending freely
Writers work on fixes with a monthly credit allowance and request more when a project needs it.
Approve before anything ships
Only approvers can publish, and a reviewer can approve from a link without an account.
Clients see their own data
Client logins see one client or client group, read-only.
Why it matters
No accidental changes
Read-only roles are enforced on every write control.
Spend under control
Credit allowances per person or role, with a request flow.
Invite everyone
No per-seat charge, so the whole team can see the data.
A record of change
Exportable activity log for audits and handovers.
Google AI OverviewsGoogle AI Mode
Team roles and permissions: Proofsource and other tools
Team access is standard in AI visibility tools, with different depths. From each company's own public pages:
| Capability | Proofsource | Profound | AthenaHQ | Peec AI | Otterly.AI | Scrunch | SE Ranking |
|---|---|---|---|---|---|---|---|
| Role-based access | YesSix built-in roles plus custom roles | YesRole-based access and SCIM provisioningSource | YesUnlimited seats with roles on Starter and EnterpriseSource | YesCompany-wide members view with role-based accessSource | YesViewer: read-only member roleSource | YesRBACSource | RelatedRoles not detailed beyond read-only client guest seatsSource |
| Credit allowances per person or team | YesPer-person and per-role allowances with requests | RelatedAI Marketer credits, shared across teamSource | Not listed | Not listed | Not listed | Not listed | Not listed |
| Activity or audit log | YesActivity log with export | YesActivity logs documented in organization settingsSource | YesOrganization audit log on EnterpriseSource | RelatedMembers view with CSV exportSource | Not listed | Not listed | Not listed |
| Seats | YesInvite the whole team | YesUnlimited seats on all plansSource | YesAll plans include unlimited usersSource | YesUnlimited seats on every planSource | YesUnlimited team members on all plansSource | Yes3 or 5 seats; add-on seats availableSource | Not listed |
| Approve a fix by link without an account | YesPublic approve-by-link task page | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
| Read-only viewers | YesViewers and client logins cannot change anything, with a plain notice. | Not listed | Not listed | Not listed | YesRead-only member roleSource | Not listed | YesRead-only client seats limited to chosen toolsSource |
| Teams inside a workspace | YesTeams under Settings, People | YesTeams with own categories, shared resources, credit wallets (Enterprise)Source | Not listed | Not listed | Not listed | Not listed | Not listed |
| Limit people to certain brands | YesPer-member limits by category or brand | Not listed | RelatedAgency page: many brands in one platform with team permissionsSource | RelatedIsolated project per client; unlimited client workspacesSource | RelatedSeparate team, reports, prompts per clientSource | Not listed | RelatedManage team and client accounts in one platformSource |
Where each of them shines
Profound pairs role-based access and SCIM with Teams that carry their own categories and credit wallets. Compare in full
AthenaHQ includes unlimited users with roles and an organization audit log on Enterprise.
Peec AI offers unlimited seats and a company-wide members view with role-based access. Compare in full
Otterly.AI includes unlimited team members and a read-only Viewer role on every plan. Compare in full
Scrunch offers role-based access with enterprise SSO and SOC 2 Type II. Compare in full
Read-only client guest seats limited to chosen tools, alongside agency client management.
Questions about team roles and permissions
What roles does Proofsource have?
Owner, Admin, Member, Viewer, Product Viewer and Client login are built in. You can also create custom roles with their own powers and credit allowances.
Can I stop someone from spending credits?
Yes. Give them a role without spending rights or a credit allowance. When they need more, they send a request.
Can I limit a teammate to one brand?
Yes. Brand and category grants limit a member to the brands or categories you choose.
How do approvals work?
With approvals on, only approvers can publish a fix. Anyone else can view it and get a plain read-only notice. A stakeholder can also approve from a link without an account.
How do people join my workspace?
By email invite, by a shared invite link, by auto-join for your work domain, or by requesting to join for an admin to accept.
Is there an audit log?
Yes. The activity log records changes in the workspace and exports for your records.
Do I pay per seat?
No. Proofsource charges in credits for work that runs, not per person, so you can invite the whole team.
Can I manage users from my identity provider?
Yes. SAML or OIDC single sign-on and SCIM provisioning are available for owners and admins.
Keep exploring
Try it on your own brand.
Proofsource is live: scan your brand and see team roles and permissions at work with your own answers, competitors and sources.
Google AI OverviewsGoogle AI Mode