Rupid · Employer Portal
Before an employer can upload anything, they need somewhere to log in. Rupid’s team creates the company’s account first with just the company name and one contact person. That person gets an invitation on their work email, with a temporary password, must be changed at the first login, verifies their phone, and lands on a checklist that walks them through the rest. There is no public sign-up — every employer account starts with Rupid.
A secure login exists before a single document changes hands, strangers cannot open accounts, and the employer’s first screen tells them exactly what to do next instead of leaving them staring at an empty portal.
Rupid’s operations team (creates and invites) · The employer’s first admin (activates) · Later admins (through handover)
Create Company Account (Rupid’s side)
Where Rupid’s team opens a new employer account. Deliberately short — this is a two-minute job, not a data-entry exercise.
What’s on it:
What you can do:
Invitation Manager (Rupid’s side) : A User Role
One list showing every invitation and where it stands, so the team can see at a glance who has activated and who has not
What’s on it:
What you can do:
Activation (employer’s side)
The employer’s first-ever screen. Three short steps on one page with a progress strip, so it never feels like a form marathon.
What’s on it:
What you can do:
Onboarding Checklist
The employer’s home screen until the programme goes live. It answers one question at a glance: what do I do next?
What’s on it:
What you can do:
Admin Handover (Don’t implement it)
Used rarely but needed badly when the HR head changes. Kept as one simple form to avoid support tickets.
What’s on it:
What you can do:
| Case | Handling |
|---|---|
| The 72 hours pass with nobody activating | The link stops working. A fresh invitation goes out — automatically after a day, or by Rupid’s team — and the record shows both. |
| The contact person quits before activating | Rupid’s team replaces the contact and reissues; the earlier link stops working from that moment. |
| Someone forwards the invitation to a colleague | The link still demands the OTP on the original mobile, so a forwarded email alone does not grant access. |
| The company genuinely has no email domain | Rupid’s team records the reason and approves a personal address by exception — visible on the account so an auditor can see it was deliberate. |
| The admin loses access to their second factor | Rupid’s team resets it after verifying identity on a call, and the reset is on record. |
From nothing to a working login
| Detail | |
|---|---|
| Who | Rupid’s team, then the employer’s admin |
| Starting point | Commercials agreed |
| Steps | Rupid creates the account with the company name and the HR head’s work email and mobile → invitation lands in her inbox → she opens it, sets a password, enters the OTP, adds a second factor → the checklist appears with ‘Company verification’ as the first open step. |
| Result | A protected login exists and the employer knows exactly what comes next |
Handing over to a new HR head
| Detail | |
|---|---|
| Who | The outgoing admin |
| Starting point | She is leaving the company |
| Steps | Settings → Handover → enter the successor’s name, work email and mobile → the successor activates like a first login → her own access closes automatically. |
| Result | A clean handover, both sides on record, no shared passwords |
| Role | View | Create | Update | Delete | Approve |
|---|---|---|---|---|---|
| Rupid Ops | ✓ | ✓ | ✓ | ✓ | ✓ |
| Owner Admin | ✓ | ✗ | ✓ | ✗ | ✓ |
| HR Admin | ✓ | ✗ | ✗ | ✗ | ✗ |
| Finance | ✓ | ✗ | ✗ | ✗ | ✗ |
| Field | What it is | Type and allowed input | Length / range | Required | Example |
|---|---|---|---|---|---|
| Company Name | The registered name of the company | Letters, numbers, & . , - ( ) | 3–128 | Yes | One97 Communications Ltd |
| Everyday Name | A shorter name used on screens | Letters, numbers, spaces | 0–64 | No | Paytm |
| Contact Name | The first admin’s full name | Letters, space, dot, apostrophe, hyphen | 3–100 | Yes | K. Lakshmi Prasanna |
| Designation | Their role at the company | Letters, space, & , - | 0–50 | No | Head – HR |
| Work Email | Where the invitation goes; becomes the login | A company-domain email; personal domains refused | up to 254 | Yes | lakshmi.p@paytm.com |
| Mobile | For the OTP at activation and login | 10 digits, starting 6–9 | 10 | Yes | 9876543210 |
| Password | Set by the admin at activation | Upper, lower, number and symbol | 8–64 | Yes | (hidden) |
| Second Factor | The extra check at login | Authenticator app or SMS code | — | Yes | Authenticator app |
| When it happens | Message shown |
|---|---|
| Personal email used | Please use your company email address. Portal access carries authority over salary data, so we can’t set it up on a personal address. |
| Lapsed link | This activation link has expired. Ask for a fresh invitation and we’ll send one right away. |
| Used link | This link has already been used. If that wasn’t you, contact Rupid support immediately. |
| Weak password | The password needs at least 8 characters with an uppercase letter, a lowercase letter, a number and a symbol. |
| Three wrong OTPs | Too many incorrect codes. Please try again after 15 minutes. |
| Channel | Message |
|---|---|
| You’ve been invited to set up {company} on Rupid. The link works for 72 hours: {link} | |
| SMS | Rupid: your activation link for {company} has been sent to {email}. |
| Your Rupid access for {company} is active. Next on your checklist: company verification. |