Your organization's library

Your organization's library is your team's private shelf: equipment published there appears in every team member's pickers, so the whole shop designs with the same specs, and nobody outside your team can see it. This page also covers its private sibling, Your library: the equipment only you can see.

Who can see what

Library	Who sees it in their pickers	Who can change it
Org library (your team's)	Everyone on your team: owner, admins and members	Any team member, on a Pro or Studio plan
Your library (personal)	Only you, not even your teammates	Only you
Community library	Every LED.FYI user	LED.FYI reviewers

Your team's library stays private to your team:

• People on other teams, people on no team, and anyone signed out never see it: it isn't just hidden from their pickers, the server refuses to send it to them.
• Only your team can change or remove its rows.
• When someone leaves your team (or is removed), your team's equipment disappears from their pickers straight away. Projects they already made keep working, because specs travel with the project.
• Publishing to your team never puts anything in the public community library. That only happens if you separately submit a spec for review.

Everything happens in one dialog: the account menu (top right) → Equipment library…, or ⌘K → Equipment Library…. Top to bottom it holds the Community library, Create custom equipment, In this document, Your library, and Org library.

Who can do what

Opening the dialog requires a signed-in account (signed out, the menu item shows a "Sign in required" note instead). Any signed-in user can open it; the Org library section only ever lists your own team's rows. Publishing to or editing the org library additionally requires both of:

• being on a team (Teams & roles): any role (owner, admin or member) can publish; without a team the dialog notes "Publishing needs an organization", and
• a Pro or Studio plan: the check runs when you click a publish/update action (Plans & billing).

Personal-library actions (saving, re-editing, removing your own rows) need only the signed-in account.

Everything except panels is admin-only: only platform admins can create, edit, publish or submit processors, processor input/output cards, switches and receiver cards. Everyone else requests the model and the LED.FYI team adds it to the built-in library. Ones already in your libraries keep working in pickers and projects, and you can still remove them.

Publishing from a project ("In this document")

The In this document section lists every publishable equipment record embedded in the open project. Each row shows a kind badge (Panel, Processor, Switch, Output card, Input card), the brand and model, and its tier (Community, Personal or Org). Receiver cards aren't listed here; a platform admin authors a receiver card for the org with Create custom equipment below.

Click Publish to org to copy the spec into the org library. From then on it's in every member's pickers. On every row except panels the button is disabled unless you're a platform admin (hover it: "Only admins can add processors, switches and cards to a library.").

Update, not duplicate

LED.FYI fingerprints each spec by its content. If the row you're publishing already exists in the org library (even under a different tier or identity, such as a community panel your org previously published), the button reads Update instead, and clicking it bumps that existing org row's version rather than creating a duplicate. Rows already matched are marked "already in org library".

Publishing or updating also re-anchors every matching reference in the open document onto the new org version, as one undoable edit.

Authoring straight to the org library

Team members also get a Create custom equipment section: choose a kind (Panel, Processor, Switch, Output card, Input card, Receiver card), click New, and fill the same authoring form used everywhere else. The submit button reads Publish to org: the spec goes directly into the shared library without needing to exist in a project first.

Choosing any kind other than Panel and clicking New opens the request card instead of the form, unless you're a platform admin. For admins this is the only place to author output and input cards, since no Inspector picker offers + Create custom… for them.

Your library (personal rows)

Your library lists the private equipment you saved, typically via + Create custom… in a picker while signed in. Each row shows its kind badge, brand and model, and version (· v1, · v2, …), plus:

Control	What it does
Cloud icon	Submit to the public catalog for review: offered to platform admins on processors, switches and receiver, output and input cards; panels publish to the community directly. While pending, the row shows a Pending review badge; a rejection later shows "Rejected:" with the reviewer's note
Pencil	Re-edit the spec inline. Save changes bumps the version and re-anchors the open project onto it (one undoable step). Shown only on panel rows unless you're a platform admin
Trash	Remove the row from your library

When the list is empty it reads "No personal equipment yet. Create custom equipment from an Inspector picker."

Org library rows

The Org library section lists the organization's shared rows with the same anatomy: version tag, submit-for-review (non-panel kinds), edit, remove. Everyone on your team sees the list and can change it; editing an org row is plan-gated like publishing. When empty it reads "Nothing published yet. Publish equipment from the document above."

What edits and deletions do to projects

• Editing a personal or org row updates the row in place (version +1) and re-anchors the project you have open. Other projects keep the snapshot they embedded until someone opens and touches them.
• Removing a row never breaks any document that used it: specs travel with the project, so existing projects keep resolving from their embedded copy. The row simply stops being offered in pickers.

Personal vs. org: which to use?

You want…	Use
A one-off spec for this project only	Add to document (offline authoring) or Make custom…
A spec you'll reuse across your own projects	Your library (save from a picker while signed in)
A spec your whole team should design with	Org library (publish from a document, or author directly)
A spec every LED.FYI user should have	The community library