Guides

These guides describe Knowspread screen by screen, each one captured from a running space rather than written from memory. Every claim carries a marker saying how far it was verified, so Fact is something we measured and Assumption is something we inferred and have not confirmed.

The order below is a path, not a catalogue. If you administer a space, the middle three sections are the work.

If you are starting from nothing

Starting a space walks the whole thing end to end — three screens in one sitting, from no organisation to one you can invite people into. Inviting people continues from there to the first person in it, and to telling whether they ever arrived. Buying content crosses to the marketplace, which is a separate site — and names the one field there that decides which of your organisations pays. Writing a course is the other way to get content: make it yourself, and let the draft tell you what is still missing. Publishing a version is what then makes it real — and the only step in these journeys that cannot be undone. Building a plan is how content reaches people at all, and starts by noticing how many plans you already have. Setting recurrence shows how to save and verify a recurrence interval for content already assigned to a plan. Assigning a plan puts people into it, and says why the counters read nought for a moment afterwards. Going through a course is the first journey seen from the learner’s side, all the way to the certificate — and to the declaration you can get one without. Following completion closes the chain: one table, one person finished, one not. Building a quiz adds a test to a course that is already published — which means founding its next version — and passing a test takes that test, fails it once, and finds out that no certificate arrives until it is passed. The chapters below describe each screen on its own; those journeys put them in order.

Everyone

The screens each person meets whatever their role.

• Signing in — getting into a space
• Finding your way — how the navigation is arranged
• Your learning — what you have been assigned
• Your profile — your name, photo and password

Setting a space up

What an owner decides once, and what everything else then depends on.

• General settings — the space’s identity and what its users may do
• User details and sign-in rules — what people must tell you
• Code lists — sites, job titles and labels the rest draws on
• Permissions — who administers the space

Getting people in

• Access links — how people join, and why each link is a credential
• Managing users — the list, its filters and its columns

What people learn

• Content — the material, its versions and licences
• Study plans — the unit that actually gets assigned
• Approvals — requests for training bought from outside
• The admin dashboard — overview, and what Premium adds

Integrating

• API credentials — the client_id and client_secret a system needs
• Webhooks — events the space pushes to you

How these were made

Each screenshot comes from a live space, masked before capture and refused outright while anything real remained. What could not be captured safely is recorded as such rather than faked.

Chapters captured in a personal space say so. Several screens behave differently there — some refuse and show the refusal as an empty state — and each affected chapter notes it.