Security classes are the mechanism through which Epic grants users the right to perform specific actions. Each class contains a defined set of privileges, such as editing public reports or exporting line-level details, and administrators assign the classes to users or user roles. Because the permission is attached to the class, adding or removing the class changes what the user can do without altering the content itself. The other options address different concerns. Summary targets are goals or benchmarks against which metric values are compared and do not control actions. Report groups determine which content is shared with which users, controlling visibility, not the ability to perform an action on what is visible. User types categorize users, for instance as clinical or administrative, for purposes of licensing and defaults, and they do not carry individual action privileges. The distinction between visibility and ability is a useful one. A user who cannot see a report needs a report group or distribution change, whereas a user who can see a report but cannot edit or export it needs a security class. Diagnosing the correct mechanism is the first step in resolving access requests efficiently.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit