Enrollment and payment
A learner needs a signed-in account and a valid paid enrollment or organization seat before certificate-track access opens.
Certificate readiness
TCAA separates public learning from verified certification. The first paid pathway now has a controlled launch structure: secure enrollment, learner-only access, final assessment, capstone review, admin approval, and public certificate verification.
Trust gates
A learner needs a signed-in account and a valid paid enrollment or organization seat before certificate-track access opens.
Lessons, materials, notes, bookmarks, and progress are connected to the correct learner account.
The certification pathway uses a published final assessment with a defined pass threshold, limited attempts, and server-side scoring.
Learners submit practical work against an approved rubric so the certificate reflects applied judgment, not only quiz completion.
A reviewer confirms completion evidence and approves or rejects certificate issue before any credential is created.
Certificate ID, learner name, course title, issue date, and status come from protected server-side records.
Visitors can verify a certificate code without seeing private learner, payment, or admin data. Open verifier.
Name corrections, mistaken issue, misconduct, expiry, and revoked certificates remain admin-controlled.
Plain boundary
Free learning records are for personal evidence and orientation. They are not paid certificates, accreditation, university credit, or employment guarantees. Paid TCAA certificates require the controlled certification pathway: enrollment, completion, assessment, capstone review, admin approval, and verification.