TLC Hub SitemapHow the hub sites flow
Section one · staff-facing

The TLC Hubs

The sites staff sign into. One master site holds the accounts and the roles; the rest are subdomains that trust its token and check their own access-key before letting anyone in. They share two databases, one design system, and a cross-site launcher managed centrally from the master.

6hub sites
1sign-in, shared by all
2shared databases

How a staff session runs

the common path

Every hub below starts the same way, because none of them can authenticate anyone on their own.

1
tlcbase.org/login
The only password prompt anywhere in the family.
2
Token + cookie
A token row in sso_sessions, a cookie scoped to .tlcbase.org.
3
hub.php
The destinations page — a tile per hub the user's role grants.
4
A subdomain
Its sso/sso.php validates the token, then checks its own site:* key.
5
The launcher
From there, the icon bar moves you between hubs without going back.

The hubs

six sites

In the order a new starter meets them: the master first, then the intranet they will live in, then the specialist hubs.

TLC Base Staffbase Knowledge Hub Admin Hub Guides Hub Quality Hub

TLC Base

The master site — the only place anyone types a password.
TLCBase_2026/ tlcbase.org Master / SSO issuer

Every other hub hangs off this one. TLC Base owns the user accounts, the roles, and the RBAC access-keys; it mints the SSO token that lets a signed-in user walk into any sibling subdomain without signing in again. It is also a working site in its own right: document submission and approvals, enrolment, complaints, surveys, right-to-work, and the whole admin back office.

Step 1
login.php
The one password prompt in the family.
Step 2
authenticate.php
Validates, mints the SSO token, drops the .tlcbase.org cookie.
Step 3
hub.php
The destinations page — a tile per hub the role can reach.
Step 4
The chosen hub
Or straight on into TLC Base's own sections.
Front door
Sign in
The single sign-in form for the whole family.
login.php
Authenticate
Checks credentials, writes the sso_sessions row, sets the parent-domain cookie.
authenticate.php
Hub / destinations
Where a signed-in user lands: a tile per hub their role grants, plus personal quick actions.
hub.php
Global sign-out
Deletes the token row and clears the cookie — signs the user out of every hub at once.
logout.php
Reset password
Self-service reset off the login page.
resetpassword.php
What staff do here
My profile
The profile every hub's account menu points back to.
profile.php
Submit a document
Assessors submit work for review; goes into the approvals queue.
submit_document.php
My submissions
Track what you sent, and pick up anything returned to you.
my_submissions.php
Approvals
The reviewer side of the same queue.
approvals/
Enrolment
Staff-side enrolment records and uploads.
enrol.php
Complaints
Log and track a complaint.
complaints.php
Surveys
Learner, employer, staff and safeguarding surveys.
survey.php
Right to work
RTW checks and evidence.
rtw.php
Back office
Admin
Users, roles, RBAC access-keys, settings, and the Hub Launcher that drives every site's cross-site icon bar.
admin/
Heatmaps
Survey and activity heatmaps.
heatmap/
Learner action dashboard
Actions raised against learners, tracked to closure.
learner_action_dashboard/
e-Portfolio section
The assessor + admin halves of the e-Portfolio moved here — that is why efolio bounces those roles back.
admin/ (e-Portfolio)
Proposals & design requests
Client proposals and the design-request pipeline.
proposals/, designrequest_serve.php
Protected file serving
Uploads are never linked directly — each type has a serve script that re-checks who is asking.
*_serve.php

Staffbase

The everyday staff intranet — where most people start their day.
TLC-Staffnet/ staff.tlcbase.org site:staff Largest hub

The original intranet, and still the biggest site in the family. News, events, the staff directory, policies and procedures, the resource library, 1-2-1s, the helpdesk and its own full admin panel. Its top bar and account menu are the pattern every newer hub copied, and its section tabs are database-driven (the buttonnav table) rather than hard-coded.

