HR Access Governance in the Data Lake
1. Overview
This challenge assesses your ability to implement role-based Data Fabric security for HR data in the Data Lake. You will:
- Generate an
EmployeeDataschema from a sample CSV file and upload the data through Atlas. - Create the
HRANALYSTandHRDEPTMANAGERsecurity roles and profiles. - Configure page, feature, and data access, including object-level and property-level restrictions.
- Control access to sensitive fields such as salary and hire date.
- Export the
HRDEPTMANAGERprofile as JSON for validation.
Throughout, apply the principle of least privilege.
Learning Objectives
- Understand the three layers of Data Fabric security: Page Access, Feature Access, and Data Access.
- Configure role-based access to Data Fabric pages and features.
- Implement object-level and property-level data restrictions.
- Create reusable security profiles for organizational roles.
Business Scenario
You are the Data Fabric administrator at Global Corp, where HR data from multiple departments flows into the Data Lake. The compliance team requires role-based access controls so that employees can access only the data appropriate to their responsibilities. You will configure security profiles for different organizational roles while meeting data governance requirements.
Prerequisites
Requirement | Detail |
|---|---|
Portal access | Infor OS Portal with the roles |
Sample data |
|
Naming convention: Replace
[YOUR INITIALS]with your own initials wherever it appears.
2. Guided Tutorial
Part 1. Create the Employee Data Schema
Use the Data Catalog Generate from Sample Data feature to create the schema automatically.
1.1 Download the sample file
Download employee_data.csv.
[Figure 1: Example contents of employee_data.csv]
1.2 Start the schema wizard
- Open Infor OS Portal.
- On the OS application page, select the Data Fabric card.
- In the navigation menu, expand Data Catalog and select Object Schemas.
- Click + Add and select Generate from Sample Data.
[Figure 2: Object Schemas page with the Generate from Sample Data option]
- Drag and drop
employee_data.csvinto the upload area, then click Next.
[Figure 3: Sample file upload step]
1.3 Define the object
Field | Value |
|---|---|
Object Name |
|
Description |
|
Data Catalog detects the column structure and data types automatically. Click Next.
[Figure 4: Object information fields completed]
1.4 Adjust property data types
Keep the defaults, except for the following changes (recommended best practice):
Property | Data Type |
|---|---|
| Date |
| Date |
| Date Time |
Click Next.
[Figure 5: Property Definitions with updated data types]
1.5 Configure additional metadata
Field | Value |
|---|---|
Identifier Paths |
|
Variation Path |
|
Timestamp Path, Delete Indicator Path, Archive Indicator Path | Leave empty |
Click Next.
[Figure 6: Additional Metadata configuration]
1.6 Review and finish
Review the Schema and Additional Metadata tabs, then click Finish.
[Figure 7: Schema review screen]
Part 2. Upload Data to the Data Lake
2.1 Add the Atlas Upload widget
- [Figure 8: Workspaces Insights sidebar with Add Insight Group]
- [Figure 9: Insight Group naming dialog]
- [Figure 10: Add Widget button in the new Insight Group]
- [Figure 11: Widget Catalog search results]
- [Figure 12: Closing the Widget Catalog and saving]
The Atlas Upload widget now appears in your Data Fabric workspace.
2.2 Upload the data file
- [Figure 13: File upload in the Atlas Upload widget]
- [Figure 14: Target object selection]
- [Figure 15: Upload confirmation message]
Part 3. Data Fabric Security Architecture
Data Fabric enforces security at three levels:
Level | Purpose |
|---|---|
Page Access | Determines whether a security role can open a specific Data Fabric page. |
Feature Access | Determines whether a security role can perform a specific action on a page. |
Data Access | Determines which Data Lake objects and properties a security role can use. |
Data Access supports three settings:
Setting | Effect |
|---|---|
Object access | Full access to the data object and all of its properties. |
Property access | Access to selected properties only (NDJSON and DSV objects only). |
No access | No access to the data object. |
Part 4. Create Security Roles in Infor OS Portal
Security roles must exist in Infor OS Portal before you can create profiles for them in Data Fabric.
The HR Department Manager role is used in the final challenge.
4.1 Open Security Roles
- On the OS application page, select the Security card.
- Go to Configure → Master Data Types → Security Roles.
[Figure 16: Navigation path to Security Roles]
4.2 Create the HR Analyst role
Click + Add new item and enter the following:
Field | Value |
|---|---|
Name |
|
Description |
|
Assign to New Users | Unchecked |
Add Users | Skip |
Click Save.
[Figure 17: HRANALYST role form]
4.3 Create the HR Department Manager role
Click + Add new item again and enter the following:
Field | Value |
|---|---|
Name |
|
Description |
|
Assign to New Users | Unchecked |
Add Users | Skip |
Click Save.
[Figure 18: HRDEPTMANAGER role form]
Part 5. Create the HR Analyst Security Profile
5.1 Create the profile
- Go to Data Fabric → Security.
- Click + to create a profile.
- In Select Security role, search for and select
HRANALYST_[YOUR_INITIALS]. - Click Save.
[Figure 19: Create Profile dialog]
5.2 Configure access controls
Select the HRANALYST_[YOUR INITIALS] profile and open the Access Controls tab.
Component | Setting |
|---|---|
Data Lake | ON |
Atlas | ON |
Atlas – Download | Enabled |
Atlas – Mark corrupt | Disabled (restricted) |
Atlas – Purge | Disabled (restricted) |
Data Ledger | ON (no additional permissions) |
Purge | OFF (data deletion restricted) |
[Figure 20: Data Lake access controls for HRANALYST]
All other components must remain OFF:
Component | Setting | Note |
|---|---|---|
Compass | OFF | |
Data Catalog | OFF | |
Metagraphs | OFF | |
Pipelines | OFF | Streaming data not required; this option may not be available |
Security | OFF | Administrative function |
Auditing | OFF | |
Utilities | OFF | |
Configuration Management | OFF |
[Figure 21: Remaining components switched off]
5.3 Configure data security
- In the profile, open the Data Security tab.
- Find
EmployeeData_[YOUR_INITIALS]and switch it ON. - Expand the Object access card.
- Enable Selected properties only.
- Select the properties shown below, then click Save.
Property | Access | Rationale |
|---|---|---|
| Allowed | |
| Allowed | |
| Allowed | |
| Allowed | |
| Allowed | |
| Restricted | Not required for the analyst role |
| Restricted | Not required for the analyst role |
| Allowed | |
| Allowed |
[Figure 22: Property-level data security for HRANALYST]
Part 6. Enable Data Security (If Required)
Important: Enabling data security affects all users in the tenant. Consult your system administrator first.
- Check the current status. If the Enable data security button appears at the top of the Security page, data security is currently disabled.
- Enable enforcement (only if approved). Click Enable data security, then confirm with Yes.
[Figure 23: Enable data security button and confirmation dialog]
Once enabled, users can access only the data they have been explicitly granted.
3. Challenge: Configure the HRDEPTMANAGER Profile
Department managers need broader access than HR analysts. Budget planning requires salary and hire date information, but birthdate information is not needed.
Business Requirements
The HRDEPTMANAGER role must:
- Access Atlas to browse and download employee data files.
- Access Compass to run analytical queries on employee data.
- Access Data Ledger to validate data integrity for reporting.
- View Metagraphs to understand data relationships (read-only).
- See all employee data except birthdate, including salaries and hire dates.
- Not access Purge (data deletion) or Security (administrative functions).
Tasks
Task 1. Create the profile
- On the Data Fabric Security page, click +.
- Select
HRDEPTMANAGER_[YOUR_INITIALS]as the security role. - Save and close.
Task 2. Configure access controls
Based on the business requirements, decide:
- Which Data Lake pages should be enabled?
- Should Compass access be enabled?
- Should Metagraphs access be enabled?
- Should Pipelines access be enabled?
- Should Security access be enabled?
Task 3. Configure data security
Based on the business requirements, decide:
- Which property access level applies to the
EmployeeDataobject? - Which properties should be included?
- Should salary and hire date be accessible?
- Should birthdate be accessible?
Task 4. Export the configuration
- After saving the profile, hover over
HRDEPTMANAGERin the Security Profiles list. - Click the More icon (three dots).
- Select Export.
- Save the JSON file for validation.
Submission
Upload the JSON file containing your HRDEPTMANAGER profile configuration.
Common Issues
- The
EmployeeDataobject is missing or misnamed. - The
Salaryproperty is not accessible. - The export was made too early, or the JSON is malformed.
- The role or profile name is wrong, or the role was not created in the Portal.
- The
accessLevelvalue or other JSON keys are invalid or missing. - The property list is missing for property-level access.
On this page
- HR Access Governance in the Data Lake