Vianordis
--:--:-- UTCVianordis / SUPPORT
education

Paideia

Coming soon

Paideia is a learning platform for adult, corporate, partner, and customer education. Teams can author courses, manage enrolment, deliver media and live sessions, run assessments, issue certificates, track skills, and govern AI-assisted learning work.

Release-readiness guide

Paideia pre-release readiness manual

Prepare governance, learning content, roles, and acceptance evidence for the Paideia adult and corporate learning platform before release.

Manual
Version 1.0
Product
Paideia 0.1.0 pre-release
Verified
July 15, 2026
Language
English · Source
Owner
Paideia learning product, compliance, and support
Source
paideia · 9f5e7b7
Review cycle
90 days
Start here

Audience, scope, and prerequisites

This is a release-readiness guide for Paideia authoring, catalog, enrolment, delivery, assessment, certificates, skills, imported content, webinars, analytics, and governance. It is not production learner guidance or authorization to publish a live academy.

Who this is for

  • Learning owners and course authors
  • Academy and compliance administrators
  • Privacy, security, and release testers
  • Learner representatives

Before you sign in

  • A formal preview invitation and non-production tenant
  • Synthetic learners and approved test content
  • Named learning, privacy, security, accessibility, and support owners
  • Documented completion, assessment, certificate, retention, AI, SCORM, LTI, and webinar policies
Access model

Roles and responsibilities

RoleAccessResponsibilities
Learner testerPreview assigned catalog, course, lesson, quiz, webinar, and certificate flows.
  • Use synthetic identity and results
  • Report accessibility and completion issues
AuthorPreview course structure, content, assessment, skills, packages, and sessions.
  • Verify rights and accessibility
  • Keep publication human-controlled
Academy or compliance administratorPreview enrolment, reporting, roles, governance, and elevated operations.
  • Use live elevation only when required
  • Verify privacy and audit evidence
Workspace map

Navigation

Catalog

/catalog

Preview discoverable learning and enrolment.

Authoring

/authoring

Preview courses, modules, lessons, content, quizzes, skills, packages, and webinars.

Dashboard

/dashboard

Preview assigned learning and progress.

Certificates

/certificates

Preview issued certificate records and verification.

Analytics

/analytics

Preview learner, academy, and compliance reporting.

Chapter 01

Prepare a governed learning preview

Establish content rights, human accountability, privacy, accessibility, and expected learning outcomes before testing delivery.

Procedure 1.1

Confirm preview authorization and governance

Define what may be tested, by whom, with which data and content, and under which stop conditions.

  1. 1
    Record the release notice

    Capture environment, version, available scope, known gaps, support path, and test window.

  2. 2
    Verify identities and tenant

    Confirm learner, author, and administrator scope and test denied access.

  3. 3
    Approve test content

    Use synthetic learners and content with known rights, classifications, accessibility, and expected results.

  4. 4
    Set governance controls

    Keep AI disabled unless approved; define human review, audit, privacy, retention, and elevated-access rules.

  5. 5
    Set stop conditions

    Stop on cross-tenant access, unauthorized publication, real personal data, invalid certificates, or uncontrolled external launch.

Expected result

The preview has explicit scope, roles, synthetic inputs, accountable owners, governance settings, and stop conditions.

Procedure 1.2

Prepare an acceptance course

Build a compact test course that exercises content, assessment, completion, and accessibility without production publication.

  1. 1
    Define learning outcomes

    Write measurable outcomes, audience, prerequisites, completion rule, and expected evidence.

  2. 2
    Create the structure

    Prepare modules, lessons, text/media blocks, sequencing, and one accessible alternative for each medium.

  3. 3
    Add assessment

    Use synthetic questions, pass threshold, attempt rules, feedback, and known expected scores.

  4. 4
    Select optional integrations

    Include SCORM, LTI, webinar, or AI only when separately approved and safely isolated.

  5. 5
    Define expected records

    Specify enrolment, progress, completion, certificate, skill, analytics, audit, and notification outcomes.

Expected result

A rights-cleared, accessible, synthetic course has documented expected behavior for every tested capability.

Chapter 02

Run end-to-end acceptance

Use separate author and learner sessions and verify records, permissions, and human controls at every transition.

Procedure 2.1

Accept authoring through completion

