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

# Canva setup

Configview reads your Canva organization (the design platform) through the **Canva Admin API** (`https://api.canva.com/admin/v1`), using an **Admin API client** (client ID and secret) created by a Canva administrator. Configview only sends `GET` requests. It never creates, changes or removes anything in Canva.

You will end up with **2 required secrets** (`CANVA_CLIENT_ID` and `CANVA_CLIENT_SECRET`) in Configview when setup is complete.

> **Scope of this integration today.** Configview answers "who can design and publish under our brand, who administers Canva, who has gone quiet, which invitations are still open, and what did people do": every member with role (admin, brand designer, member), last active date and SSO link, teams and their members, groups and their members, pending invitations, and the audit log (actor, action, outcome, target, IP address). It does **not** read designs, folders, brand kits, templates, files or download links.

> **Plan requirement.** The Admin API (and the audit log) is available on **Canva Enterprise**, Canva Districts and Canva Campus only. The Admin API is a **preview** and may change. Canva Teams organizations cannot create an Admin API client, so this integration does not apply to them.

***

## What you need

* A Canva Enterprise (or Districts / Campus) organization and an **organization admin**
* Permission to create an Admin API client under organization settings

***

## Step 1: Open the Canva page in Configview

Open Configview in a second browser tab and leave it open:

`https://{companyname}.configview.com/admin/integrations/canva`

***

## Step 2: Create the Admin API client

1. In Canva open **Admin settings** and find the **Admin API** (developer) section, then **Create client**. Canva's guide: [https://www.canva.com/help/set-up-admin-api/](https://www.canva.com/help/set-up-admin-api/)
2. Name it, for example, `Configview (read-only)`
3. Tick **only these read scopes**: `admin:user:read`, `admin:team:read`, `admin:group:read`, `admin:auditevent:read`. Do **not** tick any `write` scope or `admin:organization:read` (not needed).
4. Generate the **client secret** and copy it now (shown once)
5. In the Configview tab paste the client ID into `CANVA_CLIENT_ID` and the secret into `CANVA_CLIENT_SECRET` under **Credentials** and save

Configview exchanges the client ID and secret for a short-lived access token (about 4 hours) at the start of every run. Nothing rotates and nothing needs to be re-authorised; revoking or deleting the client in Canva stops Configview.

***

## Step 3: Connect and verify

1. Click **Connect**. Configview creates its tables and schedules every collector at your default run time:

| Script | Notes |
| - | - |
| **Users** | Every member: email, name, role, locale, last active, SSO link. |
| **Teams / Team members** | Teams and who is in each, with their team role. |
| **Team invitations** | Pending invitations: email, role, expiry. |
| **Groups / Group members** | Groups inside each team and their members. |
| **Audit logs** | Audit events, kept as a growing history (first run reads 90 days). |

2. Click **Verify now**. The health check reads both secrets, exchanges them for a token and lists one page of teams.

If a check fails:

* **400 / 401 from the token endpoint.** The client ID or secret is wrong, or the client was deleted.
* **403.** The client does not have the scope that area needs, or the organization is not on an eligible plan.

***

## Data Tables

Snapshot tables have a `run_at` column and keep only the newest run. `canva_audit_logs` is a history: events are added, never removed.

| Table | Source | Key Columns |
| - | - | - |
| `canva_users` | `GET /admin/v1/users` | user\_id, email, role, last\_active\_at, sso\_linked |
| `canva_teams` | `GET /admin/v1/teams` | team\_id, name, created\_at, sso\_mapped |
| `canva_team_members` | `GET /admin/v1/teams/{teamId}/members` | team\_id, user\_id, role |
| `canva_team_invitations` | `GET /admin/v1/teams/{teamId}/invitations` | team\_id, email, role, expires\_at |
| `canva_groups` | `GET /admin/v1/teams/{teamId}/groups` | team\_id, group\_id, name, description |
| `canva_group_members` | `GET /admin/v1/teams/{teamId}/groups/{groupId}/members` | team\_id, group\_id, user\_id, role |
| `canva_audit_logs` | `GET /admin/v1/audit-events` | event\_id, event\_at, action, outcome, actor\_email, actor\_client\_name, target\_type, ip\_address |

***

## Things worth knowing

**Roles.** Users carry `admin`, `brand_designer` or `member`; inside a team the roles are `admin`, `designer` or `member`; inside a group `admin` or `member`. Team and group member tables hold a user id only, so join them to `canva_users.user_id` for the email.

**Admin API clients in the audit log.** Actions performed through an Admin API client are logged under the client (client id and name), not under the admin who created it. Configview's own reads are listed there too.

**Audit log.** Canva retains audit events for a limited time (the help center states 90 days), and the Admin API audit feed is in preview. Configview stores action, outcome, actor, target type and id, and IP address. Session, device id, request id and event payloads are not stored. Time filters use ingestion time, so Configview re-reads the last day on every run and ignores duplicates.

**SSO.** `sso_linked` is true when Canva holds a SAML identity for the user. The SAML NameID itself is not stored.

**Rate limit.** Canva allows 1,000 requests per minute per client on list endpoints and 100 per minute on audit events. Configview paces itself well inside both and waits when Canva answers 429. Team members, invitations and groups need one request per team, and group members one per group.

## Known gaps

* The Admin API does not list third-party apps or integrations connected to the organization, brand kits, seat or plan counts, or SSO and security settings
* Pending invitation links are never returned or stored
* The Canva **Connect API** (designs and folders) is per-user OAuth and is not used; it is not a governance source
* The **SCIM API** (bearer token, requires SSO) is not used; it would add only an active/deprovisioned flag

## What isn't collected

* Designs, folders, brand kits, templates, files and download links
* Invitation URLs
* SAML NameIDs, sessions and device ids
* Client secrets and access tokens


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.