> ## 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 Canvas integration

> Prepare Canvas access and create a scoped Canvas connection in K16.

A Canvas integration uses an approved Canvas account to read or write data within the account scope you select.

## Prepare Canvas

Ask your Canvas administrator to:

1. Create or identify a dedicated account for the integration.
2. Assign a Canvas account role that covers the intended import, archive, restore, or sync workflow.
3. Apply the role at the root account or required subaccount scope.
4. Complete any provider-side account activation or policy acknowledgement.
5. Confirm the subaccount ID when you want to limit access.

<Note>
  Required Canvas permissions depend on whether K16 reads courses, restores content, or syncs
  content back to Canvas. Review the workflow with your K16 contact and Canvas administrator instead
  of copying a broad legacy permission list.
</Note>

## Create the integration

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

  <Step title="Name and direct the connection">
    Enter a **Friendly name**. Choose **Source** when K16 pulls from Canvas or **Destination** when K16 pushes to Canvas.
  </Step>

  <Step title="Enter Canvas settings">
    Enter the **Integration URL** and the approved account values. Add **Sub Account ID** when the connection must be scoped below the root account.
  </Step>

  <Step title="Validate and create">
    Select **Validate & continue**. Resolve URL, account, or scope issues, then select **Create integration**.
  </Step>
</Steps>

Use the normal Canvas base URL for **Integration URL**. Do not append an authentication-only path.

## Resolve common Canvas validation failures

| Failure                                 | What to check                                                                                 |
| --------------------------------------- | --------------------------------------------------------------------------------------------- |
| URL validation                          | Confirm the Canvas base URL and HTTPS scheme.                                                 |
| Account validation                      | Confirm the provider account is active and approved for API access.                           |
| Permission validation                   | Confirm the account role is applied at the same scope as **Sub Account ID**.                  |
| Root details or subaccount verification | Confirm the account can see the selected account hierarchy.                                   |
| Token generation                        | Ask the Canvas administrator to review the role's token-management access and account policy. |

If Canvas requires MFA for the account, see [MFA for integrations](/administration/integrations/mfa).

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