> 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/administration-and-branding/white-labeling.md).

# White-Labeling

Customize presentation while preserving legal and operator accountability disclosures.

White-labeling customizes the visual identity and presentation of tenant storefronts and community hubs. It does not alter platform, payment, tax, provider, or legal liability boundaries.

***

## Customizable Presentation Layers

Depending on delegated administrative scope (see [Admin Hierarchy](/islamu-event/documentation/readme/administration-and-branding/admin-hierarchy.md)), operators can customize:

* **Theme Tokens**: Brand primary and secondary colors, typography, and dark/light mode defaults.
* **Header & Navigation**: Logos, favicons, custom menus, and external links.
* **Footer Layouts**: Social links, copyright notices, and supplementary link groups.
* **Email Templates**: Branded headers and footers for [SMTP Outbox Delivery](/islamu-event/documentation/readme/communications-and-notifications/email-smtp.md).

> \[!IMPORTANT] **Governance Locks Retain Legal Disclosures!**\
> Instance administrators can enforce **Governance Locks** on footer components. This prevents individual tenants from hiding or deleting legally required terms of service, privacy notices, or operator identity disclosures.

***

## Visual Branding vs. Legal Accountability Identity

Visual branding is not legal identity:

* Public pages preserve **Operator Legal Identity** as a mandatory, non-overrideable disclosure resource (configured via `INSTANCE__OPERATORIDENTITY__*` in [Environment Variables](/islamu-event/documentation/readme/configuration-and-operations/environment-variables.md#9-operator-legal-identity-production-gate)).
* If required public disclosure identity is unavailable, the footer fails closed with `503 tenant_identity_unavailable`. A brand logo or display name will never be substituted as a legal fallback.

***

## Standard Operational Workflow

1. Establish tenant ownership and bind approved domains (see [Custom Domains & SEO](/islamu-event/documentation/readme/administration-and-branding/custom-domains-and-seo.md)).
2. Configure required accountability identities in `.env` before customizing visual branding.
3. Apply theme, navigation, and footer settings through the [Tenant Admin Console](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md) or import via [Configuration Manifests](/islamu-event/documentation/readme/configuration-and-operations/configuration-manifests.md).
4. Verify that governance-locked disclosures remain visible and immutable.
5. Test public pages across desktop, tablet, and mobile viewport breakpoints.

***

## Related Guides & Next Steps

* [**Administration Web Walkthrough**](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md) — Step-by-step branding customization in the UI.
* [**Custom Domains & SEO**](/islamu-event/documentation/readme/administration-and-branding/custom-domains-and-seo.md) — Bind custom vanity domains to individual tenants.
* [**Configuration Manifests**](/islamu-event/documentation/readme/configuration-and-operations/configuration-manifests.md) — Export and deploy declarative branding bundles.
* [**Operator Legal Identity Reference**](/islamu-event/documentation/readme/configuration-and-operations/environment-variables.md#9-operator-legal-identity-production-gate) — Required production disclosures.


---

# 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/administration-and-branding/white-labeling.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.