Redwood Documentation

Product Documentation

 

›Required Privileges

RunMyJobsSecurity

Roles and Users

  • Authorization
  • Partitions
  • Managing Users and Roles

Privileges

  • Privileges
  • Granted System Privileges
  • Object Security
  • Object Privileges
  • Granting and Revoking System Privileges
  • Granting and Revoking Object Privileges
  • System Privileges
  • Privileges
  • System Privileges

Required Privileges

  • Privileges Required for Objects
  • Ad Hoc Alert Sources
  • Alert Source Actions
  • Applications
  • Audit Rules
  • Audit Trail
  • SAP BAE connectors
  • Credential Protocols
  • Credentials
  • Datum Definitions
  • Documents
  • Alert Escalations
  • Event Definitions
  • Export Rule Sets
  • Export Processes
  • Formats
  • Email Alert Gateways
  • Housekeeping Dashbaord
  • Import Rule Definitions
  • Import Rule Sets
  • Import Sources
  • Imports
  • Chains
  • Process Alert Sources
  • Process Definitions
  • Definition Types (JobDefinitionsTypes)
  • Processes
  • Libraries
  • Process Locks
  • Monitoring Dashbaord
  • Monitor Alert Sources
  • Monitor Nodes
  • Operator Messages
  • Oracle Applications Systems
  • OHI Systems
  • Partitions
  • PeopleSoft Systems
  • Period Functions
  • Process Monitor Definitions
  • Process Monitors
  • Process Server Alert Sources
  • Process Servers
  • Query Filters
  • Queue Alert Source
  • Queues
  • R2W Catalogs
  • Registry Entries
  • Remote Systems
  • Reports
  • Resources
  • Roles
  • SAP Systems
  • Services
  • Shell
  • Subject Role Grant Expanded
  • Subjects
  • Submit Forms
  • Submit Frames
  • Table Definitions
  • Tables
  • Tabs and Links
  • Time Windows
  • Time Zones
  • Triggers
  • Users
  • User Messages
  • Visualization Alerts
  • Visualization Process Server Queues
← Monitoring DashbaordMonitor Nodes →

Privileges Required to use Monitor Alert Sources

To use Monitor Alert Sources, you need one of the following:

  • scheduler-administrator or redwood-administrator role
  • system or partition-level permissions
  • object-specific privileges

Using Monitor Alert Sources

The following privilege ranks are available on Monitor Alert Sources:

  • Create - allows you to create a Monitor Alert Source on the level the privilege was granted (system, partition), you have no further privileges through this rank, you automatically get All privilege rank on Monitor Alert Sources you create.
  • View - allows you to view a Monitor Alert Source on the level the privilege was granted (system, partition), you have no further privileges through this rank.
  • Edit - allows you to create, view, and edit a Monitor Alert Source on the level the privilege was granted (system, partition).
  • Delete - allows you to create, view, and delete a Monitor Alert Source on the level the privilege was granted (system, partition).
  • All - full control over a Monitor Alert Source on the level the privilege was granted (system, partition).

You always need View privileges on the partition of the Monitor Alert Source.

Process server alert sources can reference the following objects, you need at least View privileges on these objects as well as their partition(s) when you want to create/edit/delete a Monitor Alert Source that references them:

  • Application.
  • Alert Escalation.

Built-in Roles

  • The scheduler-administrator or redwood-administrator built-in role provides full control over Monitor Alert Sources.
  • The scheduler-viewer built-in role provides read-only access to Monitor Alert Sources.

Creating Monitor Alert Sources

You need one of the following privilege ranks to be able to create Monitor Alert Sources:

  • Create - allows you to create Monitor Alert Sources on the level the privilege was granted (system, partition), you have no further privileges through this rank, you automatically get All privilege rank on Monitor Alert Sources you create.
  • Edit - allows you to create, view, and edit all Monitor Alert Sources on the level the privilege was granted (system, partition).
  • Delete - allows you to create, view, and delete all Monitor Alert Sources on the level the privilege was granted (system, partition).
  • All - full control over all Monitor Alert Sources on the level the privilege was granted (system, partition).

Editing Monitor Alert Sources

To successfully edit a Monitor Alert Source, you must have one the following privileges:

  • Edit - privilege rank on the Monitor Alert Source, or on Monitor Alert Source in its partition or system-wide
  • Delete - privilege rank on the Monitor Alert Source, or on Monitor Alert Source in its partition or system-wide
  • All - privilege rank on the Monitor Alert Source, or on Monitor Alert Source in its partition or system-wide

Editing Alert Source Actions

To successfully edit an Alert Source Action, you must have one of the following privileges:

  • Edit - privilege rank on the Alert Source Action, or on Alert Source Action in its partition or system-wide
  • Delete - privilege rank on the Alert Source Action, or Alert Source Action in its partition or system-wide
  • All - privilege rank on the Alert Source Action, or on Alert Source Action in its partition or system-wide

See Also

  • Privileges Required to use Applications
  • Privileges Required to use Monitor Nodes
  • Privileges Required to use Objects
← Monitoring DashbaordMonitor Nodes →
  • Using Monitor Alert Sources
  • Built-in Roles
  • Creating Monitor Alert Sources
  • Editing Monitor Alert Sources
  • Editing Alert Source Actions
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |