Skip to content
NEWA smarter way to manage modern institutions.
Edusmart Systems

Security

Control access through institutional boundaries.

Users, roles, granular permissions and audit trails with tenant isolation by design — so information appears only where it should.

Connected to Human Resources

Administration

Users • Roles • Audit

Pending

12

In progress

7

Completed

34

ItemOwnerStatus
Application — J. AchiengRegistrarReview
Invoice INV-2044FinanceIssued
LPO-0892ProcurementPending

Challenge

What institutions experience without connected systems.

Access is granted broadly because permissions lack granularity — information crosses department and campus boundaries unintentionally.

Edusmart addresses this by bringing security & administration into the same institutional record — with workflows, audit trails and period-aware context instead of disconnected files.

Capabilities

Everything needed for security & administration — in context.

Tenant isolation

Institutional data boundaries enforced by design.

Role & permission controls

Granular access by function, not just role name.

Authentication

Secure, policy-driven access for every user.

Audit trails

Administrative actions retain actor and time.

User lifecycle

Provisioning and de-provisioning tied to HR status.

API security

Server-side boundaries; no direct MIS exposure to browsers.

Workflow

Data and process flow.

From intake to completion, information moves through responsible officers with status preserved at every step.

  • Request → review → approval → execution → audit
  • Every action retains actor and timestamp
Request
Department Review
Approval
Execution
Audit Trail

Connected

Works as part of the platform.

Security & Administration shares the same institutional record with its neighbors. No re-keying, no reconciliation between modules.

Who uses it

Designed around responsible roles.

ICT & System Administration
Management
HR

Reporting

Relevant reports derive from the system of record — filterable by programme, campus and period.

  • User & access overview
  • Permission audits
  • Activity trails

User

1,240

Permission

86%

Activity

42

Security & permissions

Access scopes to campus, department and function. Tenant isolation ensures information stays within institutional boundaries.

  • Granular role and permission controls
  • Audit trails on every action

Permission example

Finance — view balancesAllowed
HR — edit payrollDenied
Procurement — approve LPOThreshold

FAQ

Common questions

Can permissions vary by campus?

Yes — permissions can scope by campus, department and programme.

See Security & Administration in your context.

Book a demo and explore how it maps to your processes.