Enterprise governance

Govern consent across every team and entity.

Isolated workspaces, role-based access control and a team activity log keep consent operations accountable, so you always know who changed what, where and when.

Roles
4
Workspaces
Per entity
Default region
Mumbai
Definition

What is consent governance?

Consent governance is the set of controls that decide who in your organization can configure, view and export consent records, and how those actions are recorded. In ConsentPlix it combines workspace isolation, role-based access control and a team activity log, alongside the sealed consent ledger, so accountability obligations under DPDP, GDPR, CCPA/CPRA and LGPD can be demonstrated rather than asserted.

Capabilities

Four controls that keep consent operations accountable.

  • Workspace isolation

    Each brand, entity or region gets its own workspace with separate domains, consent configuration and ledger, so records never mix.

  • Role-based access

    Grant owners, admins, editors and read-only auditors exactly the permissions their job needs, scoped per workspace.

  • Team activity log

    Configuration changes, role grants and exports are recorded with actor and timestamp, giving reviewers an audit-ready trail.

  • Domain control

    Register the domains each workspace may serve the consent widget on, and review scanner results per domain.

Access model

Built-in roles, scoped per workspace.

Workspace roles and their permissions
RoleCan manage
OwnerBilling, workspaces, all roles
AdminWidget, domains, webhooks, members
EditorNotice text, languages, categories
AuditorRead-only ledger and receipts
Organization structureIsolated
ORGANIZATIONENTITY AENTITY BLEDGERLEDGER
How it works

Set up governance in three steps.

Default region AWS Mumbai (ap-south-1).
  1. 01

    Create workspaces

    Mirror your organization: one workspace per legal entity, brand or market, each with its own default region.

  2. 02

    Invite your team

    Assign roles per workspace so legal edits notices, engineering manages the SDK and auditors only read.

  3. 03

    Review the trail

    Every administrative change lands in the activity log next to sealed consent receipts, ready for an audit request.

FAQ

Governance questions, answered.

Can one company manage several brands or entities?

Yes. Create a workspace for each brand, subsidiary or market. Domains, consent settings and ledgers stay separate, while owners can see across all of them.

Can I give an auditor access without letting them change anything?

Yes. The Auditor role is read-only: it can inspect the consent ledger and sealed receipts but cannot edit configuration or manage members.

Are administrative changes recorded?

Yes. Configuration edits, role changes and exports are written to the team activity log with the acting user and a timestamp.

Where is governance data stored?

In the workspace region you choose, with AWS Mumbai (ap-south-1) as the default. ConsentPlix stores only pseudonymous consent records.

Bring accountability to every consent decision.

See workspaces, roles and the activity log configured for your organization in a 30-minute walkthrough.