Organizations
3
Amanah DFW, demo masjid, and future DFW partners.
Active
1
Ready to operate with scoped users, roles, and modules.
Onboarding
2
Designed so partner masajid can join without mixing records.
Data rule
Scoped
Every record, permission, form, AI source, and alert is tenant-bound.
Organization Registry
A shared platform can serve multiple masajid while each organization keeps its own people, content, forms, and records.
| Organization | Status | Plan | Domain | City | Boundary | Owners |
|---|---|---|---|---|---|---|
Amanah DFW Amanah | America/Chicago | onboarding | enterprise | amanahdfw.org | Dallas-Fort Worth | dedicated_database | Amanah AdminCasework Lead |
Masjid Operations Demo Demo Masjid | America/Chicago | active | operations | demo.masjid.local | Allen | shared_app_isolated_data | Operations AdminImam Office |
Future DFW Partner Masjid Partner Masjid | America/Chicago | onboarding | starter | partner.example.org | DFW | shared_app_isolated_data | Masjid Admin |
Enabled Modules
Each masjid can turn on the modules it needs first.
Amanah DFW
Masjid Operations Demo
Future DFW Partner Masjid
Isolation Policies
The rules that keep each masjid safe on a shared platform.
Tenant-scoped records
Every record stores organizationId and cannot be queried outside the current tenant context.
Enforcement: Application middleware, database policies, API guards, and audit logs all check tenant context.
Tenant roles
A user can be Admin in one masjid and Viewer in another without permissions leaking.
Enforcement: Role assignments are keyed by organizationId, userId, role, module, and optional expiration.
Tenant knowledge base
Each masjid gets its own website content, policies, prayer times, forms, staff directory, and documents.
Enforcement: AI retrieval requires tenant id, content permission level, and source citation before answering.
Financial aid isolation
Amanah-style aid data must remain separate from normal masjid operations unless explicitly integrated.
Enforcement: Dedicated database option, restricted roles, anonymized reporting, and separate disbursement permissions.
Brand and domain settings
Each organization controls name, logo, colors, public URLs, email sender, phone, and payment links.
Enforcement: Theme and outbound communication settings resolve from the active organization.
Onboarding Checklist
Repeatable setup for every masjid that joins the platform.
Create organization profile
Capture legal name, public name, domains, timezone, contact info, and branding.
Owner: Platform Admin
Select modules
Enable communications, signage, forms, events, education, membership, finance, or aid modules.
Owner: Masjid Admin
Invite leadership
Assign Shura, Imam, staff, education, finance, volunteers, and viewer roles per organization.
Owner: Masjid Admin
Load knowledge sources
Connect website pages, PDFs, forms, policies, staff directory, donation links, and prayer schedules.
Owner: Content Admin
Configure approvals and notifications
Set approval routes, emergency rules, email sender, and screen announcement rules.
Owner: Operations Admin
Go-live checklist
Verify tenant isolation, permissions, AI retrieval scope, forms, email delivery, and audit logging.
Owner: Platform Admin