> 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.md).

# Administration & Branding

Scoped administration, governed white-labeling, accountable domains, and focused SEO.

Administration in ISLAMU Event is layered across Instance, Tenant, Organization, and Group scopes. Branding and vanity domains remain strictly subordinate to tenant data isolation, HAL action authority, and mandatory public disclosures.

***

## In this Section

* [**Administration Guide**](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md) — Comprehensive walkthrough of the web management consoles, tenant provisioning, and platform monetization.
* [**Admin Hierarchy & Roles**](/islamu-event/documentation/readme/administration-and-branding/admin-hierarchy.md) — Permissions, delegation boundaries, dangerous operations, concurrency controls, and recovery.
* [**White-Labeling**](/islamu-event/documentation/readme/administration-and-branding/white-labeling.md) — Presentation controls, CSS variables, governance locks, and legal operator identity boundaries.
* [**Custom Domains & SEO**](/islamu-event/documentation/readme/administration-and-branding/custom-domains-and-seo.md) — DNS/TLS configuration, reverse-proxy host routing, and public search engine discovery.

***

## Delegation Boundary

Before delegating an administrative area:

1. Verify permissions by testing one allowed and one denied action for the exact user role (see [Authorization](/islamu-event/documentation/readme/security-and-identity/authorization.md)).
2. Before publishing a custom domain, verify tenant isolation and mandatory legal notices, not merely visual appearance (see [Multi-Tenancy](/islamu-event/documentation/readme/security-and-identity/multi-tenancy.md)).

***

## Related Guides & Next Steps

* [**Administration Web Walkthrough**](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md) — Step-by-step console navigation guide.
* [**Authorization & Access Control**](/islamu-event/documentation/readme/security-and-identity/authorization.md) — Learn how MediatR handlers enforce role permissions.
* [**Multi-Tenancy Architecture**](/islamu-event/documentation/readme/security-and-identity/multi-tenancy.md) — Understand tenant boundaries and query filters.
* [**Configuration Manifests**](/islamu-event/documentation/readme/configuration-and-operations/configuration-manifests.md) — Export and import declarative tenant settings.


---

# 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.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.