Validate controlled publication, enrolment, learning, assessment, completion, and certificate evidence.

  1. 1
    Author the test course

    Create the prepared structure and verify preview, accessibility, metadata, and content ownership.

  2. 2
    Publish to the test audience

    Confirm only the synthetic tenant audience can discover or enrol and preserve the publication audit event.

  3. 3
    Enrol a learner tester

    Verify assigned and self-enrolment rules, duplicate handling, reminders, and denied access.

  4. 4
    Complete learning activities

    Exercise media, sequencing, resume, lesson completion, quiz attempts, feedback, and optional approved integrations.

  5. 5
    Verify outcome records

    Reconcile progress, score, completion, certificate, skills, analytics, notifications, and audit history with the expected ledger.

  6. 6
    Test correction and revocation

    Verify permitted changes, certificate verification, and how erroneous or withdrawn outcomes are handled.

Expected result

The synthetic learner journey is accessible, tenant-scoped, human-governed, auditable, and reconciled to expected outcomes.

Procedure 2.2

Record learning and compliance acceptance

Require evidence from functional, privacy, security, accessibility, and operational owners.

  1. 1
    Review functional evidence

    Assess authoring, publication, enrolment, delivery, assessment, completion, certificate, analytics, and recovery.

  2. 2
    Review governance evidence

    Assess tenant isolation, RLS, audit, privacy requests, AI controls, elevation, content rights, retention, and external integrations.

  3. 3
    Review accessibility and support

    Test keyboard and assistive use, captions/alternatives, localization, errors, performance, and diagnostics.

  4. 4
    Classify gaps and decide

    Record severity, owner, mitigation, retest, accepted scope, version, date, and production authorization status.

Expected result

A dated, multi-owner decision states whether the tested scope is accepted, conditional, or blocked and why.

Operating rules

Security and data handling

  • Use synthetic learner identities, results, certificates, skills, and analytics until production approval.
  • Verify FORCE RLS and role boundaries with negative cross-tenant tests.
  • Keep tenant AI disabled unless specifically approved; require human review for consequential AI output.
  • Upload only rights-cleared, malware-safe, accessible test media and packages.
  • Treat SCORM, LTI, webinar, notification, and certificate operations as external or consequential effects requiring explicit acceptance.
Current release

Known limitations

Read before relying on an unsupported workflow

These limits describe the source-pinned Paideia 0.1.0 pre-release scope and must be rechecked when the product changes.

  • Paideia is listed as coming soon and this manual does not authorize production learning or academy publication.
  • The source README describes its checked-in status as a provisioning/compliance foundation with further walking-skeleton work planned, even though later routes are present.
  • Route presence does not prove deployment, production configuration, integration readiness, accessibility, or operational SLA.
  • SCORM packages, LTI tools, webinars, AI, storage, notifications, and certificates each require separate security and operational acceptance.
  • Paideia serves adult, corporate, partner, and customer learning; school/SIS administration belongs to Omniscola.
Problem solving

Troubleshooting

You cannot sign in to Paideia

Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.

  1. Open the application from the approved portal and complete sign-in again.
  2. Confirm that the correct organizational identity and tenant are selected.
  3. If access is still denied, record the time and request an entitlement check from support.

A documented action or navigation item is not visible

Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.

  1. Confirm the role and prerequisites listed for the procedure.
  2. Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
  3. Ask the product owner whether the feature is enabled for the tenant before reporting a defect.

A saved change or background operation is not visible

Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.

  1. Review inline validation, status indicators, filters, and the selected tenant or workspace.
  2. Refresh once and search for the item by its stable name or identifier.
  3. Do not repeat irreversible or externally visible actions until the original operation status is known.

Completion, score, certificate, skill, or analytics records disagree

Likely cause: Completion rules, attempt state, event processing, filters, integration callbacks, or preview implementation differ from the expected ledger.

  1. Stop official interpretation and preserve sanitized course, enrolment, attempt, and certificate identifiers.
  2. Compare the learner activity and audit sequence with the expected rule set.
  3. Raise a release-blocking defect before repeating or manually altering records.
Escalation

Contact support

Contact support when

  • A repeatable Paideia error blocks an approved workflow
  • Expected data, permissions, or tenant boundaries appear incorrect
  • A security, privacy, compliance, or data-loss concern is suspected
  • A learner sees another tenant's content, results, or records
  • A course publishes or an external integration launches without intended human control
  • Completion, assessment, certificate, skill, or compliance evidence is inconsistent

Include

  • The page, action, and expected result
  • The exact error text and time of occurrence, including time zone
  • Your tenant, role, browser, and a sanitized record or item identifier
  • Whether the problem can be reproduced and which troubleshooting steps were tried

Never include

  • Passwords, access tokens, API keys, recovery codes, or session cookies
  • Unredacted personal, health, financial, or other regulated data
  • Private encryption keys or complete confidential documents unless an approved channel is provided
Contact support