Mosque lifecycle states
A mosque moves through five states over its life with Kadim. Only a platform operator changes them, and only ever to a state that is valid from the current one. Every change is recorded. The operator's how-to is Manage a mosque's lifecycle.
The states
| State | What it means |
|---|---|
| Trial | A newly created mosque on a free trial |
| Active | A live, paying mosque |
| Past due | A grace state after a missed payment. Nothing is locked yet |
| Suspended | Dunning exhausted. The coordinator and team screens are locked |
| Archived | The mosque has left. This is final and cannot be reopened |
Valid changes from each state
| From | Changes offered |
|---|---|
| Trial | Activate, Archive |
| Active | Mark past due, Archive |
| Past due | Reactivate, Suspend, Archive |
| Suspended | Reactivate, Archive |
| Archived | None. This is final |
The page only ever offers the changes valid from the current state, so an invalid move cannot be made. From a suspended or past-due mosque the restore button reads Reactivate, because it restores access rather than converting a trial.
Who keeps access
- Suspended is a commercial state, never a child-safety one. The coordinator's rota and team screens lock straight away, but a trustee can always read the safeguarding records. Suspension never blocks safeguarding access.
- Archived ends access for everyone. The safeguarding audit is retained under the retention policy.
Not built yet
Exporting a mosque's data on the way out, and the erasure or retention of records after archiving, are not built. They need a founder and data-protection sign-off first, so the page offers no export button.