Skip to main content

2026 Release Notes

November 2026

Clearer LTI tool data in Blackboard Illuminate

Illuminate now shows data from your Learning Tools Interoperability (LTI) tools the way your institution organizes them. Each integration appears as one tool, with a readable name, an LTI tool type, and the LTI version it uses. Tool activity now matches each tool’s identifier, and the Learning Tools Adoption report shows the new names.

Nota

If you query CDM_LMS.TOOL or CDM_LMS.ACTIVITY directly, read Check your queries before your next refresh. Some of these changes return fewer or differently labeled rows without raising an error.

One row per LTI integration in CDM_LMS.TOOL

Until now, each placement of an LTI tool had its own row in CDM_LMS.TOOL, often with a different name each time. One integration with five placements appeared as five tools. With this release, placements that lead to the same tool count as one tool, and each integration has one row.

  • source_id is a single domain-level identifier per integration, in the form blti-domain;<id>. Placement identifiers such as resource/x-bb-bltiplacement-... and blti-placement-... no longer appear for LTI tools.

  • name is one domain-level name. It uses the display name your administrator sets when adding the tool to Blackboard LMS, and it always includes the URL the tool uses, even when no display name is set.

  • tool_type reads LTI Tool for LTI integrations, so you can filter for LTI tools directly. These rows were previously typed Content Handler or Application.

  • lti_version is a new field with the value 1.1 or 1.3, so you can tell LTI 1.3 tools apart from legacy LTI 1.1 tools.

The table below shows one integration with five placements, before and after the change. The values come from a Blackboard Blackboard LMStest environment, not a customer environment.

tabela 6.

Field

Before

After

source-id

The table below shows one integration with five placements, before and after the change. The values come from a Blackboard LMS test environment, not a customer environment.

blti-domain;8

name

Five names: Google Collaborative Document, Google Collab Cloud Document, Google document, Google LTI document, Google Integration 

Google Integration - tp (us.tp.bb-google-service.api.bb-fnds.com)

tool_type

Content Handler or Application

LTI Tool

lti_version

Not populated

1.3

Rows for this tool

5

1



Matching tool identifiers in CDM_LMS.ACTIVITY

The tool_source_id field in CDM_LMS.ACTIVITY now uses the same format as source_id in CDM_LMS.TOOL. New activity is recorded in the new format, and existing activity has been updated to the new format wherever possible.

The exception is activity on LTI tools that were entirely removed from Blackboard LMS. Those rows were not updated and keep their original tool_source_id value.

New LTI tool names in Illuminate reports

Illuminate reports that list LTI tools, including Learning Tools Adoption, now show the new tool names from CDM_LMS.TOOL wherever they are available. There are no other major changes to these reports. 

Because the name comes from the display name set in Blackboard LMS, administrators can make a tool easier to recognize in reports by giving it a clear display name when adding or editing it.

Check your queries

If you have your own queries or dashboards on these tables, these are the changes to review.

  1. source_id values change. Placement IDs are replaced by one blti-domain ID per integration. Filter on tool_type = 'LTI Tool', or update your queries to the new source IDs.

  2. Row counts drop. A query that counted placements now counts distinct tools. Recheck counts and joins, especially anything that reports tools used per course.

  3. tool_type is reclassified. LTI rows move out of Content Handler and Application into LTI Tool. A filter on the old two values keeps running but no longer returns LTI rows. Add 'LTI Tool' to the filter.

  4. Names change. Placement-specific names become one domain-level name. If you match on tool names, update those values.

  5. tool_source_id in activity changes. If you mapped placement IDs in CDM_LMS.ACTIVITY to tools yourself, you can now join tool_source_id to source_id in CDM_LMS.TOOL instead. Activity on tools removed from Blackboard LMS can still carry the older placement-style value, so allow for both formats if you report on historical activity for those tools.

There is nothing to fix for lti_version. It is a new field, and you can start using it right away.

Example queries

Three example queries for the new LTI data are available in the BBDN-BlackboardData-Queries repository on GitHub: LTI tool activity, LTI tools by version, and a count of LTI tools by version.

October 2026

Data Dictionary

The Data Dictionary has a redesigned layout that makes the Illuminate data models easier to browse. The new experience also adds sample data from your institution and the ability to search across all schemas with filters.

Browse by schema, table, or column

From the navigation bar, you can quickly access the Schemas and Entity Relationships.

