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
← Privileges Required for ObjectsAlert Source Actions →

Privileges Required to use Ad Hoc Alert Sources

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

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

Using Ad Hoc Alert Sources

The following privilege ranks are available on Ad Hoc Alert Sources:

  • Create - allows you to create an Ad Hoc 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 Ad Hoc Alert Sources you create.
  • View - allows you to view an Ad Hoc 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 an Ad Hoc Alert Source on the level the privilege was granted (system, partition).
  • Delete - allows you to create, view, and delete an Ad Hoc Alert Source on the level the privilege was granted (system, partition).
  • All - full control over an Ad Hoc Alert Source on the level the privilege was granted (system, partition).

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

Ad hoc 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 an Ad Hoc Alert Source that references them:

  • Application.
  • Alert Escalation.

Built-in Roles

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

Creating Ad Hoc Alert Sources

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

  • Create - privilege rank on Ad Hoc Alert Source in its partition or system-wide.
  • Edit - privilege rank on the Ad Hoc Alert Source, or on Ad Hoc Alert Source in its partition or system-wide.
  • Delete - privilege rank on the Ad Hoc Alert Source, or on Ad Hoc Alert Source in its partition or system-wide.
  • All - privilege rank on the Ad Hoc Alert Source, or on ad Ad Hoc Alert Source in its partition or system-wide.

Editing Ad Hoc Alert Sources

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

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

Deleting Ad Hoc Alert Sources

To successfully delete an Ad Hoc Alert Source, you must have one of the following privileges:

  • Delete - privilege rank on the Ad Hoc Alert Source or on Ad Hoc Alert Source in its partition or system-wide.
  • All - privilege rank on the Ad Hoc Alert Source or on Ad Hoc Alert Source in its partition or system-wide.

See Also

  • Privileges Required to use Applications
  • Privileges Required to use Alert Escalations
  • Privileges Required to use Objects
← Privileges Required for ObjectsAlert Source Actions →
  • Using Ad Hoc Alert Sources
  • Built-in Roles
  • Creating Ad Hoc Alert Sources
  • Editing Ad Hoc Alert Sources
  • Deleting Ad Hoc Alert Sources
  • 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 |