PillarShield
PillarShield integrates WordPress with the PillarShield SaaS governance API. It runs checks at the publish boundary, blocks non‑compliant content, allows optional overrides, and keeps a governance record per post for reporting. You must obtain a PillarShield API key from https://pillarshield.co for
PillarShield integrates WordPress with the PillarShield SaaS governance API. It runs checks at the publish boundary, blocks non‑compliant content, allows optional overrides, and keeps a governance record per post for reporting. You must obtain a PillarShield API key from https://pillarshield.co for the plugin to function.
Key features:
- Gate governance checks on publish/private statuses (configurable per post type).
- Optional manual checks that never block saves.
- Override workflow for privileged users.
- Governance reporting under Tools → PillarShield (blocked-at-gate items only).
- Safe storage of outcomes without raw content.
Configuration
Settings → PillarShield:
- API Endpoint : The PillarShield governance endpoint.
- API Key : Your tenant API key ( psk_... ). Get a key at https://pillarshield.co. The plugin does not perform governance checks without a valid API key.
- You can also define PILLARSHIELD_API_KEY in wp-config.php to override the stored option: define(‘PILLARSHIELD_API_KEY’, ‘psk_…’);
Enable Governance : Turn checks on/off. Allow Save Without API : Allow publishing if the API is unavailable. Enabled Post Types : Which post types are governed. Fields per Post Type : Comma‑separated fields to scan. Supports meta:KEY . Gate Configuration :
- Gated statuses (default: publish + private)
- Fallback status (default: draft)
Use the Test Connection button to validate API access.
Editor UX
On governed post types, a PillarShield meta box appears with:
- Check PillarShield governance on this save (manual check)
- Override PillarShield governance (save anyway)
These checkboxes do not persist — they only apply to the current save.
