Control Center
What needs attention, what is happening this week, and what changed recently.
Institution operating system
Nizam replaces spreadsheets, WhatsApp threads, scattered forms, ad hoc calendars, and half-connected websites with one system of record for people, content, schedules, intake, workflows, and accountability.
From chaos to clarity
Nizam is built around shared primitives so every suite speaks the same language: people, time, content, intake, state, access, audit, and automation.
Clickable operating flows
Access controls who can publish, approve, export, manage members, and operate suites.
02Forms become submissions, inbox threads, assignments, service workflows, and records.
03Registration, check-in, volunteers, announcements, calendar, and audit stay connected.
04Applications, shifts, attendance, teams, directory records, and service history share one graph.
05Important work carries state, ownership, permissions, confirmation, and audit visibility.
Inside Nizam
Control Center, Masjid Events, Access, and Database are shown as practical app surfaces: sidebar, topbar, action states, lists, cards, and operational records.
What needs attention, what is happening this week, and what changed recently.
Registration, reminder queue, QR pass readiness, volunteer shifts, and attendance in one place.
Control who can publish, approve, export, administer, and operate each suite.
Spreadsheet familiarity with permissions, publishing states, saved views, and linked workflows.
Who Nizam serves
Daily prayer operations, iqama publishing, Jumu'ah, events, announcements, bookings, media, volunteer teams, services, and public presence.
Da'wah, charity, education, youth, media, research, social services, interfaith, and community development teams.
Internal operations, customers, pipeline, marketing, staffing, tasks, support, and knowledge.
Teaching programs, Q&A workflows, publication pipelines, student mentorship, notes, and releases.
Branches, teams, location calendars, people records, and controlled access without duplicating your system.
System primitives
One user identity, invitations, workspace membership, roles, delegated access, and permissions that match the UI.
The institution is the workspace. Committees, departments, branches, and teams get scoped areas without a super-admin mess.
A canonical directory for members, volunteers, staff, partners, clients, students, and relationships.
Events, programs, bookings, shifts, meetings, maintenance, and calendars share one scheduling model.
Pages, docs, files, forms, submissions, and operational inboxes connect knowledge to real work.
Draft, review, publish, approve, archive, automate, and audit with the same grammar across every suite.
Complete product modules
Publish prayer updates, plan programs, approve facility requests, staff volunteer shifts, and keep the public portal aligned from one workspace.
Route community intake, assign follow-up, maintain people records, coordinate departments, and publish updates without losing ownership.
Keep SOPs, policies, templates, assets, workbooks, and structured records tied to the work they support.