Organizations, departments, and positions
A roster that mirrors how the agency is actually organized, down to the position someone holds at a given location.
Implementation
Adopted in operational layers.
RCVanta can start with the workflows that matter most, then grow into integrations, reporting, automation, and cross-tenant visibility as the organization is ready.
Rollout path
Quick wins first, then deeper automation.
Most agencies go live on one operating surface, usually time clocking or training compliance, and add the next once the first is carrying real work.
- 1Stand up the tenant, import people, and set the roles and permission scopes each job needs.
- 2Turn on the operating surfaces that matter first, usually time clocking, scheduling, and training compliance.
- 3Connect ADP, Google Workspace, and file-based sources so records stay current without duplicate entry.
Foundations
The structure everything else resolves against.
Roster, locations, and permissions are set up once. Every later surface, from a punch to a training assignment, reads the boundaries they define.
Locations and geofences
Sites carry their own coordinates and radius, so a punch is tied to a place rather than taken on trust.
Roles and permission scopes
Permissions read as domain and access level. Roles are assigned per tenant, and a block on one domain overrides every grant for it.
Directory sync and auto-enrollment
Staff sync from Google Workspace, and a verified email domain can place a new hire into the right tenant without an administrator doing it by hand.