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
← R2W CatalogsRemote Systems →

Privileges Required to use Registry Entries

To use registry entries, you need one of the following:

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

Using Registry Entries

The following privilege ranks are available on registry entries:

  • View - allows you to view a registry entry on the level the privilege was granted (system), you have no further privileges through this rank.
  • Owner - allows you to create, view, and edit a registry entry on the level the privilege was granted (system).
  • All - full control over a registry entry on the level the privilege was granted (system).

To view, edit, or delete a registry entry, the user also needs to be able to access the full path to the registry entry, so also parent registry entries.

Creating Registry Entries

You need one of the following privilege ranks to be able to create registry entries:

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

Editing Registry Entries

To successfully edit a registry entry, you must have one the following privileges:

  • Owner - privilege rank on the registry entry, or on Registry Entry system-wide
  • All - privilege rank on the registry entry, or on Registry Entry system-wide

See Also

  • Privileges Required to Objects
  • Privileges Required to use Objects
← R2W CatalogsRemote Systems →
  • Using Registry Entries
  • Creating Registry Entries
  • Editing Registry Entries
  • 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 |