> 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/security-and-identity.md).

# Security & Identity

Identity, resource authorization, tenant isolation, and anti-resurrection privacy workflows.

Authentication, authorization, tenant isolation, and privacy erasure are separate authorities. Each fails closed; none silently substitutes for another during an outage or error condition.

***

## In this Section

* [**Authentication**](/islamu-event/documentation/readme/security-and-identity/authentication.md) — Keycloak OIDC, Blazor BFF cookie sessions, API tokens, and linked AT Protocol sign-in.
* [**Authorization & Access Control**](/islamu-event/documentation/readme/security-and-identity/authorization.md) — Local RBAC vs. Cerbos PDP, pipeline evaluation, and server-issued HAL action links.
* [**Multi-Tenancy**](/islamu-event/documentation/readme/security-and-identity/multi-tenancy.md) — Deployment modes (`SingleTenant` vs. `multi_tenant`), host resolution, and database query filters.
* [**Privacy Erasure & Anti-Resurrection**](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md) — GDPR Right-to-Erasure workflows, receipt tokens, and authority storage topologies.

***

## Operational Claim Boundary

These pages describe implemented platform behavior, not security, privacy, accessibility, compliance, or religious certification. Adopters remain responsible for threat modeling, provider agreements, legal assessment, incident response, retention, data residency, vulnerability management, and operational controls.

***

## Related Guides & Next Steps

* [**Docker Compose Runbook**](/islamu-event/documentation/readme/self-hosting/docker-compose.md) — Deploy Keycloak and the PostgreSQL database.
* [**Admin Hierarchy & Roles**](/islamu-event/documentation/readme/administration-and-branding/admin-hierarchy.md) — Learn how platform, tenant, and event organizer roles interact.
* [**Secrets Management**](/islamu-event/documentation/readme/configuration-and-operations/secrets.md) — Protect OIDC client secrets and database passwords.
* [**Troubleshooting Authentication & Cerbos**](/islamu-event/documentation/readme/configuration-and-operations/troubleshooting-and-health.md) — Step-by-step recipes for login redirect loops and 403 Forbidden errors.


---

# 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/security-and-identity.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.
