> For the complete documentation index, see [llms.txt](https://islamu.gitbook.io/islamu-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://islamu.gitbook.io/islamu-event/documentation/readme/configuration-and-operations/configuration-manifests.md).

# Configuration Manifests

Bootstrap and export governed configuration without secrets, PII, or application data.

Configuration manifests move governed tenant settings and typed configuration documents across environments. They are specifically **not** database dumps, secret bundles, subject-data exports, or infrastructure snapshots.

***

## What Belongs in a Manifest

Only allowlisted instance/tenant settings and approved typed documents belong in the manifest contract. Typical uses include reproducible policy, [white-labeling presentation tokens](/islamu-event/documentation/readme/administration-and-branding/white-labeling.md), email templates, and feature flags that the application explicitly recognizes through the [Administration Console](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md).

***

## What is Strictly Excluded

Manifests deliberately exclude:

* Users, credentials, and identity claims (see [Authentication](/islamu-event/documentation/readme/security-and-identity/authentication.md)).
* [Registrations, admissions, orders, and payments](/islamu-event/documentation/readme/events-and-ticketing/paid-events-and-payouts.md).
* Attendee and data subject PII.
* Operational queues and transactional outbox state.
* Provider runtime bindings, endpoints, and connection strings.
* Database or [Privacy-Erasure Authority topology](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md).
* Passwords, tokens, and secret values (see [Secrets Management](/islamu-event/documentation/readme/configuration-and-operations/secrets.md)).

> \[!NOTE] Whole-instance export preserves governed configuration only. It does not replace full database backups (see [Backup, Restore & Upgrade](/islamu-event/documentation/readme/configuration-and-operations/backup-restore-upgrade.md)) or privacy-erasure compliance obligations.

***

## Safe Ingestion & Trust Boundary

Manifest file ingestion represents an administrative trust boundary:

1. Restrict file access, ownership, and write permissions to the application service user.
2. Validate schema version, authority signatures, and every included section before committing.
3. Apply outcomes are strictly atomic: if a single section fails validation, the entire manifest is rejected rather than leaving the system in a partially trusted state.

***

## Standard Operating Procedure

1. Export or author an allowlisted manifest without secrets.
2. Review the diff and intended tenant scope.
3. Back up the affected database stores (see [Backup, Restore & Upgrade](/islamu-event/documentation/readme/configuration-and-operations/backup-restore-upgrade.md)).
4. Apply in an isolated staging environment first.
5. Verify updated settings, HAL affordances, public branding, and provider behavior.
6. Promote the reviewed artifact and record its SHA-256 checksum in operational logs.

***

## Related Guides & Next Steps

* [**White-Labeling & Branding**](/islamu-event/documentation/readme/administration-and-branding/white-labeling.md) — Customize colors, logos, and typography via manifests.
* [**First-Run Administration Guide**](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md) — Manage instance and tenant configuration through the web UI.
* [**Secrets Management**](/islamu-event/documentation/readme/configuration-and-operations/secrets.md) — Separate credentials from declarative configuration manifests.
* [**Backup, Restore & Upgrade**](/islamu-event/documentation/readme/configuration-and-operations/backup-restore-upgrade.md) — Create complete database snapshots before importing manifests.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://islamu.gitbook.io/islamu-event/documentation/readme/configuration-and-operations/configuration-manifests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.