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 subscription, the central (parent) space has extensive control over consent management for all sub-spaces (local spaces).
What the Central Space can do
The Central Space is the primary manager of the organization's consents.
The Central Space can:
Manage the consents of local spaces from the Central Space.
Define the default compliance mode that applies to all subspaces.
Create shared purposes and distribute them to all sub-spaces. These purposes are visible to local spaces but cannot be modified by them.
Define default purposes, which automatically apply to all sub-spaces.
Create a generic shared purpose shared with the entire organization and all subspaces (useful for national communications or global compliance requirements).
Send a national communication from the central space.
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 default compliance mode | ✅ | ❌ |
Create shared purposes | ✅ | ❌ |
Edit shared purposes | ✅ | ❌ |
View shared purposes | ✅ | ✅ |
Set default purposes for sub-spaces | ✅ | ❌ |
Create local purposes | ❌ | ✅ |
Manage local space consents | ✅ | ❌ |
Send a national communication | ✅ | ❌ |
💡 Best practices
Define, at the central level, the purposes that apply to your entire organization (e.g., national newsletter, campaign, event, etc.).
Use the default purposes to ensure that no local space begins operations without a compliance framework.
Allow local spaces to create purposes specific to their scope of action.
Use the consent registry (in Advanced Compliance) to regularly audit the consents collected at all levels.
To learn more about general consent configuration, see our article: How to manage consents in Qomon?
Si vous avez des questions ou besoin d'aide, contactez-nous via le chat de la plateforme ou à l'adresse [email protected]