Arrive
Home
News hero, alert banner, quick links, what's coming up.
Choose
A section tab
Tabs come from the buttonnav table, so admins can reorder them.
Browse
A list page
news, events, policies, procedures, forms, resource_library…
Open
A _view page
Every list has a matching *_view.php detail page.
Act
Ticket / request
Raise support, request a design, report a safeguarding concern.
Home & people
Home
News hero, alerts banner, quick links.
index.php
Staff directory
Search colleagues; open a person for their full record.
directory.php → directory_view.php
Shoutouts
Peer recognition wall.
shoutouts.php
Question of the day
A daily question, voted on in place.
questionoftheday.php → qotd_vote.php
Business cards
Generates a branded card + QR vCard per person.
card/business_card.php, card/vcard.php
Content
News
Company stories.
news.php → news_view.php
Events
Calendar or list, plus birthdays and anniversaries.
events.php → events_view.php
Policies
Versioned, with owner, approval date and review date.
policies.php → policies_view.php
Procedures
Three levels: topic, then procedure, then its numbered steps.
procedures.php → procedures_list.php → procedures_view.php
Forms
Downloadable forms, foldered.
forms.php
Boards & brand
Notice boards and the brand guide.
boards.php, brand.php
Learning
Resource library
Learning materials by programme and topic.
resource_library.php
Repository
The wider document store.
repository.php
EPA
End-point assessment records; has its own light login (epalogout.php).
epa.php → epaview.php
Ask for something
Support / helpdesk
Raise a ticket, comment on it, watch it to closure.
support.php → support_ticket_create.php → support_ticket_view.php
Design requests
Brief the design team; files served through designrequest_serve.php.
designrequest.php → designrequest_create.php → designrequest_view.php
Safeguarding report
Raise a concern; evidence served through safeguarding_serve.php.
safeguarding_report.php
1-2-1s
Both sides of the 1-2-1: the staff view and the manager view, printable.
onetoone.php → onetoone_create / _view / _manager / _print
Behind it
Admin panel
Users, members, news, events, policies, procedures, forms, resources, recruitment, tickets, surveys, visitors, assets, access control and logs.
admin/
Web API
JSON endpoints an external apprenticeship system POSTs learner data to.
webapi/uacc.php, webapi/cacc.php
Databases
Shared with TLC Base, AdminHub and Knowledge — one dump covers all four.
tlcstaffnet + tlc_holiday

Knowledge Hub

The apprenticeship funding rules, made navigable.
Knowledgebase_2026/ knowledge.tlcbase.org site:knowledge

A reference hub built around one question: which document has to exist, for which learner, at which point? It answers that four ways — as a matrix, as a timeline, as a downloadable pack, and as a searchable library — and carries an evidence form so a gap can be filled without leaving the page.

Start
Overview
What the funding rules require, in plain English.
Locate
Document matrix
Document against learner type — the "do I need this?" grid.
Sequence
Learner line
The same documents laid out along the learner journey.
Collect
Document pack
The set assembled and ready to take away.
Evidence
Form → Submitted
Fill the gap; the submission lands in AdminHub's evidence in-tray.
Section nav
Overview
Apprenticeship funding rules — the orientation page.
index.php
Document matrix
The TLC document matrix: what is required, for whom.
matrix.php
Learner line
The same requirements plotted along the learner journey.
journey.php
Document pack
The assembled pack and its checklist.
pack.php
Reference library
The underlying source documents.
library.php
Evidence & help
Evidence form
Pick a form, fill it, confirm. Definitions come from AdminHub.
forms.php → form.php → submitted.php
Ask
Question box over the rules (inc/ai_config.php).
ask.php

Admin Hub

Back-office tools — documents, compliance, reporting, and the evidence in-tray.
AdminHub/ adminhub.tlcbase.org site:admin

The quiet half of the family. AdminHub owns the form and evidence definitions the other hubs render, receives what learners and staff submit, and reports on the result. It is the receiving end of the Knowledge Hub's evidence form.

