Controls: what it does and where to start
Controls governs who can do what, what content is allowed, and how inventory is described to buyers. Every product reads its rules from here.
Roles decide who can change what, in BCC and inside each community. Moderation, guidelines, and blocklists decide which content runs. Your brand safety profile describes your inventory to partners and buyers, and it sets the floor they pay. Player and feed settings decide how each placement behaves, without code.
You don't write these rules from scratch. Each capability below arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. Read Controls: roles, moderation, brand safety, and guidelines first for the full model.
Get started
- Invite your team and assign roles. Give content, revenue, and engineering the access they need and nothing more.
- Set moderation, roles, and brand safety. Every post passes rules you chose before anyone sees it.
- Structure communities and groups for relevance. Groups are the feeds your rules and roles apply to.
Set the rules
| Control | What it sets | When to set it |
|---|---|---|
| Business Account Roles and Scoped Roles | Owner, Admin, Content, Revenue, Developer, and Analyst roles, each scoped to a brand, network, or community | Any team larger than one |
| Community Roles and Creator Tiers | Host, Contributor, Member creator, Partner, and Buyer roles inside communities | Any community with creators, partners, or buyers |
| Moderation Baselines and Queue | Standard or Strict baselines, and a queue with SLA timers, bulk actions, and appeals | Before go-live, on every network |
| Brand Safety Profile | A GARM-aligned description of your inventory that partners and buyers see | Before you connect any demand |
| Keyword and Topic Blocklists | Lists that apply to content and ads at once | Regulated industries, competitor exclusions, and sensitive topics |
| Community Guidelines and Appeals | Your rules on top of Genuin's policy floor, shown on first post and on every appeal | Before go-live |
| Player Controls and Feed Settings | Autoplay, sound, captions, buttons, sticky player, and Maya's parameters per page type | Any time, and changes apply live |
| Audit Log, Two-Factor, and SSO for BCC | Change history, two-factor enforcement, and SSO for BCC on Enterprise | Regulated or multi-team accounts |
Rules that reach other products
- Blocklists and ad quality controls: your exclusions applied to every demand source before an ad renders.
- Content policies and community guidelines: Genuin's policy floor, which your guidelines build on.
- Privacy and VPPA: the two-channel data flow: how viewing history and identity stay apart until consent joins them.
- Security, data residency, and compliance: account isolation, encryption, and regional storage.
Build it
Element attributes on an embed override the feed settings in BCC. Embed configuration reference lists them, and Customize the Genuin video player covers sizes, layouts, and the profile menu. To sign members in with your own accounts, set up single sign-on with your identity provider.
The live server API manages community roles from your own systems. You can add moderators to a community and update a group and its members. The role and policy 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.
Questions people ask
- Can I run several brands or clients from one account? Asked by founders and business owners.
- How does moderation work day to day? Asked by content and community teams.
- What security controls can we enforce on our side? Asked by legal, privacy, and security reviewers.
