Why is there specific consent management for decentralized organizations?

Organizations with multiple sub-spaces (local chapters) need to ensure consistent compliance across the entire organization while enabling local teams to operate effectively.

With the Expert 2 plan, Qomon gives the central (parent) space full authority over the compliance framework, while still allowing local spaces to operate with flexibility within that framework. This means you can enforce organization-wide standards without having to manage every local consent manually.

What the Central Space can do

The Central Space is the primary manager of the organization's consent configuration. From the central space, you can:

Set the compliance mode for the entire organization. The compliance mode you choose (Essential or Advanced) is locked at the organization level and local spaces inherit it automatically and cannot override it. They will see an "Organization" indicator on their settings page to signal this.

Create shared purposes and distribute them to all sub-spaces. Shared purposes are visible to local spaces but cannot be modified by them.

Manage Organization and Subspace Consent Purposes from two dedicated tabs in your settings, giving you a clear view of what's defined centrally versus what local spaces have created for themselves.

Send national communications from the central space, using purposes shared across the entire organization.

💡 Reminder: Purposes from the central space are not automatically shared with subspaces. To enable purpose sharing and understand how it works for your organization, contact our support. Once set up, shared purposes are visible to local spaces but cannot be modified by them.

What local spaces can do

Local spaces:

Automatically inherit the compliance level and purposes defined by the central space.
Can view shared purposes but cannot modify them.
Can create their own purposes, tailored to their specific needs (local campaign, regional event, chapter newsletter, etc.), in addition to those defined by the central space, within the framework defined by the central space.

Overview of a Contact's Consents

From a contact's profile, you can view all the purposes for which that contact has given consent, whether they are defined centrally or locally.

This provides a comprehensive, unified view, facilitating audits and compliance.

In summary: Who does what?

Action	Central space	Local sub-space
Set the compliance mode for all spaces	✅	❌
Create & manage shared purposes	✅ (contact our support)	❌
Create & manage local purposes	✅	✅
View shared purposes	✅	✅
Set default purposes for sub-spaces	✅	❌

💡 Best practices

Define at the central level the purposes that apply to your entire organization (national newsletter, campaign, events, etc.) and set them as defaults so every local space starts with a compliance framework in place.
If you want to share purposes with your subspaces, please reach out to our support early, as this needs to be set up before local spaces start collecting consent.
When creating a shared purpose, consider enabling "Preselect by default" in the consent settings page.
If shared to sub-spaces, it ensures the purpose is automatically displayed on forms, petitions, and events across all sub-spaces, without relying on local teams to configure it themselves.
Allow local spaces to create their own purposes for anything specific to their scope: local campaigns, regional events, chapter newsletters, etc.
Use the consent registry (Advanced Compliance) to regularly audit consents collected at all levels of the organization.