Modular by design
Admissions, student lifecycle, curriculum, registration, assessment, finance, eCampus, services and credentials each own their authoritative rules and records.
Architecture and trust
Connected enough to operate as one institution. Separated enough to remain trusted.
ITEMS combines a modular product core, institution-aware security and governed data exchange to support complex tertiary operations without compromising ownership or accountability.
The architecture decision
One maintained product core with explicit domain boundaries.
The initial architecture favours a modular core rather than premature complexity. Capabilities can scale independently when evidence shows a genuine operational need.
Tenant-aware everywhere
Institution context is enforced through identity, data queries, files, caches, events, search, jobs, reports and exports.
Event-capable integration
Important changes create durable events that connect workflows, notifications, analytics and approved external services.
Domain ownership
Every important record has one accountable source.
Modules may share authorised information, but only the owning domain can change its authoritative records.
Institution
Campuses, units, calendars, policies, terminology, entitlements and configuration.
Admissions
Applications, evidence, screening, decisions, offers and clearance.
Student
Programme enrolment, status, adviser and lifecycle events.
Curriculum
Programmes, curriculum versions, courses, credits and requirements.
Registration
Offerings, eligibility, selections, class groups and authorised overrides.
Assessment
Marks, moderation, result approval, GPA, standing and progression.
Finance
Fees, invoices, verified payments, ledgers, refunds and reconciliation.
eCampus
Course design, learning spaces, activities, submissions, discussions and progress.
Services
Requests, cases, appointments, allocations, referrals and clearance.
Credentials
Awards, transcripts, digital credentials, status and verification.
Quality
Approvals, evidence, programme reviews and improvement actions.
Engagement
Notifications, preferences, enquiries, alumni and external relationships.
Institutional isolation
An institution is a security and data boundary—not just a label.
ITEMS resolves and validates the institution before authorised work begins, then carries that context through every layer.
✓
Identity and permissions
Access combines institution membership, role, unit, assignment, record relationship and workflow state.
✓
Records and files
Institution scope applies to database records, uploaded evidence, course media and generated documents.
✓
Background processes
Jobs, events, integrations, search and exports retain and validate their institution context.
✓
Privileged support
Exceptional support access is time-limited, purpose-bound, approved, recorded and reviewed.
ITEMS eCampus boundary
Digital learning connected directly to the institutional record.
eCampus owns detailed learning activity. Registration remains authoritative for enrolment; academic governance remains authoritative for approved results.
Registerconfirmed course registration grants learning eligibility
Learncourse spaces manage content, activity and engagement
Assessapproved outcomes enter the academic result workflow
Credentialawards follow institutional approval and verification
Protected decisions
Security and accountability across the full lifecycle.
Access by purpose
Deny by default, least privilege, multifactor protection for sensitive roles and periodic access review.
Historical integrity
Effective-dated rules, versioned records and controlled corrections preserve what was true at the time.
Encrypted information
Protected transport, encrypted storage, managed secrets and edition-specific key arrangements.
Logged material actions
Authentication, approvals, changes, exports, integrations and privileged access create audit evidence.
Recoverable operation
Backups, restoration tests, incident response and defined responsibilities support continuity.
Portable institutional data
Authorised exports preserve identifiers, relationships, timestamps and interpretation metadata.
Governed integrations
Connect existing systems without surrendering control.
| Integration | How ITEMS governs it |
|---|---|
| Payments and banks | Server-side verification, idempotent ledger posting, reconciliation and controlled refunds. |
| Identity providers | Standards-based sign-in, scoped claims, strong authentication and account lifecycle controls. |
| Virtual classrooms and learning tools | Minimum necessary learner context, signed launches and controlled outcome transfer. |
| Finance, library and institutional systems | Versioned APIs, named ownership, exception queues and authoritative-record decisions. |
| Regulatory and accreditation services | Approved schemas, validation, evidence and traceable submissions. |
| Credential verification | Minimum disclosure, consent or institutional authority and complete status history. |
Deployment consistency
The architecture travels across every ITEMS edition.
Cloud, Dedicated and Sovereign change the infrastructure and operating boundary—not the identity or integrity of the product.
What remains consistent
- Domain rules and authoritative records
- Institution-aware identity and access
- Audit, security and data portability
- Supported APIs and configuration
- Controlled releases and source ownership
What can vary
- Shared, dedicated or customer-approved infrastructure
- Data region and encryption-key arrangements
- Release coordination and support boundaries
- Connectivity and local operational responsibilities
- Recovery objectives and service tier
Review ITEMS against your institutional architecture.
Discuss identity, integration, data, security, deployment and eCampus requirements.