Demo Script, question 13 of 15, read 8 Nov 2026
Show me the sensitive-field control
All 15 questionsSee the Scorecard
Ask to mark salary sensitive and then ask the assistant for it as a manager.
| Vendor | The answer on its pages | Status |
|---|---|---|
| Shapes | Field-level permissions: edit, view or hidden per permission level (help center), and a release note on restricting fields. | yes |
| Rippling | Data permissions configured at the platform level. | yes |
| Humaans | Role-based permissions and explicit data scopes when connecting. | yes |
| Factorial | 'ONE enforces each person's permissions on every request. No permission, no action.' | yes |
| Workday | Actions scoped to the user's identity with safeguards for sensitive enterprise data. | yes |
| BambooHR | Access levels gate the connectors; no sensitive-field control named. | partial |
| HiBob | Sensitive data protected by role-based permissions; agents cannot create a new path to restricted information. | yes |
| Lattice | Answers scoped to each user's Lattice access. | partial |
| Personio | Unlimited access and permissions on CorePro. | partial |
| Deel | Not stated on the AI pages read. | not published |
| Gusto | Data categories chosen per connection. | partial |
| Paylocity | Role-based security in the HCM. | partial |
| ADP | Role-based access in Workforce Now. | partial |
| Sage | Permission levels in Sage HR. | partial |
Sources
- Shapes, read 8 Nov 2026
- Rippling, read 8 Nov 2026
- Humaans, read 8 Nov 2026
- Factorial, read 8 Nov 2026
- Workday, read 8 Nov 2026
- BambooHR, read 8 Nov 2026
- HiBob, read 8 Nov 2026
- Lattice, read 8 Nov 2026
- Personio, read 8 Nov 2026
- Deel, read 8 Nov 2026
- Gusto, read 8 Nov 2026
- Paylocity, read 8 Nov 2026
- ADP, read 8 Nov 2026
- Sage, read 8 Nov 2026
Last reviewed 10 Nov 2026.