Overview
TOTAL ingests HR lifecycle and organizational context events from Workday via the Workday REST API and SOAP-based Human Resources Web Service. We poll the worker event history and organizational data endpoints on a configurable interval to collect, normalize, and correlate employee lifecycle events — hires, terminations, transfers, promotions, leave events, and organizational changes — that provide critical context for identity personas. Connector Type: PollingPrerequisites
- Workday Administrator access with permission to create Integration System Users (ISUs)
- Workday HCM tenant (production or sandbox) with active worker data
- Integration Security Group configured with appropriate domain permissions
- Approximately 20 minutes to complete setup
Step 1: Identify Your Workday Tenant URL
- Sign in to your Workday tenant
- Your tenant URL follows the format:
or for production:
- Paste the Tenant URL into the TruU Portal
Step 2: Create an Integration System User (ISU)
- In Workday, search for the Create Integration System User task
- Enter:
- User Name:
ISU_TruU_TOTAL - New Password: Set a strong password
- Require New Password at Next Sign In: Unchecked
- Do Not Allow UI Sessions: Checked (API-only access)
- Session Timeout Minutes: 0 (no timeout for API sessions)
- User Name:
- Click OK
Step 3: Create an Integration Security Group
- Search for the Create Security Group task
- Select Integration System Security Group (Unconstrained)
- Enter:
- Name:
ISSG_TruU_TOTAL
- Name:
- Click OK
- Add
ISU_TruU_TOTALas a member of this security group
Step 4: Configure Domain Security Permissions
- Search for the Maintain Permissions for Security Group task
- Select
ISSG_TruU_TOTAL - Grant Get (read-only) access to the following domain security policies:
- Click OK
Step 5: Activate Security Policy Changes
- Search for the Activate Pending Security Policy Changes task
- Enter a comment:
TruU TOTAL integration - read-only API access - Click OK to activate
Security policy changes must be activated before the ISU can access the configured domains.
Step 6: Enter Credentials in the TruU Portal
In the TruU Portal, navigate to Settings → Connectors → Add Connector → Workday and enter:- Workday Tenant URL: Your tenant service URL
- Tenant Name: Your Workday tenant name
- Username:
ISU_TruU_TOTAL - Password: The ISU password
Security & Privacy
What We Access
- Read-only access to worker lifecycle events and organizational data via Workday API
- Employee hire, termination, transfer, and promotion events
- Organizational hierarchy (department, manager, cost center)
- Work email addresses for identity resolution
- All queries use effective date filtering — we only fetch new events since the last poll
What We Don’t Have Access To
- Personal information (home address, SSN, bank details, compensation)
- Write access to any Workday data
- Ability to modify worker records, org structures, or business processes
- Payroll, benefits, or financial data
- Recruiting or talent management data
Updating or Rotating Credentials
Rotate Password (Recommended: Per your organization’s policy)
- In Workday, search for the Change Integration System User Password task
- Select
ISU_TruU_TOTAL - Set a new strong password
- Update the password in the TruU Portal
- Click Test Connection to verify
Revoke Access
To immediately remove TOTAL’s access:- Option A — Disable in the TruU Portal
- Option B — Disable the ISU in Workday (search for Edit Integration System User)
- Option C — Remove the ISU from the security group
Rate Limiting & Scalability
Workday API Rate Limits
Ingestion Capacity
HR lifecycle events are inherently low-volume. Even a large enterprise with 100K+ workers generates only 200–2K events/day (hires, terminations, transfers, promotions, role changes). TOTAL polls Workday on a longer interval (default: 15–30 minutes) and typically uses < 1 req/min during steady-state polling — a negligible fraction of the shared ~10 req/s tenant budget. Rate limiting is rarely a factor for this signal class. TOTAL also performs a periodic full worker profile sync (~100K records, run daily or weekly) for persona enrichment. This is scheduled during off-peak hours and uses configurable page sizes to minimize API impact.Event Freshness
Transaction-based events are available in the Workday API near real-time. Batch processes may lag hours. TOTAL polls on a configurable interval (default: 15–30 minutes). End-to-end latency is typically 15–60 minutes.Resilience
TOTAL uses cursor-based ingestion with at-least-once delivery. The polling cursor only advances after events are successfully collected, normalized, and published. If any step fails, the cursor stays put and the next poll replays from the last known-good position. No events are lost. Transient failures (429s, 5xx, timeouts) are retried automatically with exponential backoff. After 5 consecutive failures, the connector self-pauses and can be re-enabled from the TruU Portal. Workday retains full transaction history, so data loss is effectively impossible regardless of outage duration.Connector Design
Each connector polls on an independent, configurable interval. Events are batched and published in per-user order to preserve sequence integrity for persona building. Connector workers are stateless and scale horizontally. Profile syncs run on a configurable schedule with checkpointing. All polling intervals, sync schedules, and batching parameters are tunable from the TruU Portal.Part 2: Event Types & Data Schema
Signal Classification
Event Types We Ingest
TOTAL extracts the following categories of events from Workday. Every event ingested is tied to a specific worker (human identity). HR events provide organizational context and behavioral risk indicators — they tell TOTAL who a person is, what they do, how their role is changing, and whether they are under organizational stress (PIPs, disciplinary actions, investigations, compensation changes). This context is essential for building accurate personas and detecting insider threat patterns where behavioral drift correlates with HR friction. Organizational-level events that cannot be attributed to a specific person are excluded.Employee Lifecycle Events
Job Change Events
Organizational Events
Manager & Reporting Events
Performance & Talent Events
Disciplinary Events
Compensation & Benefits Events
Worker Profile Context (Enrichment Data)
In addition to events, TOTAL periodically syncs the following worker profile data for persona enrichment:Sample Source Event (Workday — Employee Transfer)
TOTAL Normalized Events
Transfer Event
Performance Improvement Plan Event
Disciplinary Action Event
How This Feeds TOTAL
Persona Building
Workday is the authoritative source of organizational truth for TOTAL personas. HR events provide the context that makes all other signals meaningful:- Role context — A user’s job title, department, and job family determine what applications, data, and systems they should be accessing. Without this context, TOTAL cannot distinguish between normal access for a security engineer and anomalous access for a marketing manager.
- Organizational graph — Manager relationships, department structures, and cost centers define peer groups. TOTAL uses peer group analysis to establish behavioral baselines — if everyone in Engineering-Security accesses the same set of tools, that’s normal. If one person suddenly accesses Finance tools, that’s anomalous.
- Lifecycle transitions — When a user transfers departments, gets promoted, or goes on leave, their expected behavior changes. Workday events allow TOTAL to proactively adjust personas rather than generating false positives during legitimate role transitions.
- Tenure and status — New hires, long-tenured employees, and contingent workers have different behavioral baselines. Workday provides the context to model these differences.
Anomaly Detection
TOTAL’s behavioral engine uses Workday events to detect:- Terminated employee access — continued system access after a termination event in Workday indicates a deprovisioning gap or compromised credentials
- Pre-termination data exfiltration — when a termination event is initiated, TOTAL retroactively analyzes the user’s recent behavior for signs of data staging or exfiltration
- Role transition abuse — access patterns that don’t align with a user’s new role after a transfer or promotion, indicating the user retained old access they should no longer have
- Leave of absence anomalies — system activity during a leave of absence period, indicating potential account compromise
- Organizational context for other signals — Workday context enriches every other signal source. An Okta authentication anomaly is more significant when TOTAL knows the user just transferred to a sensitive department
Insider Threat Risk Correlation
HR friction events are among the strongest leading indicators of insider threat activity. TOTAL correlates these signals with digital behavior across all other connectors:- PIP + data access spike — a worker placed on a performance improvement plan who suddenly increases file downloads, SharePoint access, or email forwarding volume is exhibiting a classic pre-exfiltration pattern
- Disciplinary action + off-hours activity — a worker who receives a written warning and begins accessing systems outside their normal working hours shows behavioral drift that warrants elevated monitoring
- Negative performance review + communication pattern change — a worker who receives a poor review and shifts communication patterns, reduces collaboration, or increases external email volume signals potential flight risk
- Compensation change + resignation indicators — a worker who is passed over for a raise or bonus and begins accessing job boards, updating LinkedIn, or downloading personal files may be preparing to leave — and potentially take data with them
- Demotion + privilege retention — a worker who is demoted but retains elevated access from their previous role represents both a governance gap and a heightened insider risk

