Documentation that lives with your file transfers — onboarding guides, file specs, and runbooks, published next to the folders your partners use, walled per organization.
Every file-transfer relationship comes with paperwork that isn't a file transfer: the naming convention for invoices, the CSV column spec, the retry procedure when a feed is late, the checklist for onboarding a new partner. That knowledge usually lives in the worst possible places — email threads, an internal wiki the partner can't reach, or a PDF that was accurate two versions ago.
So the server is locked down, audited, and multi-tenant — and the instructions for using it are scattered somewhere with none of those properties. Every mismatch becomes a support ticket.
The Stylus SFTP Server Knowledge Base puts the documentation inside the same product: authored by your team, organized in a topic tree, published to exactly the organizations and groups that should read it — using the same accounts, the same groups, and the same audit trail as the file transfers themselves.
Upload one CSV per business day to /invoices/incoming before 18:00 UTC. Files are validated on arrival:
| Field | Format |
|---|---|
| invoice_number | INV-##### |
| date | ISO 8601 |
Moderators write in the browser with tools that match what technical documentation actually needs.
Insert with a Word-style picker or import straight from CSV. A floating table toolbar handles rows, columns, styles, borders with color, properties, and auto-fit — and columns resize by dragging.
A full draw.io diagramming application opens inside the page: flowcharts, network diagrams, shape libraries. Diagrams stay editable forever — open one later and change it in place.
Paste snippets in Java, XML, JSON, SQL, shell, PowerShell, Python, and more. Published pages render them highlighted, like a developer site.
Upload pictures and files into the page, or link files that live on the server itself — readers reach them through single sign-on, gated by their own folder permissions.
Pages start as drafts only moderators can see. Publish when ready; readers never see half-finished work. Unsaved changes are guarded on every exit.
Readers search across every published page their groups may see, with highlighted matching snippets — drafts and walled-off topics never leak into results.
Topic visibility is granted to groups, and groups belong to organizations. That makes the Knowledge Base a per-tenant documentation wall with zero extra infrastructure.
| Topic | Granted to | Customer A readers | Customer B readers |
|---|---|---|---|
| Getting Started | Customer A / Users, Customer B / Users | ✓ visible | ✓ visible |
| Customer A Onboarding | Customer A / Users | ✓ visible | not in tree, not in search |
| Customer B Onboarding | Customer B / Users | not in tree, not in search | ✓ visible |
| Internal Runbooks | (no grants) | moderators only | moderators only |
A grant on a topic covers everything beneath it, so one grant per customer is usually the whole configuration. Enforcement is server-side and uniform — the topic tree, page reads, search results, and attachment downloads all apply the same rule, so content outside a reader's grants isn't merely hidden; it's unreachable. An ungranted topic is visible only to your own staff, which makes "not shared yet" the safe default for work in progress.
Documentation for regulated workflows needs the same discipline as the workflows.
Nothing is ever overwritten. The History panel shows each version with time and author.
Any version renders next to the current page. Click a change in the list below and both panes scroll to the affected section, highlighted.
Revert restores an old version as a new one — history is preserved, and the revert itself is attributable and reversible.
Creates, edits, publishes, deletions, and visibility changes are recorded in the same audit trail as the file transfers.
The Knowledge Base is an Enterprise Edition feature, built on the same identity model that powers Enterprise multi-tenancy: organizations, groups, capability flags, and per-group access control. If you host file exchange for multiple customers or departments, the documentation wall comes with the tenancy you already configured — there is no second user directory to maintain and no separate wiki to secure.
It shares the server's white-label branding, so the portal your partners see and the documentation they read carry your identity, not ours.
Evaluate Enterprise Edition with the full Knowledge Base — topic walls, the rich editor, diagrams, and version history included.
