> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/studio/features-and-functionality/working-set.md).

# Working Set

### Overview <a href="#overview" id="overview"></a>

Working Sets lets users and integrations group the Records needed for one task or workflow, without changing where those Records sit in the Studio Library. It replaces external lists and disconnected trackers with a shared, in-product context for the work.

A team creates a Working Set, adds the relevant Records, performs permitted actions on them, and closes the set when the work is done. Records stay live and editable everywhere in Origin Studio throughout. The Studio Library remains the source of truth; the Working Set is an organisational layer on top of it.

Working Sets deliberately do **not** introduce record locking, staged changes, versioning or a separate approval workflow.

### Key concepts <a href="#key-concepts" id="key-concepts"></a>

<table data-header-hidden><thead><tr><th width="211.20703125"></th><th></th></tr></thead><tbody><tr><td>Term</td><td>Meaning</td></tr><tr><td>Working Set</td><td>A named group of Records for one piece of work. It references live Records; it never copies them.</td></tr><tr><td>Membership</td><td>A Record's inclusion in a Working Set. Only Records explicitly added are members; parents and children are never added automatically.</td></tr><tr><td>Open</td><td>The working state. Records can be added and removed, details edited, and Record actions run.</td></tr><tr><td>Closed</td><td>The finished state. Read-only, membership fixed, cannot be reopened in v1. The Records themselves stay editable.</td></tr><tr><td>Purpose of Work</td><td>Optional free text explaining why the Records are grouped.</td></tr><tr><td>Orchestration Reference</td><td>Optional link or ID for the external tool driving the work (for example a Jira ticket). A valid URL renders as a clickable link that opens in a new tab.</td></tr><tr><td>Creator</td><td>The user who created the set, or the API client for sets created by integration.</td></tr><tr><td>Last Updated</td><td>Changes only when the set itself changes: details edited, Records added or removed, set closed. Editing a member Record does not update it.</td></tr></tbody></table>

**Membership rules**

* A Record can belong to several Working Sets at once, Open or Closed.
* A Record can appear only once within the same Working Set.
* Membership never blocks other actions on the Record, including deletion.

### Lifecycle <a href="#lifecycle" id="lifecycle"></a>

A Working Set moves one way: Open to Closed. It can be deleted from either state.

1. **Create.** From the Working Sets page (Create Working Set), from the Create New option in the Add to Working Set drawer, or by API. The set starts `Open` with 0 Records.
   * Page modal fields: Working Set Name (required, need not be unique), Purpose of Work (optional, multi-line), Orchestration Reference (optional, URL or plain text).
   * Drawer: asks only for the Name and adds the selected Records straight away. Other details can be added later from the set's details page.
