Veyra HCM: a focused workspace for people operations

An employee's home screen leads with what is actually pending: open tasks, the next leave event, the latest payslip, and current compliance status — not a dense dashboard of everything at once. From there, employees keep their own preferred name, phone, address, emergency contact, locale, and timezone up to date themselves; changes to role, manager, employee number, or hire date route through an admin workflow instead.

Time is tracked by explicit action: an employee starts and stops a time entry, with no background tracking. Those entries roll up into a weekly timesheet that moves from draft to submitted to approved or rejected, and a manager only ever sees the timesheets of their own direct reports. Leave works the same way in spirit — an employee can see what leave is available, pending, and used, and every approval locks and rechecks the balance in one transaction so a leave can never be double-booked. A team calendar shows peers only that a colleague is "Unavailable," never why.

Payslips show the period, net, gross, and upload date, and open through a short-lived private download link — never a public URL, never a raw file sitting in storage. The benefits catalogue lists active plans with eligibility, coverage, and cost, and every selection or waiver is recorded for audit. Learning mixes global UmmeSyed courses with tenant-only courses, in video, article, reflection, or quiz form, and a completed course generates a certificate that marks completion — not accreditation. Alongside all of it, Kudos lets an employee send a short, public recognition note to a colleague, optionally tagged to a tenant value; there are no points, no leaderboard, and no cash value attached, by design.

An owner starts by creating the organization itself: a name, a slug, and a timezone. Branding is set next — either a small logo upload or an accessible brand color, and if a submitted color fails contrast the system automatically derives an accessible action shade rather than shipping an inaccessible one. The owner then creates the first tenant administrator and hands day-to-day setup to them.

Employees are brought in through a validated CSV import with a dry-run report before anything commits, rejecting rows with duplicate email addresses or employee numbers. From there, the administrator configures leave types and balances, benefit plans, and onboarding templates. Onboarding templates are reusable by employment type, location, or department, and assigning one to an employee snapshots its items — so editing a template later never rewrites the history of someone already assigned to it.

Only once setup is complete does the tenant activate, and activation itself is gated on an isolation smoke test passing — a final check that this organization's data behaves as its own before real people start using it.

Every organization's data is isolated at the database level, not just in the interface. Every tenant-owned record carries an organization identifier, and row-level security is enabled on every exposed table — so no configuration mistake in the interface can expose one tenant's data to another. Branding is data, never tenant-supplied CSS or HTML, which keeps that boundary intact even when an organization customizes how Veyra looks for its people.