Skip to content

Multi-Tenant Hierarchy

The Organization is Ilmiya’s tenant boundary: each customer institution runs in its own Organization with its own subdomain, login page, user base, and data, isolated from every other tenant.

Every Organization receives a default domain of the form org-slug.myilmiya.com, assigned by Ilmiya (for example, bahaji.myilmiya.com). The Router at myilmiya.com is the tenant-resolution entry point: a user types their school or organization name, the Router validates in real time that it exists (a green checkmark confirms a match), and on Next redirects to that organization’s login page at org-slug.myilmiya.com/login. After login, role determines the landing portal — students land in Campus, parents and guardians in Portal.

Inside the tenant, Ilmiya documents five organizational functions: Home (the dashboard, a real-time overview of activities, goals, and progress), People (roles, hierarchies, and responsibilities), Engage (internal and external communication channels), Analytics (performance measurement), and Admin (policies, security, and high-level control).

The tenant’s population covers Staff, Students, Guardians, and Families, managed through the People portal — Ilmiya’s Student Information System module. Staff hold one of three roles: Admin (full system control including staff management and settings), Staff (operational access), or Member (limited access for specialized or support roles).

Below the Organization, Spaces are the grouping unit: virtual classrooms or groups used to organize students, subjects, and teams. The Roster is the administrator dashboard for viewing and managing users across organizations or spaces, including last-login tracking. Labels are colour-coded tags applied to students, tasks, and spaces for categorization and filtering. Logs record every user action in the tenant for audit.

ObjectDefinition
OrganizationThe customer tenant; owns a default org-slug.myilmiya.com domain
Tenant IDUnique identifier for the organization; cannot be changed
Tenant RegionCountry of registration; used for compliance and localization
SpaceVirtual classroom or group under the organization
RosterDashboard of users across organizations or spaces, with last-login data
LabelColour-coded tag for students, tasks, and spaces
Staff roleAdmin (full control), Staff (operational), or Member (limited)
Log entryAudit record: user, resource, action, timestamp, and IP address

Organization-level settings live in Admin Panel → Settings. Org Info holds the Organization Name used for identification across the platform. Tenant Info holds the Tenant ID (read-only), the Tenant Domain (may be adjustable), and the Tenant Region.

Domains: the default domain is assigned automatically; one or multiple custom domains can be added and verified through DNS TXT records — see Integrations for the flow.

Staff: new members are invited by email from the Staff panel; profiles support role changes, detail updates, workspace reassignment, and removal.

Spaces: created with a name and icon; each space’s actions menu offers Edit, Add Student, Add Label, Archive, and Remove.

Logs: searchable and filterable by user, resource, action, and timestamp; downloadable as PDF for audits.

  • The Tenant ID cannot be changed.
  • The Router rejects Next without a validated organization; users who already know their direct URL can skip the Router entirely and bookmark org-slug.myilmiya.com.
  • Staff removal is permanent and Admin-only; transfer data and responsibilities first. Some configurations allow suspension instead of full deletion.
  • Space deletion is permanent and may impact linked tasks or workflows; only admins or space owners can delete. Archive disables a space without losing its data.
  • Custom-domain DNS propagation can take up to 48 hours, though it typically resolves within minutes to a few hours.
  • Logs capture every action — account creation, modification, logins — with timestamp, IP address, and live location details.