Getting started

Core concepts

The records SecureForce is built on and how they connect, from workspace to employee to deployment to roster to attendance to reports, payroll and billing.

Most "why don't I see…" questions come from one missing link in a chain. This page explains the chain.

The chain

Organization (company, branch, grade)      Clients & Sites (site point + radius)
            │                                        │
            ▼                                        │
       Employee  ──(same email)──►  Login (Field Employee)
            │                                        │
   Onboarding + KYC                                  │
            │                                        │
            ▼                                        ▼
       Deployment  (employee + client + site + role title + start date + pay rate + bill rate)
            │
            ▼
       Roster assignment  (employee + deployment + shift + site + date)
            │
            ▼
       Check-in on the phone  (photo + location vs the site's boundary)
            │
            ▼
       Attendance record  (present / late / half day / absent / leave / holiday / weekly off)
            │
            ├──► Daily report (DMR): approved headcount vs deployed vs present, per designation
            ├──► Payroll Prep: days × deployment pay rate (+ overtime)
            ├──► Billing Prep: days × deployment bill rate, per client and site
            └──► Client Portal and Reports

The records

RecordWhat it isCreated inNeeded by
WorkspaceOne organisation's private space. Nothing crosses between workspaces.Sign up / workspace switcherEverything
Company, branch, department, service line, gradeYour own company's structure.OrganizationEmployees, deployments
ClientA customer you supply staff to.Clients & SitesSites, deployments, billing
SiteA place where staff work, with latitude, longitude and a geofence radius.Clients & SitesDeployments, rosters, check-in
EmployeeOne record per person. Its email links it to a login.Employees, bulk onboardingEverything about that person
Login (member)A user account in the workspace with a role.Administration → Add memberSigning in
KYC caseThe pre-hire checks for one candidate.KYC VerificationDeployment readiness
Onboarding caseThe six-step checklist for one person.Employee profile → Start onboardingDeployment readiness
DeploymentA person posted at a site in a role, from a start date, with a pay rate and bill rate.Onboarding step 6, Deployment, bulk onboardingDMR "Deployed", payroll, billing
ShiftA time slot (Day 07:00–19:00, Night…).AttendanceRoster
Roster assignmentOne person on one shift at one site on one date, ideally linked to their deployment.AttendanceThe guard's check-in screen, muster, payroll link
Attendance recordWhat actually happened that day: check-in/out times, photo, distance, status.The guard's phone, or the musterDMR, payroll, billing, reports
Approved headcountHow many people of each designation the contract allows at a site.Field Attendance → SetupDMR "Total approved" and shortage
Data scopeA limit on what one login can see (a branch, client, site or employee).Administration → Data ScopesSupervisors, customers

Rules that catch people out

  1. The employee's email must match the login's email exactly, and only one employee may have it. Otherwise the person sees "Your account is not linked to an employee record".
  2. No roster for today means no check-in. The phone reads today's roster to know the site and shift.
  3. The deployment's role title must match the approved headcount's designation (e.g. both Security Guard). Otherwise the DMR shows the person under "Cover from another post" or "Unassigned role".
  4. A deployment counts as deployed from its start date. New deployments start today unless you set a date.
  5. Payroll and billing follow attendance → roster → deployment. If the roster entry isn't linked to a deployment, or the deployment has no rate, the days are counted at ₹0 and flagged.
  6. Without a data scope, a role sees the whole workspace. Supervisors and customers should always be scoped.
  7. Approved days are locked. Approve a day in the muster once it is correct; locked payroll periods can't be regenerated.

Statuses at a glance

RecordStatuses
Employeecandidate, onboarding, active, on leave, suspended, terminated
Onboardingdraft, in progress, blocked, completed, cancelled
Documentpending, submitted, verified, rejected, expired
KYC casedraft, in review, on hold, cleared, rejected
KYC checknot started, in progress, verified, failed, waived
Deploymentplanned, active, completed, cancelled
Shiftdraft, published, locked, cancelled
Attendancepresent, late, half day, absent, leave, holiday, weekly off, exception
Leave requestrequested, approved, rejected, cancelled
Payroll inputdraft, approved, exported, locked
Billing inputdraft, approved, invoiced, locked
Compliance taskopen, in progress, completed, overdue, waived