Manage Shared Config Constants
Shared config constants are global values managed in Strapi that are available in every questionnaire. They are used for regulatory thresholds, company branding, and other values that appear across multiple insurance products.
Prerequisites
Section titled “Prerequisites”- Access to Strapi CMS (shared-config content type)
- Familiarity with interpolations (see Configure Interpolations)
Current shared constants
Section titled “Current shared constants”The following constants are currently defined:
| Constant | Current Value | Description |
|---|---|---|
featherName |
Feather Insurance |
Company display name |
privateHealthInsuranceThreshold |
77400 |
Annual income threshold for private health eligibility |
miniJobThreshold |
7236 |
Annual mini-job income threshold |
1. Reference shared constants in question text
Section titled “1. Reference shared constants in question text”Use the constant name directly in double curly braces — no prefix needed:
You are eligible for private health insurance if your annualgross income exceeds {{privateHealthInsuranceThreshold}} EUR.This differs from questionnaire-specific constants, which require the {{constants.myConstant}} prefix.
2. How shared config is injected
Section titled “2. How shared config is injected”During sync, each questionnaire file merges shared config with questionnaire-specific constants:
constants: { ...sharedConfig, ...constants },Shared config is loaded first, then questionnaire-specific constants override any matching keys. This means a questionnaire can override a shared value if needed.
3. Update a shared constant
Section titled “3. Update a shared constant”- Open Strapi and navigate to Content Manager > Shared config.
- Edit the value you want to change.
- Publish the change.
- Notify engineering in the #birdhouse Slack channel so they can run a content sync.
4. When to update shared constants
Section titled “4. When to update shared constants”- Annually: Regulatory thresholds (e.g.,
privateHealthInsuranceThreshold,miniJobThreshold) change with each calendar year - Rebranding: Company name changes
- Regulatory changes: New thresholds or limits introduced by law
5. Shared config vs questionnaire-specific constants
Section titled “5. Shared config vs questionnaire-specific constants”| Feature | Shared config | Questionnaire constants |
|---|---|---|
| Scope | All questionnaires | Single questionnaire |
| Strapi location | Shared config content type | Questionnaire metadata > constants |
| Interpolation syntax | {{constantName}} |
{{constants.constantName}} |
| Override behavior | Can be overridden per questionnaire | Takes precedence over shared config |
See also
Section titled “See also”- Configure Interpolations — using dynamic values in question text
- Questionnaire Metadata — reference for questionnaire-specific constants
- Strapi Content Types — schema reference for the shared-config content type
- Strapi Transform Pipeline — how sync processes shared config and questionnaire data