TLC Hub SitemapHow the hub sites flow
mapping TLC-Hubs

Ten sites, one family

A map of the TLC hub estate: what each site is for, the path a person takes through it, and how the sites hand over to one another. Split the way the estate itself splits — the hubs staff sign into, and the hubs a learner moves through.

10sites mapped
6TLC Hubs
4Learner Hubs
1sign-in for all of them

The two sections

start here

The estate at a glance

who talks to whom

TLC Base sits in the middle of everything. It is the only site that takes a password, and the token it mints is what lets every subdomain to its right skip the login screen. The Apprenticeships Portal is the one site outside that arrangement, because it has to work for someone with no account at all.

Map of the TLC hub estate A user signs in at TLC Base, which issues an SSO token. That token admits them to the five staff hubs and the three learner hubs behind the SSO. Two external systems sit in the launcher but are not SSO subdomains. The public Apprenticeships Portal sits outside the SSO and feeds into the Induction Hub. Staff or learner TLC Base tlcbase.org accounts · roles RBAC access-keys issues the SSO token MASTER TLC HUBS · STAFF Staffbasestaff. Knowledge Hubknowledge. Admin Hubadminhub. Guides Hubguides. Quality Hubnot built yet LEARNER HUBS · SSO Induction Hubinduction. Enrolment Hubenroll. e-Portfolioefolio. all *.tlcbase.org — one cookie, one token SSO token IN THE LAUNCHER, NOT SSO 360 Safeguardingstaffportal.360safeguarding.io Impact MISimpactmis.org.uk OUTSIDE THE SSO · PUBLIC Apprenticeships Portal No account. Answers stay in the visitor's own browser until they choose to express interest. account Every subdomain validates the token against sso_sessions, then checks its own site:* access-key. Logging out at any one of them clears the cookie and ends every session at once.

Dashed borders mark a boundary: the Quality Hub is registered and documented but has no files on disk yet, and the two systems top-right sit in the launcher without being part of the SSO.

Every site, in one list

quick reference
TLC Hubs · staff-facing
The master site — the only place anyone types a password.
TLCBase_2026/
The everyday staff intranet — where most people start their day.
TLC-Staffnet/
The apprenticeship funding rules, made navigable.
Knowledgebase_2026/
Back-office tools — documents, compliance, reporting, and the evidence in-tray.
AdminHub/
Illustrated how-to guides for every other hub — three levels deep.
TLC-Guides/
Audits, findings and actions.
qualityhub/
Learner Hubs · learner-facing
The public, pre-enrolment site — deciding whether this is for you.
tlcapprenticeships/
The first hub behind the sign-in — what happens, and what we need from you.
induction_hub/
One long form, broken into fourteen short steps.
enrolmenthub/
On-programme: evidence, criteria, off-the-job hours and learning.
eportfolio/

How to read this site

The flow strip

Every hub card carries a left-to-right strip showing the path a person actually takes through it — not the folder listing, but the order the pages are meant to be met in.

The page map

Under the strip, the hub's pages grouped by section, each with the file path it lives at. An arrow in a path (news.php → news_view.php) means the first page opens the second.

Keeping it current

Everything comes from inc/data.php. Add a hub or a page there and both section pages pick it up — the templates hold no content of their own.

Where this site lives

Deliberately outside the estate it documents: this sitemap is served from c:\xampp\htdocs\sandbox\hub-sitemap, while the hubs it maps stay in TLC-Hubs. It has no database, no SSO guard and no dependency on any of them, so it keeps working with everything else switched off.