Only your approved employees get in — verified, not trusted.
Upload an employee roster and only listed staff can register — verified on signup, login and the form.
When only your employees are allowed to apply.
Internal certifications and staff programmes that are closed by design — eligibility is the identity, not an honour-system checkbox.
Only listed employees register
Upload three fields per person — Employee ID, Email, Full Name. Nothing outside the roster gets in.Configurable
Employee ID auto-fills identity
Candidate enters only their Employee ID; a server lookup fills read-only name and email from the roster.
Email or Employee ID
Login and forgot-password accept either identifier; reset links always go to the email on file.
Form ID matches login identity
The Employee-ID on the form must match the login identity — provably the approved employee.
Append-only roster, with stats
Import by XLSX, CSV or paste — append-only, never overwrites prior rows. Live stats: total, signed-up, remaining.
Per-row remove, claim-aware
Remove a roster row before it's used; once claimed it locks, preserving the audit trail.
Employee-roster gating is configurable (employee_roster_enabled) per programme — not a default. Application capture, payments, the applicant console and per-institute isolation remain native.
Closed by design, verified at every layer.
A four-layer duplication defence backed by server-side verification — a roster stays a roster.
How the gate holds
- Server-verified lookup — the roster match happens on the server, not in the browser
- Four-layer duplication defence stops the same identity registering twice
- Read-only auto-fill of name and email from the roster on signup
- Reset links always route to the email on file, never a typed address
- Public roster lookup is rate-limited to resist enumeration
- Claimed rows are locked from removal, keeping the trail intact
What the gate changes on the portal
- The Mobile field is hidden — identity comes from the roster
- The public "Available Programmes" tab is hidden for a closed cohort
- The login identifier is relabelled to fit Employee ID or email
- Signup collects only what the roster already verifies
- Every action stays scoped to the institute that owns the roster
When employee_roster_enabled is on, the portal hides the Mobile field and public Available Programmes tab and relabels the login identifier — a closed cohort needs no public discovery.
A lighter touch, when you want it.
The engine does the heavy lifting alone. If you want it, WhatsApp and email agents nudge invited staff who haven't signed up and answer "how do I enrol?". See the Suite →
The AI Counseling Suite is an optional add-on. Roster gating works fully without it.
From roster to results, closed end to end.
Four steps. Only approved employees ever get in.
You post the assessment on the notice board so invited staff see the dates and what's required.
Your teamThe employee registers on your branded portal with their Employee ID — name and email auto-fill from the roster.
ApplicantThe employee launches the online exam through one-click Eklavvya SSO — no second login.
ApplicantYou filter results in the console and export them to Excel for the training or HR record.
Your teamQuestions HR and L&D teams ask.
How do we make sure only our own employees can register?
You upload an employee roster and nothing outside it gets in. The candidate enters only their Employee ID; a server-side lookup fills their name and email as read-only fields from the roster, so identity is verified rather than typed. The Employee ID on the form must match the login identity, making every registration provably an approved employee.
What do we need to upload, and how?
Three fields per person — Employee ID, Email and Full Name — imported by XLSX, CSV or paste. The import is append-only and never overwrites prior rows, and live stats show total, signed-up and remaining. You can remove a roster row before it is used; once claimed it locks, so the trail stays intact.
Can the same person register twice?
No. A four-layer duplication defence stops the same identity registering more than once, and the roster match happens on the server rather than in the browser. Public roster lookup is rate-limited to resist enumeration, and password reset links always route to the email on file rather than one a user types in.
How do employees take the assessment?
Registered employees launch the online exam through one-click Eklavvya SSO from the same portal — no second login and no credentials to distribute. Because entry is gated on the roster, the people who sit the assessment are exactly the people you approved.
How do we get the results out?
You filter results in the console and export them to Excel for the training or HR record. This is a closed assessment programme rather than an admission cycle, so there are no merit lists or public listings to manage — when roster gating is on, the portal even hides the public Available Programmes tab and the Mobile field.
Do we need the AI Counseling Suite for this?
No. The engine is native and complete on its own — roster gating, registration, the assessment and Excel reports all work without it. The AI Counseling Suite is an optional add-on enabled per institute; here it does little more than nudge invited staff who have not signed up and answer "how do I enrol?".
Close your admission programme to approved staff.
We'll stand up a roster-gated portal against a sample list — signup auto-fill, dual-identifier login and the four-layer defence, live.