# Review what an employee test account can see

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/review-employee-account-permissions/)

Use fictional employee records to check the limits of a workforce role. Verify what the account can view and whether a higher-privilege page stays restricted.

## Before you start

- Use a test environment with fictional records and a separate administrator. Choose a single account and record its current role, access level or permission set before starting.
- Choose one read-only action that should work and a second action or page that should be restricted. Compare the same actions before and after changing the test assignment.

## Data and access

- **Shared or checked**. The workforce app shows the fictional fields allowed for the test employee’s role. The test checks a page that requires a higher role.
- **Check separately**. Service accounts, exports, and app connections can have different scopes from an employee’s page access.

## 1. Workday

In your test tenant, identify the domain that secures the report or field and the security group on that policy. Check the View permission with the test account. Check separately that the same account cannot reach a selected action requiring Modify.

**Check.** The test user can read the approved report or field. The separate action governed by Modify is denied.

## 2. BambooHR

In Settings, open Access Levels and inspect the test employee’s assigned level. After the scoped change, check Access Levels History for that employee and time. Open a permitted test record and try a page that should stay restricted.

**Check.** Access Levels History identifies the change for the test employee. The allowed record opens and the restricted page stays unavailable.

## 3. Access People HR

Compare the test user’s standard access level and any separately elevated rights. For a manager, use a fictional report and a fictional employee outside their reporting line. Choose a field or page whose access should differ between those records.

**Check.** The test manager sees the permitted fictional record. The record outside the reporting line remains outside the test result.

## 4. Breathe HR

Check your plan before using pay visibility as the test. On Regular and higher plans, HR and Finance permissions are separate. On Micro and Starter, the HR user already has access to salary information. Choose the expected result for the test account’s plan and permissions.

**Check.** The fictional pay field behaves as expected for the test account’s plan and role.

## 5. Cezanne HR

Compare HR Professional with Restricted HR Professional in the test environment. Pick a fictional employee record the restricted role should reach and a system configuration area the provider reserves for HR Professional. Check both with the test user.

**Check.** The restricted professional can open the in-scope test record, and the reserved configuration remains unavailable.

## 6. Fourth

In HotSchedules, inspect the test user’s Permission Set and store assignment. Apply an existing test set and confirm the change saved. Check one allowed and one restricted page at the selected store. Editing the permission set itself can affect other stores, so leave the shared set intact.

**Check.** The test user shows the intended Permission Set and store. Record the allowed and restricted outcomes inside that store.

## 7. Restore and recheck the test role

Restore the recorded assignment through the separate administrator. Start a fresh test session and confirm the original read and restricted page results.

**Check.** After restoring the assignment, a fresh session reproduces the test account’s original results.

## Check your result

The fictional record and restricted page behave as expected for the test account. Restoring the assignment reproduces the recorded starting behavior.

[How to verify your setup](https://keysigner.io/integrations/verify-a-setup/)

## If you get stuck

### The restricted page still opens

Check for a second role, elevated access, a plan-specific default or an existing session. Retest in the intended tenant, location or reporting relationship.

## Tools in this guide

- [Workday](https://keysigner.io/integrations/workday/)
- [BambooHR](https://keysigner.io/integrations/bamboohr/)
  - [Find access levels and field permissions in BambooHR’s guide](https://www.bamboohr.com/resources/guides/100-ways-to-customize-bamboohr)
- [Access People HR](https://keysigner.io/integrations/access-people-hr/)
- [Breathe HR](https://keysigner.io/integrations/breathe-hr/)
- [Cezanne HR](https://keysigner.io/integrations/cezanne-hr/)
  - [Review Cezanne user permissions](https://knowledge-base.cezannehr.com/user-permissions)
- [Fourth](https://keysigner.io/integrations/fourth/)

## Setup instructions

- [Compare Workday domain permissions](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/configurable-security-framework.html)
- [Find BambooHR access level changes](https://www.bamboohr.com/product-updates/access-level-history)
- [Check standard levels in Access People HR](https://help-peoplehr.theaccessgroup.com/en/articles/17264427-standard-levels-of-access)
- [Check which Breathe HR permissions your plan separates](https://intercom.help/breathehr/en/articles/2089510-user-permissions)
- [Compare the two Cezanne HR Professional roles](https://knowledge-base.cezannehr.com/hr-professional-vs-restricted-hr-professional)
- [Check Fourth HotSchedules permission set assignment](https://help.hotschedules.com/hc/en-us/articles/214873168-HS-How-to-Update-User-Permissions)
- [Contact Fourth support about HotSchedules permissions](https://www.fourth.com/support/customer-support)
- [Check which workforce data a connection can read](https://keysigner.io/integrations/guides/check-workforce-data-access/)

[More guides for this task](https://keysigner.io/integrations/tasks/test-account-access/)
