Users can revoke their previously given consent via contextual links placed above or below the embedded content, or centrally in the site footer. If disabled, revocation remains available via the user profile page.
Users can withdraw their consent.
Pro | |
|---|---|
| Consent Enforcement Prevent external content from loading before users give consent. | |
| Block external content Stop unauthorized data sharing at the source. | ✔ |
| GDPR compliance Respect data protection by design. | ✔ |
| Customizable placeholder Explain before you embed. | ✔ |
| Consent Management Put users in control of their consent decisions. | |
| Consent withdrawal options Consent is not forever – allow users to change their mind. | ✔ |
| Global consent handling Define exactly which policy applies to each service. | ✔ |
| Filter-based implementation Seamless, efficient, and native to Moodle. | ✔ |
| Administrative Settings Configure exactly how and when external content is shown. | |
| Blacklist mode Block only what you specify. | ✔ |
| Whitelist mode Block everything unless approved. | ✔ |
| Role-based capabilities Empower the right users with the right permissions. | ✔ |
| View blocked content capability Let teachers preview all content without restriction. | ✔ |
| External Service Registry Manage all third-party services in one central place. | |
| Preconfigured services Start with the essentials. | ✔ |
| Service editor Add any third-party service with ease. | ✔ |
| Domain mapping Support multiple domains per service. | ✔ |
| Service toggling Enable or disable services site-wide. | ✔ |
| Policy Integration Connect content visibility to Moodle’s native policy system. | |
| Policy binding Link services to existing Moodle policies. | ✔ |
| Flexible policy requirements Choose how strictly to enforce consent. | ✔ |
| Policy update handling Ensure consent is current. | ✔ |
| Null privacy provider No extra data, no extra concerns. | ✔ |