CIS-ITSM · Question #12
How is granular read and write access for a specific change model defined?
The correct answer is A. Setting Advanced Security to true and applying user criteria. Advanced Security on a Change Model enables granular access control by allowing administrators to define user criteria for read and write permissions on that specific model.
Question
How is granular read and write access for a specific change model defined?
Options
- ASetting Advanced Security to true and applying user criteria
- BConfiguring ACL's on the Create New landing page
- CChange properties
- DConfiguring ACL's on the chge_model table
How the community answered
(17 responses)- A88% (15)
- B6% (1)
- C6% (1)
Why each option
Advanced Security on a Change Model enables granular access control by allowing administrators to define user criteria for read and write permissions on that specific model.
Enabling Advanced Security on a Change Model activates user criteria fields that allow administrators to specify exactly which users or groups can read or write that model, providing granular access beyond standard table-level ACLs. This configuration is done directly on the change model record, not at the table level.
ACLs on the Create New landing page control access to initiating change records generally, not granular read/write access tied to a specific change model.
Change properties store configuration metadata of a change model such as workflow and approval settings, but do not define user-specific security access.
ACLs on the chge_model table apply broadly to all change model records, not to an individual model with user-criteria-based granularity.
Concept tested: Change Model Advanced Security and user criteria access control
Source: https://docs.servicenow.com/bundle/washingtondc-it-service-management/page/product/change-management/concept/change-models.html
Topics
Community Discussion
No community discussion yet for this question.