Internal documents
Guidelines, playbooks, policies, and reference material — searchable, versioned, and never lost in email again.
Workflow — Intranet
The intranet your team actually opens — and the reach an intranet was never supposed to have.
Internal knowledge sharing, team communication, and organizational learning on one knowledge platform that works like a professional space, not a corporate portal nobody visits twice. Internal by default, fully under your control — and the day you want to publish something outward, the same space does that too. Your intranet now has reach.
Internal by default — open up only what you choose, when you choose.
Why this exists
The knowledge is already there. Nobody can find it, and every departure deletes more.
Most intranets are where information goes to be filed and forgotten. Guidelines live in one folder, the playbook in someone’s inbox, the policy in a wiki nobody has updated since the last reorg, and the actual decisions in a chat thread that scrolled away last quarter. People stop looking because looking rarely works — and an organization that cannot find what it knows slowly forgets it.
The cost shows up at exactly the wrong moments. A new hire spends their first three months hunting for what a departing colleague never wrote down. The same question gets answered three times in three places by three people who never saw the other answers.
One space where the whole working memory lives together.
Documents, conversation, learning, and events in a single environment — not scattered across four tools that never talk to each other.
Team communication
Discussion spaces tied directly to the knowledge being discussed. Not another disconnected chat tool.
Onboarding paths
Structured journeys for new hires — the organization’s whole body of knowledge, sequenced.
Continuous learning
Internal courses and training programs running beside documents, not isolated in a separate LMS.
Internal events
All-hands, department meetings, and training sessions — recorded, searchable, and connected to source material.
Organizational memory
Knowledge persists beyond the person who created it — so a departure no longer takes a chunk of institutional knowledge with it, and a new hire ramps from what the team already knows.
Every resignation quietly deletes a piece of institutional memory — knowledge you paid for, walking out the door for good.
How it works
How the Intranet workflow operates.
-
Bring knowledge in
Documents, playbooks, and policies move into one searchable, versioned Container — out of inboxes and dead wikis, into a space your team actually uses.
-
Connect people to it
Discussion spaces sit beside the knowledge being discussed, and onboarding paths sequence the whole body of knowledge for new hires.
-
Keep the memory
Contributions stay attributed, searchable, and linked, so when someone leaves, what they knew stays — turnover stops deleting institutional knowledge.
Proof, not promise
The model already runs at enterprise scale.
This is the pattern proven in healthcare through doclift — where institutions and enterprises keep professional knowledge in one connected space instead of scattered across disconnected tools.
-
Insel Spital
One connected space
Professional knowledge lives in a single environment instead of folders, inboxes, and dead wikis.
-
RUAG
Knowledge that outlasts people
What the organization knows stays findable and attributed, so turnover stops deleting institutional memory.
-
Credit Suisse
A single environment, not three
People work where documents, discussion, learning, and events live together — not across disconnected tools.
Best for
Where what the team knows matters more than the tools admit.
Hospitals, universities, professional services firms, and regulated enterprises — any organization where expertise is the asset, turnover is real, and what the team knows needs to outlast the people who happen to know it today. If onboarding a new hire feels like rebuilding the same knowledge every time, this workflow is the fix.
Most organizations run the Intranet workflow alongside one or two others — typically Education for formal training and Compliance for regulated documentation. Because all three share the same Container and the same identity layer, there is no integration work between them — they are simply different views of the same body of knowledge.
Bringing existing material in matters as much as what happens after. For how the platform connects to the directories, single sign-on, and document tools you already run, see integrations.
Questions
Intranet workflow questions.
-
How is this different from the corporate intranet we already have?
A typical intranet is a filing cabinet people stop opening. This is a working knowledge platform where documents, discussion, learning, and events live together, stay searchable, and link to each other — so people find what they need on the first try and actually come back. And unlike a closed portal, it can reach outward when you choose: the same space that holds your internal knowledge can publish selected material to a wider professional audience, with one click and zero migration.
-
Is it internal-only, or is anything exposed?
It is internal by default and fully under your control. You decide if and when to open anything up — for example pairing it with the Public Knowledge workflow to publish selected material outward — but nothing leaves your Container unless you choose it.
-
What does "organizational memory" mean in practice?
Contributions stay attributed, versioned, and searchable. When someone leaves, their documents, answers, and decisions remain findable — so a departure no longer takes a chunk of institutional knowledge with it.
-
Do we need separate tools for training and compliance too?
No. Most teams pair this with the Education and Compliance workflows in the same Container. Because they share one space and one identity layer, there is no integration to build between them.
Where this connects.
The bundle that packages this workflow, the workflows it pairs with, and who it serves.
Intranet Suite
The commercial package built on this workflow — internal knowledge, communication, and learning in one bundle.
See the Intranet SuiteEducation workflow
The workflow teams most often pair this with for formal internal training and onboarding.
Education workflowCompliance workflow
Pair this for regulated documentation, versioned policy, and audit-ready records.
Compliance workflowFor Businesses
How internal knowledge fits a commercial organization that wants reach as well as control.
For businessesStop letting turnover delete what your organization knows.
Get Started begins a scoped conversation, not a contract — we look at where your knowledge lives today and give you a concrete next step on the first call. A space your team actually opens, with the reach a portal never had. Your space, your brand, your data — you own it; expertshare is infrastructure, not an intermediary.