Configure Security Areas for the module

A security area defines a specific functional area within Service Manager, such as Incident, Incident Task, or Incident Management Configuration. Each security area definition includes default rights that are copied to the role whenever a new role is created.

Usually, you must create the following Security Areas for Service Manager Codeless module:

  • A Security Area that contains the default security rights and settings for tickets
  • A Security Area that contains the default security rights and settings for the module’s Management configuration. For example, the security rights for maintaining the Categories, Approval Definitions, and so on
  • A Security Area that contains the default security rights and settings for request tasks (only if your Service Manager Codeless module includes tasks)

The default rights and settings in the Security Area are copied to new roles that are created for this area. However, the values of specific settings are inherited only if no value is specified for those settings in the role.

For example, an out-of-box Request module contains the following Security Areas:

  • Request
  • Request Management Configuration
  • Request Tasks

Configure the Security Area settings

If you need to configure additional security rights in addition to the default rights (such as View, New, Update, Delete/Close, and Modify Template) to control a Security Area, you can modify the Security Area settings.

For example, out-of-box Request modules include a security control that determines whether users have the right to edit the task planner for a record. You can add settings such as this to the Request Area.