Schemas

Browse the list of schemas to view all available canonical data models.

illuminate-data-dictionary-schemas-navbar.png

Tables

When you select a CDM, you can view all of its tables. Select a table.

illuminate-data-dictionary-CDM-tables.png

Each table has Columns, Sample Data, and Table Detail tabs.

Columns

From a table, select Columns. Then select a column to see its entry definition and technical specifications.

illuminate-data-dictionary-columns.png
Sample data

From a table, signed-in Administrators, Authors, or Developers can select Sample Data to view up to 100 example rows of their institution's own data. You can copy samples directly from the table. For longer description values, select the expand button and then copy the description from the window.

Nota

Loading sample data for the first time can take a few seconds.

illuminate-data-dictionary-sample-data.png
Table details

From a table, select Table Detail to view the definition, technical specifications, and entity relationships for the table.

illuminate-data-dictionary-entity-rels.png

Enhanced search

Using the new Search field in the navigation bar, you can search across all tables and columns at one time. Use the toggles to filter which types of items to include in the search.

illuminate-data-dictionary-search-screen.png

For a more granular search, you can use the search field found on each schema, table, or column page.

Dica

If you receive no results when searching by name, select Search descriptions too to search descriptions as well.

Tell us what you think

We'd love to hear what you think about the new Data Dictionary! Signed-in users can select the feedback button to rate the new experience and provide additional comments.

illuminate-feedback.png

July 2026

New Developer role for Snowflake access

Administrators can now assign a dedicated Developer role to technical users while keeping Illuminate's administration separate. This enables your data team to work directly with your institution’s data in Snowflake, while your administrators keep control of platform settings.

With this release:

  • A new Developer role can be assigned to any current or new user. It's intended for data analysts, SQL developers, and integration partners.

  • The Developer area is now fully dedicated to developer features, including Launch Snowflake to query institutional data and the Data Dictionary to explore the data models.

  • On the navigation bar, the Settings link was moved outside of the Developer area and it's only available to Administrators now. This keeps administration clearly separated from the Developer experience. 

  • The Developer role does not consume an Author or Viewer license. 

  • Roles are stackable. For example, a user who needs both data and administrative access can hold the Developer and Administrator roles at the same time. A Developer who also needs reports can be given the Viewer role.

To assign a developer role to a user, go to Settings and then select License management. Select Edit for a user, and then select Developer under User Roles. For more information, visit Use functions to restrict access to reports.

illuminate-RN-dev-role.png

February 2026

Manage user roles in Illuminate

Administrators can now assign roles to users in Illuminate Settings, eliminating the need to manage roles through SAML groups or the Blackboard Administrator Panel. This streamlines user management by reducing dependencies on external platforms and prevents operational bottlenecks.

Institutional authentication is still managed through Blackboard or SAML. After the initial connection to the identity provider, administrators can manage all users, roles, and permissions directly from Illuminate Settings.

Assign roles to an Illuminate user

To assign role permissions for a user, from Settings in Illuminate, select License management. Then, under Actions, select Edit for the user to update. On the Edit User page, select which roles to assign.

Image 1. Edit user page in Illuminate where you can assign roles and permissions

Roles-management.png

These are the roles available in Illuminate:

  • Administrators: Have full platform access, including settings, Snowflake access, and read access to all pre-built reports and data.

  • Authors (exclusive for Illuminate Premium): Can create custom reports, have Snowflake access, and by default can view all pre-built reports and data, with permissions configurable.

  • Viewers: Have read-only access to pre-built reports, with no data permissions assigned by default, ensuring data security.

Notes

  • If institutional authentication is already configured, no additional steps are required. 

  • Existing users currently listed in the user list will remain in place, and their roles will be reflected in Illuminate without requiring any additional configuration. 

  • Users who previously had roles configured in Blackboard or SAML but have never logged into Illuminate will not appear in the user list and will need to be created again. 

  • Users without any assigned roles can still log into Illuminate, but they will not have any permissions within the platform. These users do not occupy a licensed user seat, allowing administrators to manage license capacity efficiently.

Delete Illuminate users or remove their roles

In a recent release, we introduced the ability to delete Viewer users. Administrators can now delete other Administrators or Authors. Administrators can also remove roles from users to reassign them to other users.

Delete a user

From Settings in Illuminate, select License management. Then, under Actions, select Delete for the user to remove.

