---
title: "Shared Elements and Workspace RBAC"
slug: "shared-elements-and-workspace-rbac"
tags: ["rbac", "security"]
updated: 2026-09-15T15:46:14Z
published: 2026-09-15T15:46:14Z
canonical: "docs.unqork.io/shared-elements-and-workspace-rbac"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](/unqorkai/docs/library-elements).

## Sharing Permissions

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

| Action | Required Permission |
| --- | --- |
| Share a data collection to the library | `create` or `update` on `sharedElementData` |
| Share a module to the library | `create` or `update` on `sharedElementModule` |

When a Creator lacks the required permission, **Share to Library** does not display in the element's ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20260915_154243_744ce88b72694e8cb218dca3ef596db6.svg?sv=2026-02-06&spr=https&st=2026-11-08T10%3A33%3A46Z&se=2026-11-08T11%3A33%3A46Z&sr=c&sp=r&sig=SVCcjKHklO9Qde1YDFRymXF1ybmXRWy5eGfMtRohnpg%3D) **(ellipsis)** menu.

Permissions are not the only reason the option can be absent: elements inside a versioned application never offer **Share to Library**, because the library cannot connect to a versioned application. See [Library Elements](/unqorkai/docs/library-elements).

## 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](/unqorkai/docs/workspace-level-role-based-access-control-rbac) and [Designer RBAC Overview](/unqorkai/docs/understanding-designer-role-based-access-control-rbac).

| Role | Can View Settings | Can Edit Settings |
| --- | --- | --- |
| **Administrator** (Creator Role) | Yes | Yes, any element, any scope |
| **CAN_MANAGE** (workspace role) | Yes | Yes, elements shared to workspaces they manage |
| **CAN_EDIT** (workspace role) | Yes | No |
| **CAN_VIEW** (workspace role) | Yes | No |

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.

| Scope | Who Can Modify Settings After Sharing |
| --- | --- |
| **Share to Workspaces and/or Applications** | Administrators and Creators with CAN_MANAGE in any workspace included in the sharing scope. |
| **Share to Environment** | Administrators only. CAN_MANAGE workspace roles cannot modify settings for environment-shared elements. |

> [!WARNING]
> 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](/unqorkai/docs/library-elements) for the unsharing workflow.

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-08-12 | Editorial pass: replaced "across the UnqorkAI platform" with "across the UnqorkAI platform" (EN-8001). |
| 2026-08-11 | Rewrote as a focused permissions reference; removed step-by-step workflow (covered by Library Elements), persona examples, best practices, and common scenarios (EN-8001). |
| 2026-08-10 | Updated navigation and Access & Usage step references (EN-8001). |

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.

Elements are are what you use to build Unqork applications. Elements include modules, workflows, Data Collections, Data Schema, and Record Collections.

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.

Scope is a tool that limits an application's access to a user's account. An application can request one or more scopes, this information is then presented to the user in the consent screen, and the access token issued to the application will be limited to the scopes granted.