sitemap.xml llms.txt
Skip to main content

Epicenter Release 6.2

Release date: November 14, 2026

Overview​

This release adds project-level team access, so that a team member can be limited to individual projects, a new project SSO settings page with Canvas LTI 1.3 configuration, and a workshop user list export. It also improves Canvas roster imports, tightens session security, and allows simulation models to keep long-running calls alive. On the administration side, this update rolls up the Epicenter Dashboard improvements from version 1.19.

Epicenter Administration New Features​

Project-Level Team Access​

  • Associate team members: Organization owners can invite or change a team member to the new Associate role. An Associate has no organization-wide access and can work only on the projects granted to them individually.
  • Grant access project by project: The Manage Team Member page has a new Project Access section. Owners can add a project, choose the member's role in it (Author or Customer Support), and remove access later.
  • Focused experience for project members: Associates can see only the projects they have been granted access to. Within a project, the available pages and actions reflect their roles in that project, including workshop and user management. A grant to an inactive project is shown as disabled.

Project SSO Settings​

  • New SSO tab in Project Settings: Team projects in organizations on the Large, Extra Large, and Enterprise plans have a new SSO tab. The user creation, single sign-on file, and LMS Outcomes settings moved here from Administrative Settings.
  • Canvas LTI 1.3 configuration: The SSO tab includes a Canvas LTI 1.3 form for the Canvas Site URL, the Client ID from Canvas, and whether to create a workshop during single sign-on if it doesn't exist.

Workshop User Export​

  • Export List of Users: The workshop users page has a new Export List of Users link that downloads every member of the workshop as a .csv file, regardless of the page's current search, sort, or paging. The file uses the same columns as the user upload template. The password column is always blank.

Epicenter Administration Fixes and Improvements​

Organization User Management​

  • Number of logins restored: The organization Users table shows the # of Logins column again.

Pipeline/Git Integration​

  • Build pipeline pages refresh correctly: The pipeline run page and the History page no longer show a 404 error while waiting for a running pipeline to finish.
  • GitHub SSH addresses accepted: The repository URL field now accepts the address format GitHub displays (git@github.com:organization/repository.git), in addition to ssh:// URLs.
  • Clearer directory layout message: Generating keys for a project that does not use the Developer directory layout now explains the requirement.
  • More reliable integration actions: Removing an integration and running the initial pull no longer fail when the server version cannot be read.

Other Improvements​

  • Faster reads of long lists: Pages that read a complete list, such as the participant list for world assignment, make fewer server requests.
  • Miscellaneous: Updated third-party libraries to address security advisories.

Platform/API Improvements​

Security and Authentication​

  • Sessions end when account credentials change: Changing a team organization's shared secret or API key now invalidates the sessions that were issued for that organization.
  • Stricter session validation: Session tokens presented by external requests are validated more strictly, and non-expiring sessions are no longer accepted from outside the platform.
  • User lookup by project administrators: Administrators with an Author or Customer Support role, including those granted the role on a single project, can now look up a specific user by handle.

LTI and Canvas​

  • Import a single Canvas section: The LTI 1.3 user import accepts an optional sectionId. When supplied, only that section's members are imported, into the Epicenter group named {courseId}-{sectionId} unless a group key is given. This requires the custom field section_id=$Canvas.course.sectionIds in the Canvas tool configuration.
  • Organization filled in from Canvas: Groups created automatically during a Canvas LTI 1.3 launch now record the Canvas platform name as their organization.
  • Fixed repeated launch failures: Single sign-on launches could fail for up to 20 minutes after a group whose name contains special characters was deleted and recreated. Group lookup now uses the same name that is stored.

Projects and Models​

  • Keep long-running model calls alive: The Epicenter libraries for Python, JavaScript, and Julia models have a new refresh function. A proxy model can call it during a long-running operation to reset its inactivity timer, so the run is not stopped prematurely.
  • Node 16 minimum for JavaScript Proxy models: JavaScript Proxy models that previously ran on Node 14 now run on Node 16.

Other Improvements​

  • Group status events: Updating a group's status now publishes a status event on the group's push channel, so connected clients can react immediately.
  • Consensus without actions: Submitting to a consensus barrier no longer requires a list of actions.
  • Channel protocol in the v2 API: The v2 project API has a new channel endpoint that returns the project's push channel protocol.
  • PowerPoint generation: Text substitution falls back to document-level parameters when a slide-level value is missing or null.
  • Legacy group creation: Fixed an error when creating a group through the legacy user group API.
  • Epicenter Encyclopedia: Every v3 REST API endpoint now has a summary and a description in the Epicenter Encyclopedia.
  • Pipeline improvements: A pipeline execution can override individual operations of the saved pipeline. Git operations accept GitHub's git@host:organization/repository.git address format and git:// URLs, and fetch from the repository only when needed. The Git status request for a project that has never been cloned now returns an empty response instead of an error.
  • Miscellaneous: Improvements to site performance, stability, and security.