Image 1. The Delete option for removing users

delete-authors-and-admins.png

Nota

Because Authors can create and own custom report content, additional safeguards are in place to ensure data security. When you delete an Author with saved content, you can choose to transfer their content to another Author or to all Authors. If the content transfer fails, the deletion process stops automatically to prevent any data loss.

Image 2. Content transfer prompt for choosing where to transfer the deleted author's content.

Transfer-content.png

Notes

  • Once a user is deleted, they immediately lose access to the platform. This action cannot be undone.

  • Administrators cannot delete themselves or remove their own Administrator role.

Remove roles from an Administrator or Author

From Settings in Illuminate, select License management. Under Actions, select Edit for the user to update. On the Edit User page, clear the checkboxes for the roles to remove.

AI conversations data included in Blackboard Source Tables for Illuminate Premium

For customers with Illuminate Premium, data for AI Conversations is now included in the Blackboard source tables in Illuminate. The new data is available in the LEARN schema in Snowflake. This update is retroactive and includes historical AI Conversations data.

With this data, you can identify these items:

  • AI conversation’s name and type (Socratic or role play) 

  • Number of conversations per course 

  • Whether the AI conversation was created with AI Identify if the AI conversation is a test or formative 

  • Number of student messages in an AI conversation 

  • Texts of questions and answers

Image 1. Query to analyze AI Conversations in Snowflake

AI-conversations.png

New columns included in LEARN schema are:

Date (YYY-MM-DD)

Status

Entry

Source

Description

2026-2-15

Added

LEARN.QTI_ASI_DATA.DATA

Blackboard

Contains raw XML markup for assessment, section, item data

2026-2-15

Added

LEARN.QTI_RESULT_DATA.DATA

Blackboard

Contains raw XML markup for questions in assessments such as tests

January 2026 Release

Blackboard source tables available in Snowflake for Illuminate Premium clients in America region

Blackboard source tables are now available for Illuminate Premium clients hosted in the US AWS region, covering North, Central, and South America. This means Blackboard source tables are now deployed across all supported Illuminate regions.

Illuminate Premium includes 183 tables from Blackboard’s Open Database Schema. These source tables are available in Snowflake as views in the LEARN schema and refresh every 4 hours. Note: These tables are not documented in the data dictionary. Learn more about Illuminate Premium and Blackboard source tables included in Illuminate.

Image 1. A query with LEARN schema source tables in Snowflake.

schema_and_tables.png.jpg

Importante

If you have Illuminate Premium, these source tables are included in your current license with no additional setup required.

Nota

In some accounts, source tables will appear in the LEARN schema by the first week of February 2026 due to incremental delivery processes. 

America region migration to Multi-tenant architecture

We completed the migration of the Blackboard Canonical Data Model (CDM_LMS) to a multi-tenant deployment for institutions hosted in the US AWS region. This update provides a more reliable data connection method.

The US region includes institutions in North, Central, and South America. With this milestone, the multi-tenant migration is now complete across all regions supported by Illuminate.

You can check whether your instance is multi-tenant by viewing CDM_LMS in Snowflake. Multi-tenant instances have data organized in views while single-tenant instances have data organized in tables.

Key considerations:

  • Your Snowflake queries may take longer to load. 

  • If you are extracting data from Illuminate into Power BI, update to the latest version of the Power BI app that supports Snowflake views.

  • If you are using Looker Studio or Qlik, use SQL queries instead of the Wizard-based connection method.

Image 1: Query in Snowflake showing CDM_LMS views.

MT_migration.png

Multiple Snowflake Service Accounts for Premium

Snowflake Service Accounts in Illuminate enable secure machine-to-machine connections for extracting data from Illuminate to external tools, such as BI platforms for reporting or data warehouses.

Illuminate Core includes one Snowflake Service Account. Now, Illuminate Premium clients can request additional Snowflake Service Accounts by submitting a support ticket. Administrators can view all Service Accounts in Illuminate Settings under the Snowflake settings menu.

Multiple Service Accounts provide greater control, allowing administrators to assign dedicated accounts to specific teams or purposes and manage passwords and IP restrictions independently.

Learn more about Snowflake Service Accounts and how to apply IP address restrictions to them.

Image 1. Two Snowflake Service Accounts listed in Illuminate settings.

illuminate-BB-source-tables.png