Client and learning portals
A portal is built around one program. Clients or participants get a place to open materials, complete the steps that program requires, and see progress. The interface follows those requirements. What a person sees depends on the step they are on.
What goes in
The program’s materials, the steps a person must complete, the progress rules, and the systems that should stay connected. Materials and progress stay in that place rather than in a side thread.
What the engine does
- Set the materials and steps the program requires.
- Give each person access to what they are meant to see.
- Record completed steps and show progress.
- Connect only the tools the program needs.
What your team receives
A place for materials, steps, and progress, built for that program. Later changes to the program are scoped on their own. Connections are added only when the program needs them.