Connect libraries
This page shows you how to browse a library another site shared with you.
You need two things from that site: its Share URL and an access token. If you're the one handing those out, see Share libraries instead.
Only Administrators see this dialog.
Connect a site
Open the Library modal, click Connected libraries in the header, then Connect a site.
Paste the Share URL and the access token, then click Connect. Every library that token opens is registered at once, and a snackbar confirms how many.
Connected libraries then appear in the rail alongside the official catalog, read-only. To change one of their patterns, edit it on the origin site. The change reaches you on the next refresh.
Manage a connection
Each row shows the libraries it brought in, the origin's host, and a status dot. Click the dot to re-check.
| Status | What happened |
|---|---|
| Green | Everything reachable |
| Unreachable | The origin didn't answer, or answered with a server error: site down, or a timeout |
| Access refused | The origin turned the request away: its Unblock license is no longer valid, or a security plugin or firewall in front of it blocks the call |
| No longer shared | The origin removed the library, or your token was paused, deleted, regenerated, or no longer opens it |
No longer shared covers several causes on purpose: the origin answers them all the same way, so nobody can probe which libraries it holds. Ask whoever runs it, or paste a new token and Reconnect.
A connected library is cached on your site. When the origin goes unreachable, the patterns you already pulled stay browsable. Only new ones stop arriving.
Row actions:
- Refresh libraries — pull the origin's latest catalog now
- Disconnect — removes its libraries from this site
- Open the row to edit the Share URL or paste a new Access token, then Reconnect
Two licenses matter, not one. Yours gates the Library on this site. The origin's license gates what it serves, so if it lapses your connection flips to Access refused even though your token is perfectly valid. Ask whoever runs the origin before assuming the token is the problem.
Next steps
- Share libraries — the origin side of the same setup
- Overview — browsing, filters and inserting