Getting started with Knowspread
This page is the entry point for a client starting with Knowspread. The goal is not to explain every system detail, but to put the first decisions in the right order.
First decisions
Section titled “First decisions”| Area | Question | Why it matters |
|---|---|---|
| Space | What will the company space be called and who owns it? | The owner is the last administrative fallback for the account. |
| Users | Will users be created manually, by import, or through API? | Defines the identity management and update process. |
| Required metadata | Do we need employee number, department, position, or birth date? | These fields affect imports, reporting, and traceability. |
| Groups | Will groups match departments, courses, or projects? | Groups drive bulk content assignment. |
| Content | Will the client use own content, purchased content, or both? | Version management, licenses, and marketplace flows differ. |
| Integrations | Should Knowspread connect to HRIS, LMS, or a data warehouse? | Integrations need credentials, identifiers, and retry rules. |
Minimal operational set
Section titled “Minimal operational set”Before launch, the client should know:
- who owns the space,
- who may manage users,
- which user identifier is authoritative,
- how groups will be structured,
- how leaving users will be handled,
- who approves content and assignment changes,
- where completion is checked.
First setup sequence
Section titled “First setup sequence”- Create or confirm the company space owner.
- Select the stable user identifier and agree who owns user data.
- Create a small test population with one owner, one admin, and at least two learners.
- Create the first groups with clear naming.
- Add launch content and confirm the active version.
- Assign content to one group and one individual learner.
- Complete one learning item as a learner.
- Check reporting, certificate state, and any configured integration output.
- Record screenshots and evidence in the QA log.
Definition of ready
Section titled “Definition of ready”The space is ready for broader rollout when the owner can demonstrate:
- how a new user enters Knowspread,
- how a user gets required learning,
- how completion is checked,
- how a mistake is corrected,
- who handles content, data, and technical escalation.