Support & Troubleshooting

If a governance check is blocking critical content, you can bypass it in two ways:

1. Fail Safe Mode (Admin): In your Drupal configuration, set the "Fail Safe" behavior to "Allow". This will permit all content even if checks fail.
2. Permission Override: Users with the bypass pillarshield checks permission can ignore blocking errors and publish anyway. Grant this permission to your Editors role temporarily.

Ensure you have copied the Tenant API Key from your dashboard settings. If you are using the Key module, clear your Drupal cache after updating the key value. On your Drupal configuration page, use the "Test Connection" button to verify that your site can reach the PillarShield API. If the test fails, check your firewall or network settings.

Governance models are conservative by design. To allow a specific term:

• Protect Plan: Add the term to your Safe List in Policy Settings.
• Core Plan: Core uses a fixed baseline policy. Contact support if you believe a standard term is being flagged incorrectly.

No. Checks only run during the Save/Publish action for authorized users. They do not run for anonymous visitors or on front-end pages. Deterministic checks typically take under 200ms. LLM-based checks (if enabled) may take longer (~2s) but never affect site readers.

Your site will continue to function. The module is designed to "fail open" or "fail closed" based on your local configuration. By default, if the API is unreachable, the module will Allow the content save to proceed so your workflow is not discouraged.