Tazvori

Product guides

Practical guides for employees and workspace administrators.

Log in

Published Aug 8, 2026 · Product documentation

Admin getting started

Day-1 checklist: settings, departments, employees, leave, and payroll.

Day-1 checklist

  1. Workspace settings — Company name, work week, holidays baseline (Settings).
  2. Departments & designations — Mirror your org tree before importing people.
  3. Invite / import employees — Add from Employees, or import CSV. Provision login when ready.
  4. Leave types — Configure annual / sick / casual under Leave → Types.
  5. First payroll structure (Professional+) — Components → Structure → Assign salaries.
  6. Roles & access — Review system roles; create custom roles under your plan ceiling.
  7. Branding — Logo and colors in Settings when available.

Done criteria

  • At least one department and one active employee
  • Leave types published
  • Admin can open Approvals inbox

Employee self-service

Clock in, leave, expenses, documents, payslips, and profile.

My Portal

Open My Portal for attendance snapshot, leave balances, announcements, and quick links.

Common tasks

  • Clock in/out — Attendance
  • [Demo GIF: clock-in.gif — see docs/PENDING_EXTERNAL_DEPENDENCIES.md]
  • Apply leave — Leave → Apply; check balances first
  • [Demo GIF: apply-leave.gif — see docs/PENDING_EXTERNAL_DEPENDENCIES.md]
  • Expenses — Submit claims with receipts
  • Documents — Policies and personal files
  • Payslips — Portal payslips hub after payroll publishes
  • Profile — Request name/bank changes (HR approves)
  • Notifications — Bell icon for approvals and announcements

Password

If password expiry is enabled, you will be prompted at /change-password.

Manager approvals & team

Team list, leave and expense approvals, workflow inbox, and boundaries.

What you can do

  • View your team and attendance
  • Approve / reject leave and attendance regularizations for direct reports
  • [Demo GIF: approve-leave.gif — see docs/PENDING_EXTERNAL_DEPENDENCIES.md]
  • Approve expenses when assigned
  • Act on recruitment interviews you are scheduled for
  • Clear items in the Approvals (workflow) inbox

What you cannot do (admin-only)

  • Change company settings, plans, or security policy
  • Edit salary structures or lock payroll runs
  • Create custom roles or assign elevated permissions
  • Process GDPR erasure requests

Ask your admin if you need broader access.

Manager performance guide

Run fair performance cycles, goals, reviews, 1:1s, and improvement plans.

Performance cycles

Use the cycle dates and criteria set by HR. Explain the purpose and deadlines to your team, and record feedback based on observed work rather than assumptions.

Goals

Agree a small number of clear, measurable goals with each employee. Check progress in regular 1:1s and update context when priorities change; do not silently rewrite agreed goals.

Reviews

Prepare specific examples, invite employee self-reflection, and give balanced feedback. Keep review comments professional, relevant to work, and free of sensitive personal information.

1:1s

Use 1:1s to remove blockers, recognize progress, discuss development, and make follow-up commitments. Record only the work-related notes your organization needs.

Performance improvement plans

Use a PIP only with HR guidance and according to company policy. State the expected improvement, support available, checkpoints, and consequences clearly. Do not make legal, medical, or employment-status promises; escalate sensitive cases to HR.

Payroll run playbook (India)

Structures, assignments, run, lock, payslips, and statutory notes.

Recommended order

  1. Salary components
  2. Structures (CTC breakup)
  3. Assignments to employees
  4. Tax declarations (as applicable)
  5. Open a payroll run for the month
  • [Demo GIF: create-payroll-run.gif — see docs/PENDING_EXTERNAL_DEPENDENCIES.md]
  1. Review exceptions / LOP
  2. Lock the run (irreversible for that period)
  3. Publish payslips and bank export

Warning

Locking a run cannot be undone from the UI. Double-check headcount and net totals first.

India notes

PF / ESI / TDS appear when components and employee statutory fields are configured. Use demo tenant data for a sample month walkthrough.

Recruitment / ATS

Jobs, careers page, pipeline, interviews, offers, and hire handoff.

Flow

  1. Create a job
  2. Publish careers listing (public URL pattern: /careers/{workspace})
  3. Manage candidates through pipeline stages
  • [Demo GIF: move-candidate.gif — see docs/PENDING_EXTERNAL_DEPENDENCIES.md]
  1. Schedule interviews
  2. Send offers from templates
  3. Hire → creates / links the employee record

Not included (yet)

External job-board sync (LinkedIn / Naukri / Indeed) is not shipped. Post manually and source candidates into Tazvori.

Attendance & leave policy setup

Shifts, regularization, leave types, holidays, and approval chain.

Setup

  • Shifts for office or rotational teams
  • Regularization policy for missed punches
  • Leave types + opening balances
  • Holidays calendar
  • Approval chain via reporting manager / workflows

Examples

  • Standard office: single day shift, Mon–Fri work week, annual + sick leave
  • Shift-based: multiple shifts, weekly offs vary, compensatory leave optional

Security, SSO & privacy

Password policy, sessions, IP allowlist, audit, GDPR — available now vs coming.

Available now

  • Password policy
  • Session list / terminate
  • IP allowlist
  • Audit export
  • GDPR export / deletion requests

Coming / config-only

  • Enforced TOTP 2FA for all users
  • Production-grade SAML/OIDC login (config form exists; complete IdP wiring before relying on it)

Mark features honestly in customer conversations.

Integrations setup

Slack, Calendar, API tokens, webhooks, and SAML troubleshooting.

Connect

  • Slack — incoming webhook URL
  • Google Calendar — OAuth when GOOGLE_CLIENT_ID is set; otherwise mock locally
  • API tokens — Sanctum tokens + X-Tenant
  • Webhooks — event subscriptions
  • SAML — entity ID, SSO URL, certificate

Troubleshooting “Connected but mock”

If Calendar shows connected in local/demo without Google credentials, events are simulated. Set production env vars before go-live.

Roles & plan entitlements

How plans unlock modules and how your company designs custom roles.

Model

  1. Super Admin packages modules on a plan
  2. Your tenant only sees permissions for enabled modules
  3. Admins create custom roles and toggle a subset of those permissions
  4. Users receive one or more roles (union of permissions)

Plan changes

Downgrading a plan removes unavailable permissions from roles automatically. Users lose related nav items immediately.

Examples

  • Retail: Store Manager (attendance + leave approve) + Regional HR
  • Startup: Team Lead (leave approve) without payroll
  • Services: Delivery Manager + Finance Ops