Before you can document anything about a client, you need somewhere to put it. A credential belongs to a client. An asset belongs to a client. A network diagram, a set of onboarding articles, a list of monitored domains — all of it belongs to a client. The quality of that organisation determines whether your technicians can find what they need when they need it, or end up asking a colleague who isn’t available.
Weavestream’s Company module is where that organisation lives. Every piece of data in the platform — assets, passwords, articles, files, domains — is scoped to a company record. Understanding how those records are structured is worth five minutes of your time.
Everything Starts With a Company
A Company record in Weavestream is the top-level container for a tenant. Create one for a client, and you get a dedicated space for all of that client’s documentation. No shared buckets, no tagging scheme that drifts over time, no cross-contamination between clients. Each company has its own asset inventory, its own credential vault, its own documentation folders, its own files, its own monitored domains.
For MSPs running Weavestream as their primary IT documentation platform, this means the question “whose is this?” is always answered by the record’s location — not by a tag, a prefix, or tribal knowledge.
What a Company Record Holds
Beyond acting as a container, a company record stores everything you’d want to capture about a client at the account level:
| Field | What it’s for |
|---|---|
| Name & slug | Display name and URL-safe identifier |
| Type | CLIENT, PROSPECT, VENDOR, INTERNAL, PARTNER, or OTHER |
| Notes | Rich-text freeform field for account-level observations |
| Quick notes | Short plain-text shown inline in the company list |
| Primary contact | Name, title, email, and phone for the main point of contact |
| General contact | Office phone, fax, website, general email |
| Address | Full postal address with country |
| Logo | One uploaded image used as the client’s branding marker |
| Parent company | Optional link to a parent record for hierarchy |
| Sticky note | A pinned alert banner (Info, Warning, or Critical) |
That contact and address data tends to be undervalued until the moment someone needs it. When a technician is heading to a client site and wants the street address without digging through an email thread, or when you need to reach a client contact quickly, having it in the documentation platform — rather than scattered across CRM exports, spreadsheet tabs, and memory — saves the kind of time that’s hard to measure until it stops being a problem.
Client Types That Actually Match Your Business
The type field on a company record isn’t just a label — it’s how you filter and manage your list at scale.
| Type | Typical use |
|---|---|
| CLIENT | External paying customers |
| PROSPECT | Active sales pipeline |
| VENDOR | Suppliers and service providers you depend on |
| INTERNAL | Your own organisation |
| PARTNER | Business partners and referral relationships |
| OTHER | Anything that doesn’t fit cleanly |
MSPs often underestimate how useful it is to document vendors alongside clients. The firewall vendor whose support number you need at 2am, the ISP whose escalation path is non-obvious, the hardware supplier with a specific RMA process — those all belong somewhere. Having VENDOR records in the same platform as CLIENT records means technicians have one place to look, regardless of whether they’re looking for client documentation or a vendor contact.
INTERNAL records are similarly useful: document your own infrastructure, your own tooling, your own processes as a first-class tenant. When a new hire needs to know how your RMM is configured or where your backup solution sends alerts, it’s in the same platform as everything else.
Parent-Child Hierarchy for Complex Clients
Some clients aren’t a single flat entity. A managed services customer might have a head office and several branch sites. A corporate parent might have multiple subsidiary companies, each with their own IT footprint. Weavestream supports this with parent-child company relationships.
When you set a parent on a company record, you’re modelling the organisational structure in your documentation. The branch site’s assets and passwords are scoped to that site’s record, while the corporate parent has its own. You can navigate the hierarchy directly from the company view.
Cycle prevention is built in — a company can’t be set as its own ancestor — so the hierarchy stays sane as you add records over time.
Sticky Notes: Alerts That Stay Visible While You Work
Every company record can carry a sticky note: a short banner (up to 300 characters) that stays pinned at the top of every admin page for that client while you’re working in their context. There are three severity levels:
- Info — for reminders and context (“contract renewal in Q3”, “client prefers out-of-hours maintenance”)
- Warning — for active issues you don’t want a technician to miss (“router firmware update pending — schedule with client”)
- Critical — for urgent flags that need immediate attention (“client under active ransomware investigation — do not make changes without approval”)
This is the kind of feature that sounds small until you’ve had a technician accidentally reboot a server that was mid-migration because the relevant context was in a ticket nobody had open. A persistent, visible banner in the documentation platform is a different communication channel than a Teams message or a ticket comment. It’s there when the record is open, regardless of whether anyone mentioned it on the call.
Call It Whatever Your Team Calls It
“Company” is the default terminology, but Weavestream lets you change it workspace-wide from Admin → Settings. Common alternatives:
- Client — natural for MSPs
- Tenant — fits multi-tenanted services
- Department — for internal IT teams documenting business units
- Site — for physical location-centric documentation
- Organisation — for professional services firms
The change is cosmetic: URL paths, API endpoints, and database columns remain company / companies internally. But the label your team sees throughout the interface — navigation items, headings, list views — reflects the term you chose. If your team has called them “clients” for a decade, there’s no reason for your documentation platform to fight that habit.
Data That Stays With the Record
One of the practical advantages of organising everything under a company record is that client data travels with the client context. When you navigate to a client in Weavestream, you’re seeing all of their documentation in one place:
- All asset records for that client
- The full credential vault scoped to that client
- Every article and documentation folder
- Uploaded files and photos
- Monitored domains and SSL certificates
- The team members who have access
There’s no cross-client search result that requires you to figure out which client a record belongs to. There’s no credential that was accidentally shared with the wrong tenant. The company boundary is enforced by the data model, not by convention.
For MSPs who’ve dealt with the consequences of a documentation platform where client data is insufficiently isolated — a technician who searched the wrong client’s assets, a credential exported from the wrong vault — this structural separation is worth paying attention to.
Getting Started
If you’re already running Weavestream, company records are the first thing you’ll see after logging in. To set up parent-child relationships, edit a company record and use the Parent field. To configure a sticky note, go to Company → Settings and find the Sticky note panel.
New to Weavestream? The quickstart guide walks through standing up the full stack with Docker Compose. The company module is where everything starts — once the container structure is in place, the rest of the platform’s documentation features build naturally on top of it.