A password record on its own tells you almost nothing useful. “Firewall admin” — okay, which firewall? Is there a runbook for what this login is actually for? Is there a warranty document or a config export sitting somewhere else in the system that a technician would also want open right now? Most password managers stop at “here’s the secret.” Weavestream’s Linked Items feature is built around a different assumption: a credential is rarely useful in isolation, and your documentation platform should know that.
The Problem With Siloed Records
Every IT documentation platform ends up with the same three buckets: credentials, assets, and articles. The trouble is that in most tools, those buckets don’t talk to each other. You store the firewall’s admin password in the vault. You store the firewall itself as an asset record with its serial number and firmware version. You store the failover runbook as an article. Three separate records, three separate places a technician has to think to look, and no structural connection between them beyond whatever naming convention you hoped everyone would follow.
That naming convention breaks down fast. “FW-Main-Admin” the password, “Main Office Firewall” the asset, and “Firewall Failover Procedure” the article don’t obviously belong together unless you already know they do. New technicians don’t have that context. Neither does anyone six months into a ticket queue who’s trying to move fast during an outage.
Linked Items: One Record, Many Connections
Weavestream addresses this directly. Every password record has a Linked items tab in its detail panel. From there, you can search for and attach any article or asset that exists in the same company — the firewall asset the credential unlocks, the runbook that explains how to use it, a related switch, an onboarding article for the client. There’s no limit on how many items you link, and no requirement that they be the same type of record.
This turns a password from a flat name-and-secret pair into a hub. Open the credential and you’re one click away from the exact asset it authenticates against, or the documentation that explains what to do with it. That’s a meaningfully different experience than searching three separate parts of the platform and hoping your naming convention held up.
Bidirectional By Design
The part that makes this genuinely useful rather than just a convenience is that the links go both ways. Link a password to an asset, and that asset’s own relations panel now shows the password too — you don’t have to remember to go set up the connection from both sides. Open a firewall’s asset record and the admin credential is right there, without anyone having had to think to attach it from that direction.
For MSPs, this matters operationally more than it sounds like it should. Technicians rarely start from the credential. They usually start from the asset — they’re looking at a switch that’s down, or a server that needs a reboot — and then they need the login. A one-directional link that only shows up when you’re already in the password vault doesn’t help in that moment. A bidirectional link does.
File Attachments Right Where You Need Them
Linked items cover other records, but sometimes what you need attached to a credential isn’t another Weavestream record — it’s a file. Weavestream supports attaching files directly to a password’s detail view, alongside the existing credential fields. A signed access agreement for a client-managed account, a vendor-issued PDF with recovery codes, a screenshot of a two-factor enrollment page — any of it can live on the credential record itself instead of in a separate file share that nobody remembers to check during an incident.
Combined with linked items, a single password record can end up being the actual center of gravity for a piece of infrastructure: the secret, the asset it unlocks, the runbook for using it, and the supporting paperwork, all reachable from one place.
Where This Actually Saves Time
The value of this shows up most during the moments that matter least conveniently — after hours, mid-incident, or when the technician working the ticket isn’t the one who originally set up the client. A few concrete scenarios:
A VPN goes down at 11pm and the on-call tech pulls up the VPN appliance asset. The admin credential and the failover runbook are both linked directly to it — no separate hunt through the password vault or the knowledge base guessing at naming conventions.
A new hire is onboarding a client for the first time. They open the client’s core switch asset and every linked credential and article is visible immediately, giving them a starting point instead of a blank vault and folder tree to search from scratch.
An auditor asks for evidence of how a specific credential is used. Because the password is linked to the asset it authenticates and the documentation describing its purpose, that context is already assembled — you’re not reconstructing it from memory or a spreadsheet.
Setting It Up
Linking is done from either side. Open a password’s detail panel, switch to the Linked items tab, and search for the article or asset you want to connect — the search is scoped to the current company, so you’re only matching against records that actually belong to that client. The same relations system is exposed from the asset and article side too, so once you’ve linked something, it stays visible no matter where you navigate from.
File attachments are added the same way you’d attach a file anywhere else in Weavestream — from the password’s detail view, without needing a separate upload flow or file management step.
Self-Hosted Means the Links Don’t Break
Because Weavestream is self-hosted, this relational structure lives entirely in your own Postgres instance — there’s no external API rate limit governing how many links you create, and no vendor-side sync delay between linking something on one side and seeing it reflected on the other. For MSPs who’ve dealt with a documentation platform where “related items” is a paid add-on or a laggy afterthought, having it built in and instantaneous is worth noticing.
If you’re already running Weavestream, open any password record and try the Linked items tab — attach the asset it belongs to and see it show up on that asset’s own record automatically. Not yet running Weavestream? The quickstart guide gets the full stack up with Docker Compose in a few minutes, and the relations system works out of the box with no extra configuration.