Portal vs WP Admin: What Lives Where
|
Applies to: WordPress Plugin + Admin Portal WP Admin: All four tabs (Overview / Cookie Consent / Privacy Consent / Consent Logs)
|
Overview
Cookie Compliance has two management interfaces: the WordPress admin (inside your WordPress dashboard) and the Admin Portal (at app.hu-manity.co). Some settings live in one interface only; others are accessible from both. This article maps every feature to the correct interface so you always know where to go.
WordPress Admin Tabs
The WordPress plugin interface has four tabs:
- Overview — Status verdict, six status boxes (Banner, Script blocking, Google Consent Mode, Meta & Microsoft, GPC signal, Visit limit), 7-day consents count, Next steps
- Cookie Consent — Your banner panel (engine; Standard or Compact style on the New engine), Laws, languages & signals card (including the Consent Signals panel), setting cards, privacy policy link, custom scripts, display/animation, technical settings. An unconnected Banner Only site also has banner design, consent behavior and cookie expiry
- Privacy Consent — Choose which forms record privacy (form) consent
- Consent Logs — Consent log viewer, Form Consent records, and CSV export (Professional plan)
Admin Portal Navigation
The Admin Portal at app.hu-manity.co has the following pages accessible from the left sidebar:
| Page | Portal URL | Purpose |
|---|---|---|
| Dashboard | /#/dashboard |
Domain activity charts, page view analytics, consent log summary, top languages, live consent/visit counters, autoblocking activity, device breakdown |
| Configuration | /#/configuration |
Laws, Content, Behavior, Design, Consent Signals (consent modes), and Privacy |
| Autoblocking | /#/autoblocking |
Add, edit, and delete script providers per cookie category; manage URL blocking patterns |
| Consent Logs | /#/consentlogs |
Cookie consent and privacy consent log tables; date-range export with IP/email anonymization (Professional) |
| Languages | /#/languages |
Add and manage banner translations per language |
| Integrations | /#/integrations |
WordPress plugin setup instructions and manual JS embed code |
Additional portal pages (not in left sidebar): Account (/#/account), Preferences (/#/preferences), API Tokens (/#/api-tokens), Add Domain (/#/add-domain).
Portal Configuration pages
The Configuration page (/#/configuration) has six pages: Laws, Content, Behavior, Design, Consent Signals, and Privacy. The old Privacy Teller tab is not a page; its text fields are not editable in the portal.
| Page | What It Controls | Pro Only? |
|---|---|---|
| Laws | Regulations, site-wide autoblocking, geolocation method, and per-law rules (Banner Display, Update consent, Autoblocking, Privacy Policy, Do Not Sell Link) | Mixed |
| Content | Banner text (heading, body, button labels), access-level names and descriptions, and the Protection / Metrics labels | No |
| Behavior | Number of choices, default consent level, Update consent, consent on close / click / scroll, UI blocking, reloading, consent expiry, privacy-policy link, Do Not Sell link. Classic engine only: consent on close / click / scroll, UI blocking and the link targets (same or new tab). The New engine ignores them, so they are not shown on a New-engine site; their saved values still apply if you switch back to Classic. | Mixed |
| Design | Banner position (top, bottom, left, right, center/popup), display type (floating/fixed), Update consent icon position, icon margins, colors, font. Banner engine is in the header, not here. | Mixed (Update consent icon margins are Pro) |
| Consent Signals | Google, Facebook, and Microsoft consent modes (including category maps), GPC, and Do Not Track. Not the left-nav Integrations page, which holds the App ID and install snippet | Mixed |
| Privacy | Privacy Paper (heading, body, access / data-types / benefits / rights; Classic engine only, not offered on a New-engine site) and Privacy Contact (name, phone, email, address, rights / opt-out / complaint links) | Yes (both sections) |
Feature-by-Feature Comparison
Use this table to find which interface controls each feature:
| Capability | Portal | WP Admin |
|---|---|---|
| Script blocking engine (master switch — off means nothing is blocked for anyone) | No | Yes — Cookie Consent tab → Script blocking engine card (plugin 3.1.10+). On a snippet install, the blockingEngine key instead |
| Autoblocking (block before consent) | Yes — Configuration → Laws, Site-wide autoblocking. Saving it updates the plugin setting, with plugin 3.1.11 or later | Yes — Cookie Consent tab → Autoblocking card. Does nothing while the engine above is off |
| Banner text editing (heading, body, button labels, level names) | Yes | No on a connected site. An unconnected Banner Only site edits its message and button text in Cookie Consent → Banner Design |
| Banner design (position, colors, display type) | Yes | Banner style only (Standard / Compact, New engine) on a connected site. An unconnected Banner Only site sets position (top / bottom), animation and colors in Cookie Consent → Banner Design |
| Consent mode toggles (GCM, MCM, Facebook, GPC, DNT) | Yes | Yes |
| Consent behavior (Update consent, scroll/click) | Yes | Yes (unconnected sites only — connected sites see read-only cards on the Cookie Consent tab) |
| UI Blocking / Cookie Wall | Yes | No (portal-only; WP shows read-only card) |
| Accept on close | Yes | No (portal-only; WP shows read-only card) |
| Refuse button | No | Yes (unconnected sites only; connected sites see a read-only card) |
| Geolocation configuration | Yes (full per-law rules) | No (set on Configuration → Laws) |
| Autoblocking provider management (add/edit/delete) | Yes | No (read-only view) |
| Privacy Paper | Yes (Pro) | No |
| Privacy Contact | Yes (Pro) | No |
| Metrics label customization | Yes | No |
| Privacy Teller (video explainer) | No — not a Configuration page; its text is not editable | No |
| Consent log viewing | Yes | Yes (Consent Logs tab) |
| Consent log CSV export | Yes (Free: the last 7 days of Cookie Consent logs; Pro: any date range, plus Privacy Consent) | Yes (Pro) |
| Privacy consent log viewing | Yes | Yes — Consent Logs tab → Form Consent (forms are chosen on the Privacy Consent tab) |
| Dashboard analytics | Yes | No |
| Language/translation management | Yes | Languages can be picked in the first-run setup; translated text is edited only in the portal |
| Billing/subscription management | Yes | No (upgrade prompts only) |
| Account management (2FA, API tokens) | Yes | No |
| Caching compatibility toggle | No | Yes |
| Conditional display (show/hide on specific pages) | No | Yes |
| Bot detection toggle | No | Yes |
| Custom scripts (head/body) | No | Yes |
| Pull latest settings (sync portal changes to WP) | No | Yes |
How Settings Sync Between Portal and WP Admin
Changes you make in the Admin Portal are published to our configuration service. The WordPress plugin normally fetches it within seconds of Publish Now, otherwise every 12 hours, or when you click Pull latest settings on the Domain Info card (visible on Overview, Cookie Consent, and Consent Logs).
Changes you make in the WordPress admin Cookie Consent tab are saved locally to your WordPress database. On a connected site, saving changes only one thing on your live banner: the privacy policy link, taken from your WordPress privacy page. Colors, position, opacity and consent behavior come only from the Admin Portal.
Important: Portal changes are not reflected in WordPress until the next configuration pull. If you just changed settings in the portal and need them immediately, use the Pull latest settings button or the Purge Cache button in the WP admin.
Related Articles
- React Admin Overview — Detailed walkthrough of the WordPress admin tabs.
- Getting Started — Initial setup and connection flow.