7.5 Employee Central Permissions for Administrators

7.5 Employee Central Permissions for Administrators

Quick Answer: EC permissions are split into Employee Central Effective Dated Entities (history-based blocks such as Job Information) and Employee Data (non-effective-dated items). Effective-dated cards use block actions: View Current, View History, Edit/Insert, Correct, and Delete. The Edit Link permission controls the pencil icon. Separate permission categories cover imports and foundation objects.

Permissions THR81 Covers

• Employee Central Effective Dated Entities
• Employee Data
• Employee Central Import Entities
• Manage Foundation Object Types
• Manage Foundation Objects
• MDF Foundation Objects

When granting permissions, consider category, card, and field levels. People Profile categories are also controlled in RBP. A user needs the category and at least one card in it (Section 4.1).

Employee Central Effective Dated Entities

This category covers elements and fields that track historical and future changes. It becomes available once the Succession Data Models are uploaded. Standard effective-dated entities include personalInfo, homeAddress, personRelationshipInfo (Dependents), jobInfo, compInfo, and jobRelationsInfo.

Block Actions

Important: the create, correct, and delete actions in History do not trigger workflows, even if workflow derivation rules are implemented. That is why History access is normally reserved for HR administrators (Section 9.4).

The Edit Link

The Edit Link permission controls whether the pencil icon is available on the card. Only its Edit/Insert level matters; the other levels are ignored. With it, users open and edit the card to start a transaction in People Profile, which can trigger event reason derivation and workflows. Edits can also be started from the People Profile Actions menu when the Update Employment Records permission is granted.

Field-Level Permissions

Newly enabled fields, whether standard, custom, or country-specific, appear in this category. Country-specific fields are prefixed with the country code, for example DEU-Travel Distance. THR81's exercises grant new fields all levels for the System Admin role.

Employee Data

Non-effective-dated entities are permissioned in the separate Employee Data category. For example, HR Information > Personal Contacts and National ID Card are granted here. Employment Information is the only non-effective-dated entity that supports field-level permissions.

Worked Example: IT Managers and Personal Contacts

ACE wants IT managers to edit their employees' contact information in the Personal Contacts card:

1. Proxy as an IT manager (Tammy Aberts) and confirm the card is not visible for an employee.
2. Manage Permission Groups: create Granted: IT Managers with people pool Job Code = IT-MGR, update membership, and confirm Tammy is included.
3. Manage Permission Roles: create IT Manager Access with Employee Data > HR Information > Personal Contacts > Edit.
4. Grant it to the IT Managers group, target Everyone, and exclude granted users from having the same access to themselves.
5. Log out and in, proxy as Tammy, and confirm she can see and edit the Personal Contacts card.

Employee Central Import Entities

This category lets you perform or restrict imports of person and employment objects, and ensures imports stay within the importing user's target population. It works together with Employee Central Import Settings > Import Employee Data (Section 8.2).

Foundation Object Permissions

Other EC Permissions to Remember

• Manage Hires: hire and rehire activities (Section 8.1).
• Employee Central Quick Actions: use rights for Quick Action templates (Section 10.1).
• Manage Workflows: workflow administration, the quick-approval option, and Professional Edition Manage Workflow Requests (Section 9.2).
• Manage System Properties > Employee Central Feature Settings: access to Manage Employee Central Settings, where features such as Position Management are switched on.

Testing with Proxy

Proxies are useful for verifying configuration and permissions in EC. When Private Data For Proxy Account Holder is deselected, the proxy does not see sensitive data such as home address or compensation (Section 2.3). THR81's default admin in the practice system can proxy as any user.