Introduction
Oracle Fusion HCM HR Help Desk can be configured to show different categories to employees and HR Help Desk agents. In this guide, I’ll walk through how to restrict category visibility using database resource conditions and data security policies in the Redwood experience.
Business Use Case
In Oracle HR Help Desk, you may need to restrict the categories available to employees while allowing agents to access a wider set of categories.
For example:
- Employees: Should see only Payroll, HR Support, and Benefits when creating a ticket.
- Agents: Should have access to all five configured categories.
This article explains how to achieve this using database resource conditions and data security policies.
Requirements
The requirement is to control category visibility based on the user type.
Employee
Employees should see only the following categories when creating an HR Help Desk ticket:
- Payroll
- HR Support
- Benefits
Agent
Agents should be able to see all five categories:
- Payroll
- HR Support
- Benefits
- Legacy System Data Migration
- Employee Background Check
Step-by-Step Solution
Step 1: Define HR Help Desk Categories
First, define the required categories in:
Manage Categories for HR Help Desk Requests

Figure 1: Manage Categories for HR Help Desk Requests.
Step 2: Navigate to Security Console
Navigate to:
Tools > Security Console

Figure 2: Navigate to Security Console.
Step 3: Open Manage Database Resources
In Security Console, navigate to:
Administration → Manage Database Resources

Figure 3: Open Manage Database Resources in Security Console.
Step 4: Search for SVC_CATEGORIES
Search for the following object:
Object Name: SVC_CATEGORIES
Select the object and click Edit.

Figure 4: Search for the SVC_CATEGORIES database resource.
Step 5: Create a Condition for Employees
Under General → Condition, click + to create a new condition.

Figure 5: Create a new condition for employee category visibility.
Step 6: Configure the Employee Category Condition
Enter the following details and click Save.
| Field | Value |
| Name | Employee Categories List |
| Display Name | Employee Categories List |
| Condition Type | SQL Predicate |
| Sql Predicate | (&TABLE_ALIAS.STRIPE_CD = 'ORA_SVC_HCM' AND (&TABLE_ALIAS.CATEGORY_CODE = 'D_BENEFITS' OR &TABLE_ALIAS.CATEGORY_CODE = 'D_HR_SUPPORT' OR &TABLE_ALIAS.CATEGORY_CODE = 'D_PAYROLL')) |

Figure 6: Configure the Employee Categories List condition.
This condition limits the categories available to employees to Benefits, HR Support, and Payroll.
Step 7: Create a Condition for Agents
Similarly, create a separate condition for agents using the following details:
| Field | Value |
| Name | Agent Categories List |
| Display Name | Agent Categories List |
| Condition Type | SQL Predicate |
| Sql Predicate | (&TABLE_ALIAS.STRIPE_CD = 'ORA_SVC_HCM' |

Figure 7: Configure the Agent Categories List condition.
Step 8: Save and Submit
After creating the required conditions, click:
Save & Submit

Figure 8: Save and submit the database resource conditions.
Configure Data Security Policy
Once the database resource conditions have been created, the next step is to configure the appropriate HR Help Desk Data Security Policy for the required roles.
Expected Result
After completing the configuration:
| User Type | Categories Available |
| Employee | Payroll, HR Support, Benefits |
| Agent | Payroll, HR Support, Benefits, LSDM, Employee Background Check |
This allows organizations to provide employees with a simplified category selection while giving HR Help Desk agents access to the broader set of categories required for ticket management.
Conclusion
Using database resource conditions on SVC_CATEGORIES provides a way to control HR Help Desk category visibility based on user roles.
The same approach can be considered when you need to control which categories are exposed to different user groups in the Redwood HR Help Desk experience.
If you found this article useful, feel free to comment and share your feedback. I’ll continue sharing practical Oracle HCM and HR Help Desk solutions based on real-world learning and implementation experience.


5 Comments