User Guide: PS Agent Renamed to SOC Operator
User Guide: PS Agent Renamed to SOC Operator
Release: 1.4.0
Overview
The role previously known as "Physical Security Agent" or "PS Agent" has been renamed to "SOC Operator" (Security Operations Center Operator) throughout the Bearing application. This change eliminates confusion with ServiceNow's own use of the term "Agent" (which refers to Virtual Agent chatbots and ITIL fulfillers) and adopts industry-standard terminology that more accurately reflects the role's responsibilities.
What Changed
|
Before |
After |
|
Physical Security Agent / PS Agent |
SOC Operator |
|
PS Agent Group |
SOC Operator Group |
|
PS Agent Assignment Group |
SOC Operator Assignment Group |
|
Physical Security Agent Criteria |
SOC Operator Criteria |
|
PS Agent Configuration |
SOC Operator Configuration |
Where the Name Change Applies
The updated label appears everywhere users interact with the application:
- Application workspace interface and navigation
- Group and assignment group names
- User criteria
- Configuration pages
- Form fields and dropdowns
- Notifications and system messages
- Help text and descriptions
What Did NOT Change
The underlying technical role name (x_yb_bearing.ps_agent) has not been changed. This is intentional - changing the internal role name would break existing security rules, ACLs, and business rules that reference it.
This means:
- Database field names remain the same
- ACL (Access Control List) references remain the same
- API references remain the same
This technical detail does not affect how the role appears or functions in the user interface.
For All Users
No action is required. You will simply see "SOC Operator" wherever you previously saw "PS Agent" or "Physical Security Agent." Your role, permissions, and access remain exactly the same.
If you have saved searches, personal reports, or bookmarks that reference "PS Agent," you may want to update the labels for your own reference - but the underlying filters and data will still work correctly.