Shared Elements and Workspace RBAC

Sharing a module or data collection to the library requires specific workspace permissions. This article covers which permissions let Creators share elements, who can manage Access & Usage settings after sharing, and how the sharing scope affects those controls. For the sharing workflow, see Library Elements.

Sharing Permissions

Creators must hold create or update permission on the relevant resource type to share an element to the library.

When a Creator lacks the required permission, Share to Library does not display in the element's (ellipsis) menu.

Access & Usage Permissions

The Access & Usage dialog is visible to all Creators who can see the element. Edit access is gated by Creator Role and workspace role. For a full description of each role and how to assign them, see Workspace-Level RBAC and Designer RBAC Overview.

When a Creator cannot edit settings, the Edit button does not display in the Access & Usage dialog. A message indicates that Administrator or CAN_MANAGE access in at least one shared workspace is required.

Scope and Permission Constraints

The sharing scope set in the Access & Usage dialog determines who can modify settings after an element is shared.

Important: Once an element is shared to the environment, only Administrators can change its sharing scope or unshare it from the library, regardless of any Creator's workspace role.

Removing Workspace Access

Removing a workspace from an element's sharing scope does not break existing application connections. Applications in the removed workspace continue to function, but Creators there can no longer open or edit the element in Module Builder.

Unsharing removes the element from the library entirely and returns it to a single application. This option is available only when the element is connected to no more than one application. See Library Elements for the unsharing workflow.