External-facing
- Who can see it
- Knowledge that reaches beyond the organization
- The audience
- Students, professionals, peers, or the public
- What it optimizes for
- Reach, discovery, and a public face
- The workflows
- Education · Community · Public Knowledge
Workflows
What do you actually want to build?
A workflow is capabilities assembled into a coherent pattern that solves a specific organizational problem. Not abstract, not a feature comparison. A workflow is the answer to: "what does this platform do for an organization like mine?"
How to read this page
Capabilities become workflows. Workflows become your space.
A capability is a building block. A workflow is what happens when you configure capabilities for a specific purpose. Different organizations need different configurations — the five patterns below show how the platform adapts to each context without designing from scratch. Every one is a proven configuration: the organization applies it, customizes it, and extends it.
There are five, and they fall into two groups. Start by deciding which group you are in — then pick the workflow inside it.
Start here
First decision: who is the knowledge for?
Every workflow sits on one side of a single line — knowledge that reaches beyond the organization, or knowledge for a defined internal audience. Find your side first; the workflow inside it follows quickly.
| External-facing | Internal & regulated | |
|---|---|---|
| Who can see it | Knowledge that reaches beyond the organization | Knowledge for defined, internal audiences |
| The audience | Students, professionals, peers, or the public | Employees, members, and regulated stakeholders |
| What it optimizes for | Reach, discovery, and a public face | Control, structure, and a verifiable record |
| The workflows | Education · Community · Public Knowledge | Intranet · Compliance |
Internal & regulated
- Who can see it
- Knowledge for defined, internal audiences
- The audience
- Employees, members, and regulated stakeholders
- What it optimizes for
- Control, structure, and a verifiable record
- The workflows
- Intranet · Compliance
Five patterns. Pick the one that names your problem.
Three external-facing, two internal and regulated. Each is a proven configuration of capabilities for a specific context — open one to see how it is assembled and what it covers.
Education
A structured learning environment for external audiences — students, professionals, or the public. Courses, certifications, and learning paths with full accreditation support. Best for institutions, academies, and professional bodies offering accredited education.
Explore EducationCommunity
A professional network and discussion space organized around a shared domain, interest, or profession. Events, discourse, and shared resources, all in one persistent space. Best for associations, professional networks, and expert communities.
Explore CommunityPublic Knowledge
An open knowledge base visible to anyone — no registration required for discovery. Organizations share expertise with the world while retaining full ownership and control of what they publish. Best for organizations building thought leadership and public knowledge resources.
Explore Public KnowledgeIntranet
A private, branded knowledge hub for an organization employees and internal stakeholders. Structured content, internal training, and a persistent record of what the organization knows. Best for mid-to-large organizations centralizing internal knowledge and training.
Explore IntranetCompliance
A controlled environment for regulated industries — audit trails, mandatory training tracking, and certification management with full reporting. Built for organizations where documentation is as important as learning. Best for healthcare, finance, legal, and other regulated industries.
Explore ComplianceOne platform underneath
Different workflow, same building blocks.
Whichever workflow you start from, the same live tools — moderated Q&A, discussion, credentials — are already there the moment you need the next one.Most organizations find themselves between workflows — starting from one and expanding into others. That is expected.
The next step
Once you know the workflow, what to buy follows.
A workflow shows the "how" — the use-case configuration that fits your organization. A bundle packages that configuration commercially, so you do not have to figure out what to buy. Every workflow maps to a corresponding bundle.
Workflow
The how
The proven configuration of capabilities that fits how your organization actually works — applied, customized, extended.
Bundle
What you buy
The same configuration packaged commercially, giving you a coherent starting point with clear scope. Once you know the workflow, the bundle follows naturally.
Not sure yet?
That is the normal case
Most organizations sit between workflows or expand from one into others. The conversation is where it gets specific — and where the right starting point gets named.
Find the workflow that fits how you work.
Explore the bundles, see the full capability set, or talk to someone about your use case.