Libraries
For Owners and Operators (or a LibraryManager Role) creating the shared stores deployments reuse. A Library holds one kind of resource; its Members pull from Studio (Reader) or pull and share (Contributor); pushing from this page needs the Owner or Operator tier or the LibraryManager Role. Viewers and LibraryViewers read everything.
Before you start: adding members from your directory needs a connected identity provider. Publishing and pulling happen in Studio (Libraries and sharing); pushing from this page needs a deployment that already holds the item.
Create a Library
Open Libraries from the dock. Columns are Name, Type, Members and Created; New Library is disabled without the Owner or Operator tier or a Library administration grant.
- Click New Library.
- Name (up to 100 characters) and Description (up to 500).
- Type: Agent, Knowledge Graphs, Connector, Workflow, Environment or Data. A Library holds one type only.
- Click Create Library.
The Library's header shows Name, Library ID, Type and Created, a View selector (Overview, Members, Items) and Delete. Overview shows Description, Created by, Members, Items and Recent transfers (7 d) as "N pulls · N shares · N rejected".
Manage members
Members decides who can use the Library from Studio; the header reads "Contributors can publish from their Studio and pull; Readers can pull. Roles from Identity & Access Management govern who manages this Library here." Who has access lists Name, Type (User or Group) and Library access (Contributor or Reader); tick rows and Remove. Under Add from directory, choose Users or Groups, search, choose Contributor (default) or Reader, tick rows and click Add.
Push an item
Items lists what has been pushed and who can pull it. Click Add <Type>, choose the deployment, choose the item, click Push. Columns are Name (with a Source deleted badge if the original is gone), type-specific columns, Source version (vN), Source deployment and Pushed by/at. Type-specific columns: Workflow Nodes and Agent nodes with "Travels with N dependency(ies) · Arrives ready to activate" or "N agent node(s), re-assign after pull"; Connector Type, an AWS connector badged "Role in your account: trust must be set up before pulling"; Environment Image digest; Knowledge Graphs Nodes and Edges; Agent Agent type. Items cannot be added to a Data Library here.
Each row offers Activity, Versions and, for managers, Delete (removes every version; deployments that pulled it keep their copies).
Read versions and Activity
Versions lists every version pushed under the item, newest marked Latest, with Source version, Pushed by/at and Status (Available or Source deleted). Deleting the latest makes the previous one current; deleting the last version removes the item; pulled copies are never removed.
Activity lists every share and pull, newest first: Time, Share/Pull (Share, Pull or Delete), Deployment, Who, Version ("v2 → library v5" for a share), Status (Done, Rejected, Pending, or "In progress · <phase>" with attempts or sub-steps) and Reason (the rejection reason, or "Shared without dependencies"). A workflow that travels with dependencies expands into sub-steps, each with Kind, Item, Version ("library v1 → copy v1"), Outcome (Mapped, Pulled, Waiting or Failed) and Reason. Load more pages back.
What you should see
- A pushed item under Items with Source version vN; each further push adds a version.
- A Studio user's pull in Activity as a Pull row, Done, or Rejected with the reason.
- Members under Who has access as Contributor or Reader.
Notes
- One Library, one resource type. A workflow travels with its dependencies (its steps' agents, connectors, environments and knowledge graphs, including the graph a knowledge-graph update step writes to), so one Workflow Library serves a team's whole pipeline; the copy lands as a draft wired to the recipient's copies within a few minutes.
- Membership is per Library; console permissions on Libraries are Roles.
- Delete on the header asks you to type the Library's name.