← Azure SubscriptionsCatalog →

Privileges Required to use Box Connections

To use Box Connection, you need one of the following:

  • scheduler-administrator or redwood-administrator role.
  • scheduler-user or redwood-login role in combination with the following system-wide, partition-wide or object-level privileges.

Built-in Roles

  • The scheduler-administrator or redwood-administrator built-in role provides full control over all Box connections.

Creating and Modifying Box Connections

You need all of the following privilege ranks to be able to create and modify Box connections:

  • View - on partitions GLOBAL and REDWOOD.
  • View - on application REDWOOD.Box.
  • View - on the Redwood_Box extension point.
  • View - on the Redwood_Connections extension point.
  • View - on the existing Box process server and queue, if applicable.
  • Create - on process server and queue if a new process server and queue are required.
  • Edit - on BOXConnection.

Using the Box Component

You need all of the following privilege ranks to be able to use a Box connection:

  • View - on partitions GLOBAL and REDWOOD.
  • View - on application REDWOOD.Box.
  • View - on the Redwood_Box extension point.
  • Edit - on BOXConnection, this object is modified when the token gets updated.
  • View - on the Redwood_BoxConnectionConstraint constraint definition.
  • View - on Redwood_Box library.
  • Submit - on process definitions Redwood_Box_Upload_File, Redwood_Box_Download_File, Redwood_Box_Move_Item, and/or Redwood_Box_Rename_Item (depending on the functionality you want).
  • View - on the process server of the Box connection.
  • JobAdministrator - on queue the queue of the Box component.

Deleting Box Connections

  • View - on partitions GLOBAL and REDWOOD.
  • View - on applications REDWOOD.Box and REDWOOD..
  • View - on the Redwood_Box extension point.
  • View - on the Redwood_Connections extension point.
  • Edit - on BOXConnection.

See Also

← Azure SubscriptionsCatalog →