> ## Documentation Index
> Fetch the complete documentation index at: https://docs.k16solutions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure a Brightspace integration

> Prepare Brightspace application access and create a K16 connection.

A Brightspace integration combines an approved Brightspace account with application access issued by Brightspace.

## Prepare Brightspace

Ask your Brightspace administrator to:

1. Identify the account that owns or authorizes the Brightspace application.
2. Confirm that the application and account can access the required organizational units.
3. Provide the approved application and user identifiers through a secure channel.
4. Identify a course template or semester only when your destination workflow requires it.

The Brightspace account associated with the application must match the account represented by the user access values. A mismatch can cause validation to fail.

## Create the integration

<Steps>
  <Step title="Select Brightspace">
    Open **Settings** > **Integrations** > **New integration**. Select **LMS**, then **Brightspace**.
  </Step>

  <Step title="Name and direct the connection">
    Enter a **Friendly name**. Choose **Source** to pull from Brightspace or **Destination** to push to it.
  </Step>

  <Step title="Enter provider settings">
    Complete **Integration URL**, **App ID**, **App Key**, **User ID**, and **User Key**. Enter **Course Template ID** or **Semester ID** only when your workflow calls for them.
  </Step>

  <Step title="Validate and create">
    Select **Validate & continue**. Brightspace does not currently run live credential validation in the creation wizard, so review every value carefully. Then select **Create integration**.
  </Step>
</Steps>

<Warning>
  Treat application keys and user keys as protected values. Do not include them in screenshots,
  copied diagnostics, or support messages.
</Warning>

## Resolve common Brightspace failures

* Confirm that **Integration URL** is the Brightspace base URL.
* Confirm that the application and user access values belong to the same Brightspace account context.
* Ask the Brightspace administrator to verify application registration and organizational-unit scope.
* Confirm optional destination IDs before a sync workflow uses them.

After creation, review [Status and lifecycle](/administration/integrations/status-and-lifecycle).