2. **Add Records.** From the Studio Library bulk actions bar, the Record Actions menu on Record Details, the Add Records button inside an Open set (opens the Library list in a full-screen modal), or by API. The drawer flow ends with a Review & Confirm step showing the destination, the Records and the total.\
   ![](https://2273874994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpbuQPZAuVlwuAEzIi462%2Fuploads%2FTWIFQKsqBtuMWUwjKilS%2Fimage.png?alt=media\&token=bc1a85b1-8ca4-43e4-943d-ce9d322aa5b1)
3. **Work.** Open each Record (it opens in a new browser tab, leaving the set in place) or run bulk actions from the set's Records table. All actions apply to the live canonical Records.\
   ![](https://2273874994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpbuQPZAuVlwuAEzIi462%2Fuploads%2FgdSyk3Wec3A2HMcdTHZs%2Fimage.png?alt=media\&token=9181d8bc-ed9b-431f-aa76-306626e54449)\
   ![](https://2273874994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpbuQPZAuVlwuAEzIi462%2Fuploads%2FBt1UevHErahA0Q7snNTW%2Fimage.png?alt=media\&token=59c928f6-fd84-4a10-91aa-76d21f176aaf)
4. **Close.** Close Working Set makes the set read-only and fixes its membership. It cannot be reopened. Closed sets appear on the Working Sets page's Closed tab.
5. **Delete (optional).** Removes the set, its details and its memberships permanently. The Records are untouched and stay in any other sets. Audit history is kept.

### Working with Records in a set <a href="#working-with-records-in-a-set" id="working-with-records-in-a-set"></a>

The Records table reuses the Studio Library List View: search, filtering, sorting, Manage Columns, row selection and the standard loading and empty states. Each member is its own row; there is no hierarchy view in v1.

Working Sets do not change how any action behaves. Each action keeps its existing flow, permissions, validation and Background Job behaviour; the set is just the launch point.

| Action                  | Individual Record | Bulk selection | Notes                                                                         |
| ----------------------- | ----------------- | -------------- | ----------------------------------------------------------------------------- |
| Bulk Edit               | No                | Yes            | Existing Bulk Edit flow                                                       |
| Export                  | No                | Yes            | Existing export flow                                                          |
| Add to Delivery Package | Yes               | Yes            | Existing Data Delivery access and eligibility rules                           |
| Delete Record           | Yes               | No             | Bulk Delete is shown under More but disabled until bulk delete is prioritised |
| Remove from Working Set | Yes               | Yes            | Removes membership only; no Record is deleted                                 |

**Remove from Working Set** asks for confirmation, then updates the Record count and Last Updated and clears the selection. It does not undo edits already made to the Record. If every Record is removed, the set stays Open with an empty table.

**Opening a Record** always uses the standard Record Details page and canonical URL in a new tab. No Working Set context travels with it, so edits made there carry no Working Set `changeReason`.

**Membership indicator on Record Details.** Users with Working Sets access see a Working Sets icon with a badge showing how many sets the Record belongs to. Selecting it lists each set (name, Records, status, purpose) and links to it. Users without access get the permissions error snackbar instead.

**Deleting a member Record.** The delete confirmation adds a Working Set memberships table whenever the deletion (including any dependent children) touches a set, Open or Closed. On confirm, the Records are removed from every set, counts and Last Updated are refreshed, and an audit event records why. Restoring a deleted Record does not put it back into its old sets. Users who can delete but lack Working Sets access see the table with names and statuses masked.

### Permissions and access <a href="#permissions-and-access" id="permissions-and-access"></a>

Access is controlled at two levels: a tenant entitlement, then a single policy permission.

**1. Entitlement (Administration > Feature Management).** Working Sets is an entitlement available on all Plans.

* Enabled: the feature, its API endpoints and a new Working Sets policy Resource Type become available.
* Deactivated: navigation and actions are hidden, and direct URLs and API requests are refused. Existing sets, memberships and policy configuration are kept but inaccessible.
* Reactivated: everything retained is restored.

**2. Policy (Working Sets Resource Type).** One permission, matching the Data Delivery model rather than separate CRUD rights.

| Permission  | Grants                                                                                        |
| ----------- | --------------------------------------------------------------------------------------------- |
| `access`    | View the Working Sets page; create, open, edit, close and delete sets; add and remove Records |
| `no access` | No Working Sets functionality                                                                 |

How checks behave:

* Authorisation is checked when each request (UI or API) is submitted.
* Add to Working Set and the membership icon stay visible to everyone. Users without access get a permissions error snackbar when they select them.
* Working Sets access does not bypass Record permissions. Bulk Edit, Export, Delivery Package and Delete still require their own existing permissions.

**Audit.** Administration > Audit Logs gains a Working Sets Resource Type. Events are written when a set is created, its details are updated, Records are added or removed, and when it is closed or deleted. Each event names the set (name and ID), the action, the user, API client or system process responsible, the timestamp and the affected values or Records. Deleting a set keeps its audit history.

### API and integration usage <a href="#api-and-integration-usage" id="api-and-integration-usage"></a>

Working Sets are designed to be driven by external orchestration as well as by people. An integration can create a set, populate it, and hand a reviewer a link to it from the ticket or task that triggered the work.

What the specifications commit to:

* Sets can be created and populated by API, with the same Name, Purpose of Work and Orchestration Reference fields as the UI.
* For API-created sets, Creator identifies the API client rather than a user account.
* Limits are enforced identically through UI and API, validated server-side against the latest counts.
* A request that would breach a limit fails whole: no partial set is created and no partial batch of Records is added. The response names the limit reached.
* API calls need the entitlement enabled and Working Sets `access` on the client's policy.
* Audit events attribute API activity to the API client.

**Typical pattern.** An upstream system (for example a mapping engine) creates a set for Records needing review, stores the Jira ticket URL as the Orchestration Reference, and the ticket links back to the set. The reviewer works the Records, then closes the set.

**Limits (per tenant)**

| Resource                   | Limit  | When reached                                                              |
| -------------------------- | ------ | ------------------------------------------------------------------------- |
| Open Working Sets          | 100    | No new set can be created until one is closed or deleted                  |
| Closed Working Sets        | 100    | The oldest Closed set is deleted automatically; its audit history remains |
| Records in one Working Set | 50,000 | The whole addition is blocked if it would exceed capacity                 |

Endpoint paths and payload shapes are not defined in these specifications; confirm them against the Origin Studio API reference once published.

### FAQ <a href="#faq" id="faq"></a>

**Does adding a Record to a Working Set lock it or change its status?** No. The Record stays live in the Studio Library and follows its normal lifecycle and permissions. Others can edit it at any time.

**If I add a Season, are its Episodes added too?** No. Only the Records you explicitly select become members.

**What happens if I try to add Records that are already in the set?** They are skipped and the rest are added, with a partial success message.

**Can I edit Records in a Closed set?** Yes, from Record Details. Closing freezes the set's membership, not the Records.

**Does deleting a Working Set delete its Records?** No. Only the grouping and its memberships go. Records remain in Origin Studio and in any other sets.

**I deleted a Record by mistake and an Admin restored it. Is it back in its sets?** No. Restored Records must be added back manually.

**Why didn't Last Updated change after I edited a Record?** Last Updated tracks changes to the set itself, not to its member Records.

**What happens at 100 Closed sets?** The oldest Closed set is deleted automatically when a new one closes. Its audit history is kept.