Arrive
Overview
What needs attention today.
Receive
Evidence in-tray
Submissions land here from across the family.
Act
Review / action
evidence_action.php — accept, return, or chase.
Report
Reporting
Compliance position, exported or printed.
Section nav
Overview
The landing dashboard.
index.php
Documents
The document store and its states.
documents.php
Compliance
Where the organisation stands against the rules.
compliance.php
Reporting
Exports and printed reports.
reporting.php
Admin forms
Build, fill, save and print a form. Definitions live in inc/forms_def.php.
forms.php → form.php → form_save.php → form_print.php
Evidence in-tray
Everything submitted, waiting to be dealt with.
evidence_admin.php
Underneath
Form definitions
One definition, rendered by both AdminHub and the Knowledge Hub.
inc/forms_def.php, inc/form_fields.php
Evidence definitions
What counts as evidence for each requirement.
inc/evidence_def.php
File handling
Uploads are stored out of reach and served through a checking script.
evidence_upload/ → evidence_file.php

Guides Hub

Illustrated how-to guides for every other hub — three levels deep.
TLC-Guides/ guides.tlcbase.org site:guides Double-gated

The manual for the family. Its structure mirrors the family itself: a landing page explaining TLC Base, a mini-index per hub, then the guides inside it. Access is gated twice — you need site:guides to enter, and the documented hub's own key to open its guides, so a user only ever sees instructions for hubs they can actually reach.

Level 1
Landing (index.php)
What TLC Base is, how sign-in and roles work, a card per hub.
Level 2
Hub mini-index
guides/<hub>/ — a card per guide in that hub.
Level 3
The guide
A scrollable page of numbered steps, one screenshot each.
Guides for Staffbase
Your home page
News, quick links and what is coming up.
guides/staff/home
News
Browse stories and open the full article.
guides/staff/news
Events
Calendar or list view.
guides/staff/events
Resource Library
Find, open and download learning materials.
guides/staff/library
The section menu
Linked from the home-page guide rather than shown as its own card.
guides/staff/menu
Guides for the other hubs
Knowledge · finding articles
Browse by category or search.
guides/knowledge/browse
Knowledge · reading an article
How to tell you are on the current approved version.
guides/knowledge/article
Admin · posting news
Blank form to live article.
guides/admin/news
Admin · managing users
One at a time, or by CSV import.
guides/admin/users
Admin · forms & records
Folder them, upload files, download a set as a ZIP.
guides/admin/forms
Quality · running an audit
Template to recorded findings.
guides/quality/audits
Quality · tracking actions
Findings become actions with an owner and a due date.
guides/quality/actions
Across every hub
The top bar
The masthead and the cross-site launcher.
guides/common/topbar
Your account menu
The avatar dropdown and where each item goes.
guides/common/account
Your profile
Kept on TLC Base, reached from anywhere.
guides/common/profile

Quality Hub

Audits, findings and actions.
qualityhub/ quality.tlcbase.org site:quality Local folder is empty

Registered in the SSO site list, present in the launcher, and already documented in the Guides Hub — but the local qualityhub/ folder has no files in it, so the map below is the intended shape taken from the guides, not from code on disk.

Start
From a template
Pick the audit template to run.
Work
Through the checks
Record a finding against each.
Convert
Finding → action
Give it an owner and a due date.
Close
Track to done
The action list is the live picture.
Intended sections
Running an audit
Start from a template, work the checks, record findings.
(documented in guides/quality/audits)
Tracking actions
Findings become owned, dated actions, tracked to done.
(documented in guides/quality/actions)

What they share

Two databases, four apps

TLC Base, Staffbase, AdminHub and the Knowledge Hub all read and write tlcstaffnet and tlc_holiday. One dump covers all four, which is why a schema change has to be thought about four times. tlc_holiday is also the shared auth database — it holds sso_sessions.

One chrome

The masthead, cross-site launcher, account dropdown and section subnav started on Staffbase and were ported outwards. AdminHub's assets/style.css and its ah-* classes are the reference copy; the Guides Hub and Enrolment Hub both say so in their own comments.

One access-key per site

The site-key doubles as the RBAC key: site:staff, site:knowledge, site:admin, site:quality, site:guides. A role grants it, the subdomain checks it, and the launcher only draws icons for keys the user actually holds.

Two outsiders in the launcher

site:safeguarding points at staffportal.360safeguarding.io and site:impact at impactmis.org.uk. Both sit in the launcher and are gated like the rest, but they are external systems, not SSO subdomains.