Integration
Connect your WordPress site to PillarShield to enable content governance checks at the publish boundary. This guide covers installation from the WordPress Plugin Directory and initial configuration.
Prerequisites
- WordPress 6.0+ is required (tested up to 6.9).
- A PillarShield API key from pillarshield.co is required.
- An account with Administrator access to configure settings.
Installation
Working locally with DDEV?
If you run WordPress in DDEV, you can manage the plugin via WP‑CLI inside the container:
ddev exec wp plugin install pillarshield --activate
Configuration
After activation, navigate to Settings → PillarShield.
1. Connect API Key
Paste your tenant API key from pillarshield.co. You can also define
PILLARSHIELD_API_KEY in wp-config.php to override the stored value.
2. Choose Post Types
Select which post types (e.g., Posts, Pages) should be governed. Only enabled types are checked.
3. Define Gate Behavior
Set which statuses are gated (default: publish and private) and choose a fallback status (default: draft) for blocked publishes.
4. Roles & Permissions
Only users with specific capabilities can run manual checks or override violations. By default, these are granted to Administrators. Use a role editor plugin if you want Editors/Authors to see those options.