BL TECHNO Global School Management Platform • Local-currency pricing Explore the platform
← Feature LibraryADMINISTRATION FEATURE
US
BL TECHNO FEATUREUser Management

Control who can open each School App module, what they can do and where they can do it.

Manage users, role baselines, module access, action permissions, centre scope, account-security settings and access-control audit history from one governed administration area.

See It in a Demo →Explore Capabilities
Built for Super Admin • School Admin • Authorised Security Managers
User DirectoryRolesPermission MatrixCentre ScopeMFA / SessionAudit Trail
User & Access Management
BL TECHNO User & Access Management illustrative product mockupILLUSTRATIVE • DEMO DATA
PART OFBL TECHNO SchoolExplore product →
FeatureUser Management
Operating areaAdministration
Product familyBL TECHNO School
Access modelRole + scope aware
ExperienceResponsive
WHY THIS FEATURE MATTERS

Give authorised school teams a clearer operating view without exposing every control to every user.

Manage users, role baselines, module access, action permissions, centre scope, account-security settings and access-control audit history from one governed administration area.

See BL TECHNO School →
01School identity
02Centre scope
03Permission model
04Audit-aware administration
HOW USER MANAGEMENT WORKS

Follow the workflow from first action to review.

Tap a step to change the visual. Each stage comes directly from the feature workflow defined for BL TECHNO.

BL TECHNO User & Access Management illustrative mockupSTEP 01
ADMINISTRATION WORKFLOW

Create

School App user

User & Access Management
BL TECHNO Centre Management illustrative mockupSTEP 02
ADMINISTRATION WORKFLOW

Assign

Role baseline

Centre Management
BL TECHNO School Command Centre illustrative mockupSTEP 03
ADMINISTRATION WORKFLOW

Scope

School / centres

School Command Centre
BL TECHNO School Command Dashboard illustrative mockupSTEP 04
ADMINISTRATION WORKFLOW

Permit

Module & action rights

School Command Dashboard
BL TECHNO Live Chat illustrative mockupSTEP 05
ADMINISTRATION WORKFLOW

Secure & Audit

Session policy and history

Live Chat
OPERATIONAL OUTCOMES

What User Management is designed to improve.

These outcomes describe the operating purpose of the feature without inventing customer statistics.

01

Least necessary access

Give people the capabilities needed for their work without granting the whole platform.

02

Consistent access model

Combine role baselines with module/action permissions and centre scope.

03

Reviewable security changes

Keep user, role, permission and session-security changes inside an audit trail.

CAPABILITY MAP

Go inside User Management.

Six capability areas show what the feature organises and how the workflow becomes operational.

UD

User Directory

Search and manage authorised School App users.

User listStatusRoleCentre scope
RP

Role Presets

Start from approved responsibility-based access baselines.

Role baselineSuperAdmin handlingRole assignmentPreset rights
PM

Permission Matrix

Control actions at module level.

OpenCreateEditDeleteApproveExport
CS

Centre Scope

Limit users to the school locations they are authorised to manage.

Assigned centresAll-centres controlPrimary centreScope review
SP

Security Policies

Manage selected account/session protections.

Password resetMFA requirementConcurrent sessionsIdle timeout
AT

Audit Trail

Review user, role, permission and session-security changes.

ActorTargetEvent typeBefore/after detail
OPERATIONAL SIGNALS

Bring the information that matters closer to action.

The exact records shown depend on the signed-in user, school configuration and current school data. These labels show the kinds of context this feature organises.

UsersDirectory
RolesResponsibility
PermissionsAction rights
CentresOperational scope
SecurityAccount posture
AuditChange history
BL TECHNO User & Access Management mockupUser & Access Management
WHO USES IT

One feature. Different responsibilities.

Switch roles to see how the same feature serves different authorised users without giving everyone the same view.

CONNECTED WORK

User Management does not have to become another isolated tool.

Move into the neighbouring workflows that share relevant school context.

USUser ManagementCurrent feature
SESecurity & TrustPlatform security modelCECentre ManagementLocation scopeSCSchool CommandManagement accessSTStaff ManagementWorkforce identity
CONNECTED PLATFORM STORY

See User Management as part of the wider BL TECHNO environment.

This public-safe motion teaser uses illustrative marketing visuals and demo interface language. It is designed to communicate the connected platform story without exposing production school data.

Open Product Tour →Book a Demo
IMPLEMENTATION PATH

Introduce User Management as an operating process, not just another screen.

The exact implementation depends on school size, plan and scope. This path shows the practical sequence for introducing the feature responsibly.

01

Discover

Identify where User Management fits into the school’s current operating process and what should improve.

02

Configure

Confirm school, centre, role and permission boundaries before operational use.

03

Prepare

Check the records, settings and authorised users needed for User Management to work cleanly from day one.

04

Train

Walk the responsible teams through the User Management workflow using their real roles and school scope.

05

Launch

Introduce User Management into the agreed school process with controlled access and clear ownership.

06

Review

Review usage, exceptions and operating quality, then refine the school process where needed.

SECURITY & GOVERNANCE

Access follows responsibility.

User Management inherits BL TECHNO’s role, scope and permission principles. Public marketing shows the controls; authenticated product access remains authoritative.

✓Server-side access authority
✓Open/Create/Edit/Delete/Approve/Export rights
✓Privileged-account MFA/session controls
✓Access-control audit history
Explore Security →
IDENTITYWho is signed in?
↓
ROLEWhat is their responsibility?
↓
SCOPEWhich school / centre / class?
↓
FEATUREUser Management
RESPONSIVE EXPERIENCE

Fit the feature to where the role works.

Responsive management viewsTablet-friendly operational controlPhone-ready review surfacesTouch-friendly navigation
Explore Mobile Experience →
GLOBAL CONTEXT

Keep local school context configurable.

Country and centre contextSchool timezoneLocale/language settingsLTR/RTL-ready architecture
Explore Global Platform →
RELATED SOLUTIONS

See where User Management fits by school need and responsibility.

SOLUTIONSchool OwnersExplore →SOLUTIONPrincipalsExplore →SOLUTIONAdministratorsExplore →SOLUTIONMulti-CampusExplore →
RELATED FEATURES

Continue through the connected workflow.

CM
Centre Management

Location scope

→SC
School Command

Management access

→ST
Staff Management

Workforce identity

→
FEATURE FAQ

Questions about User Management.

The current School App permission matrix includes Open, Create, Edit, Delete, Approve and Export.

No. The current access-control architecture explicitly treats browser visibility as convenience and server-side guards as the authority for mapped routes and APIs.

Yes. The user-management model includes centre scope alongside roles, permissions and personal overrides.

SEE USER MANAGEMENT IN CONTEXT

Bring this workflow into your tailored BL TECHNO demo.

Inspect the feature in detail, then see how it connects to the product family and wider school operation.

Book a DemoExplore BL TECHNO School