Every security agency has lived through some version of this: a new guard is hired, a paper form is filled out, someone types their details into a register or spreadsheet later that day (if they remember), and getting the guard an actual working login to the attendance app takes a separate follow-up step, sometimes days later. Multiply this by the guard turnover a typical agency deals with, and onboarding friction becomes a real operational cost โ not because any single step is hard, but because there are too many manual steps that all have to happen correctly, in order, for a guard to be ready to work on day one.
One form, one save โ code and login created automatically
When HR or an admin adds a new employee in Raksha Kavach, the system automatically generates a sequential employee code for that guard within the company โ no manual numbering, no risk of a duplicate code. Unless the guard is being linked to an existing account (for example, someone hired through the recruitment portal who already has a candidate profile), the platform also automatically creates their login in the same step, with a random one-time password. There is no separate "now go create their user account" task for HR to remember.
Credentials shown once, and emailed if possible
The generated password is shown to the person completing onboarding exactly once, right after the guard is created โ enough to write it down or hand it to the guard directly โ and is best-effort emailed to the guard as well if they have an email address on file. It is never stored in plain text and can't be retrieved again after that point, which keeps the process both fast and reasonably secure by default.
Login without needing an email address
A meaningful number of guards genuinely don't have (or don't regularly check) a personal email address. Raksha Kavach's login accepts an employee code, a phone number, or an email โ whichever the guard actually has and remembers โ so the absence of an email address is never a blocker to getting a guard logged into the mobile app on their first day.
Documents attached now, or added later
Onboarding paperwork rarely arrives all at once โ a guard might have their Aadhaar ready on day one but their police verification only clears a week later. The same document upload (Aadhaar, PAN, driving licence, police verification, photo, bank passbook, education certificates) works whether it's done during the initial registration or added to the guard's profile any time afterward, so onboarding doesn't have to be blocked waiting for every document to be in hand.
From candidate to employee, without re-typing anything
For agencies using the AI Job Recruitment Portal, a candidate who's been through interview scheduling and received an offer can be hired directly to a site in one step โ creating their employee record, linking it back to their original candidate profile, and creating an active deployment, all without re-entering information that was already captured during their application.
The goal of digital onboarding isn't paperwork for its own sake โ it's making sure a guard can actually punch in, correctly assigned to the right site, on day one, without a manual scramble behind the scenes.
Conclusion
Onboarding is the first impression a new guard has of how professionally an agency runs โ and it's also the point where the most manual, error-prone admin work traditionally piles up. Automating the mechanical parts (codes, logins, credential delivery) while keeping document collection flexible lets an agency onboard a guard in minutes rather than days, and start them off correctly recorded from their very first shift.