1. Model the institution
Create a workspace for the organization, then branch into locations, teams, committees, roles, and operating areas.
Platform architecture
One workspace. Every operation. One trust model.
Nizam is not a bundle of disconnected apps. It is a workspace architecture where suites share identity, access, people, time, content, intake, workflow state, audit, and automation.
WorkspaceInstitution boundary
TeamspaceCommittee or department
SuiteComplete product module
2. Connect the primitives
People, calendars, files, forms, permissions, states, and audit become shared infrastructure instead of duplicated work.
3. Enable complete suites
Turn on modules for events, bookings, docs, database, volunteers, announcements, masjid operations, and more.
4. Automate follow-through
Published events, approved bookings, new submissions, and volunteer shifts can trigger reminders and next actions.
Operating model
Built around the real institutional graph.
Workspaces
Each institution gets one boundary for data, members, roles, settings, public presence, and enabled suites.
Teamspaces
Committees and departments get scoped work areas for docs, tasks, calendars, files, and decisions.
Packs
Masjid, Islamic org, business, and scholar packs add specialized workflows on top of the same OS primitives.
Why this matters
When roles, people, events, documents, bookings, and forms share a model, the platform can answer the operational questions scattered tools cannot: who owns it, who approved it, what changed, what is next, and who needs to know?