Folder authorizations grant users access to specific folders in the Planning domain and an authorization level for each folder. In addition, you can define different authorizations per job within a specific folder based on Application and Sub Application criteria.
EXAMPLE: If you want to allow the user to update jobs that belong to Application App1 but restrict this user from changing the Folder Properties, such as User Daily, Site Standards, and Business field values, define the fields, as follows:
Field |
Description |
|---|---|
Access Level |
Determines one of the following access levels for each user and group:
|
Control-M Server |
Defines the name of the Control-M/Server (or Control-M for z/OS) that processes the job. |
Library |
Defines the name of the library that contains the job’s folder. |
Folder |
Defines the name of the folder. In the Properties pane, this parameter indicates the folder where the job belongs. |
Job Level Authorization |
Determines whether to enable authorizations on jobs in a specific folder based on Application and Sub Application criteria. NOTE: You can only define job level authorizations if Control-M Workload Change Manager was installed (see Control-M Workload Change Manager installation). If Control-M Workload Change Manager was uninstalled, you can still define job level authorizations. |
Job Access Level |
Determines one of the following access levels for each user and group:
|
Application |
Provides a logical name for sorting groups of jobs. This parameter is used to supply a common descriptive name to a set of related job groups. |
Sub Application |
Indicates the name of the Sub Application where the job belongs logically. It is a sub-category of the Application parameter. For example, the Application is Finances, and the Sub Application is Payroll. |
The following procedures describe how to assign, edit, and delete folder authorizations:
Parent Topic |