Admin & Integration Documentation

Overview

Palatinum runs in the browser and on WebXR-compatible headsets. There is no server infrastructure for your institution to host, no clients to install on student devices. Integration is a one-day effort for a program with an existing LMS.

• LTI 1.3 for Canvas, Blackboard, Moodle, D2L Brightspace
• SAML 2.0 / OpenID Connect SSO for institutional authentication
• FERPA-compliant hosting with signed DPAs on request
• Cohort management + usage analytics API

Install

Deployment follows four steps:

1. Your admin receives a tenant URL at your-program.palatinum.app
2. Configure SSO (SAML or OIDC) against your IdP — Okta, Azure AD, Google Workspace all supported
3. Install the LTI 1.3 tool in your LMS and point it at the tenant
4. Add cohorts via the admin dashboard or synced from your LMS enrollment

SSO · SAML 2.0 / OIDC

Palatinum is both an SP-initiated and IdP-initiated SAML service provider. Metadata is served at:

https://your-program.palatinum.app/sso/saml/metadata.xml

The following attributes are required: email, givenName, surname, cohortId.

LTI 1.3

Palatinum ships as a deep-linkable LTI 1.3 tool. From any course in your LMS, faculty can embed a specific palace room or an entire curriculum.

Tool URL:       https://your-program.palatinum.app/lti/launch
JWKS URL:       https://your-program.palatinum.app/.well-known/jwks.json
Login Init URL: https://your-program.palatinum.app/lti/init
Redirect URIs:  https://your-program.palatinum.app/lti/callback

Cohorts

Students are grouped into cohorts for licensing, analytics, and curriculum assignment. Cohorts can be manually managed from the admin dashboard or synced automatically from your LMS enrollment via LTI Names and Role Provisioning Service (NRPS).

Analytics API

Per-cohort and per-student engagement data is available through a REST API, scoped to your tenant. Available on Program and Institution plans.

GET /api/v1/cohorts/{cohortId}/engagement
Authorization: Bearer <tenant-api-key>

{
  "cohortId": "step1-sp26",
  "students": 180,
  "rooms_visited_median": 42,
  "revisits_per_room_median": 11,
  "palace_hours_median": 18.4
}

FERPA

Palatinum is operated as a "school official" under FERPA with legitimate educational interest. Student data stays within the institution's tenant and is never used to train shared models. DPAs available on request — see the Security page.

Support

Starter: email support, 1 business day. Program: dedicated solutions engineer. Institution: named engineering + support contacts, 1-hour response SLA on priority incidents.