Business Account Roles and Scoped Roles
Owner, Admin, Content, Revenue, Developer, and Analyst roles, each scopeable to one brand, network, or community.
Business Account roles decide what each person on your team can see and change in Brand Control Center. Genuin proposes your team from your company type and the people in your email domain's directory, when it's connected. Each teammate gets the access they need and nothing more.
This capability arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. It's part of Controls, and Controls: roles, moderation, brand safety, and guidelines explains how team roles differ from the roles creators and partners hold.
When to use it
Use it for any team larger than one. Agencies and holding companies use scoped roles to run several brands from one Business Account.
Some roles carry specific rights across Genuin:
| Role | What it covers |
|---|---|
| Owner | Signs agreements and changes billing; only Owners can do either |
| Content | Owns the moderation queue |
| Revenue | Approves partners, reads payouts, and gets alerts when an ads.txt line disappears |
| Developer | Often owns the embed and auto login, and gets email when the API or SDKs change |
| Analyst | Read-only access |
How it works
- The proposal has one Owner, plus Admin, Content, Revenue, Developer, and Analyst roles. Each role is scoped to the brands it needs to see.
- Each invitation is drafted with a tour matched to its role. Where your policy or plan calls for it, two-factor authentication is proposed as required.
- In a multi-brand Business Account, the brand switcher moves between brands, and roles can be scoped per brand or per community. Brand communities and groups explains the structure.
- Team roles cover your staff. Creators, partners, and buyers get community roles and creator tiers instead.
- Octo acts only with the permissions of the role using it.
- Record who owns what under Brand > Context. Approvals and support requests then reach the right person.
Set it up
Octo proposes the team with these steps already done. You review the result and confirm it.
- Invite each teammate under Settings > Team. Learn how in Invite your team and assign roles.
- Pick a role for each person, and add a scope when the role covers one brand, network, or community. Choose Approve and send to send the invitations.
- Review each change in the audit log. Audit Log, Two-Factor, and SSO for BCC covers the log and its export.
Settings
| Setting | What it controls |
|---|---|
| Role | Owner, Admin, Content, Revenue, Developer, or Analyst |
| Scope | Optional; limits the role to one brand, network, or community |
| Two-factor requirement | Whether the teammate signs in with two-factor authentication |
Add, remove, or re-scope anyone inline before you approve. As the team grows, Octo proposes role changes, for example when a partner's editor needs access to one group.
What it reports
The audit log under Settings > Audit starts recording when the invitations go out. Security, data residency, and compliance explains how it fits with Genuin's other account controls.
- Change history: every change, recorded by user and time.
- Octo actions: each action Octo took, with the approval or rule that allowed it.
Connect your systems
Roles run in Brand Control Center and need no code. Add moderators to a community gives accounts the moderator role from your own systems. Update a group and its members adds or removes group members and changes group settings. Generate an access token exchanges your API key and secret for the token every other call needs. Environments, credentials, and test data explains the separate QA and Production credentials.
The team and role calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
