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
← Ad Hoc Alert SourcesApplications →

Privileges Required to use Alert Source Actions

To use Alert Source Actions you need one of the following:

  • scheduler-administrator or redwood-administrator role.
  • system or partition-level permissions on the alert source and system-wide permissions on Alert Source Action
  • object-specific privileges on the alert source and system-wide permissions on Alert Source Action
note

Alert Source Actions are properties of alert sources and as such you require permissions on the mother-object as well, in this case the alert source.

Using Alert Source Actions

The following privilege ranks are available on Alert Source Actions:

  • Create - allows you to create an Alert Source Action on the level the privilege was granted (system, partition), you have no further privileges through this rank, you automatically get All privilege rank on Alert Source Actions you create.
  • View - allows you to view an Alert Source Action 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 Alert Source Action on the level the privilege was granted (system, partition).
  • Delete - allows you to create, view, and delete an Alert Source Action on the level the privilege was granted (system, partition).
  • All - full control over an Alert Source Action on the level the privilege was granted (system, partition).

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

Alert Source Actions 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 Alert Source Action that references them:

  • Library.
  • Subject.

Built-in Roles

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

Creating Alert Source Actions

You need one of the following privilege ranks to be able to create Alert Source Actions:

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

Editing Alert Source Actions

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

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

Deleting Alert Source Actions

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

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

See Also

  • Privileges Required to use Libraries
  • Privileges Required to use Process Servers
  • Privileges Required to use Ad Hoc Alert Sources
  • Privileges Required to use Process Alert Sources
  • Privileges Required to use Process Server Alert Sources
  • Privileges Required to use Queue Alert Sources
  • Privileges Required to use Objects
← Ad Hoc Alert SourcesApplications →
  • Using Alert Source Actions
  • Built-in Roles
  • Creating Alert Source Actions
  • Editing Alert Source Actions
  • Deleting 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 |