This page is for customer and partner organizations: people who run learning programs, configure simulations, and support learners. It stays at the product and policy level. It does not describe hostnames, ports, secrets, or how to self-host the platform.

​
What JobSim is

An AI-powered workplace simulation: learners use a chat-style workspace with tasks, channels, and AI characters. Each organization has its own members, branding (where enabled), and simulation configuration that shapes difficulty, pacing, privacy behavior, and realism.

​
Who does what in your tenant

Role names and which screens each role can use are summarized in Roles and product surfaces. In short:
  • Learners focus on chat, tasks, and their personal progress views.
  • Organization administrators (admin) configure simulation settings, characters, tasks, and related options for your organization.
  • HR (hr) can help with people workflows in the product; full simulation administration is tied to the admin role—see the roles page for the exact split.
  • Platform support (super_admin) is for the team operating JobSim across customers, not something most orgs assign internally.
Your JobSim host can confirm which roles your contract uses and how users are provisioned.

​
Where to configure the simulation

If you administer one organization:
  1. Organization admin manual — Scope, safe practices, and pointers to full reference material.
  2. Simulation settings — full catalog — Top-level parameters, defaults, and learner impact.
  3. Simulation policy paths — Fine-grained simulation_policy options (routing, privacy, memory, and similar).
  4. Parameter documentation standard — Template for pilots or formal signoff when you need more than the catalog tables.

​
What this site does not publish here

To avoid exposing information that could help attackers or that belongs in private runbooks:
  • Default ports, internal URLs, and infrastructure topology for deployments.
  • Credential names, rotation procedures, or secret store layouts for production.
  • Host-specific hardening checklists (those live with your platform and security teams).
Technical contributors building or integrating JobSim should use For developers and the Architecture / Deployment sections together with your organization’s internal deployment guide.

​
API reference on this site

The API reference tab uses a redacted OpenAPI file: long descriptions that discuss credentials, mail, or similar topics are shortened, and examples are removed so the doc site stays closer to an SDK-style contract. Your provider can supply a full export under NDA or contract if you need it.

​
Getting help

Use the channels your JobSim provider gives you (support portal, CSM, or engineering). For API integration questions, your provider may share partner-only material beyond this public documentation.