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

# Scopes

The `scope` parameter specifies the types of access that your app needs for a user's account. The list of possible scopes used in the Canva REST APIs are shown below:

<table>
  <thead>
    <tr>
      <th>Scope</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>`asset:read`</td>
      <td>View the metadata for the user's assets, such as uploaded images.</td>
    </tr>

    <tr>
      <td>`asset:write`</td>
      <td>Upload, update, or delete assets on the user's behalf.</td>
    </tr>

    <tr>
      <td>`brandtemplate:content:read`</td>
      <td>Read the content of the brand templates associated with the user's brand.</td>
    </tr>

    <tr>
      <td>`brandtemplate:content:write`</td>
      <td>Publish brand templates associated with the user's brand.</td>
    </tr>

    <tr>
      <td>`brandtemplate:meta:read`</td>
      <td>View the metadata of the brand templates associated with the user's brand.</td>
    </tr>

    <tr>
      <td>`collaboration:event`</td>
      <td>Receive webhook notifications about events relevant to the user.</td>
    </tr>

    <tr>
      <td>`comment:read`</td>
      <td>View the comments on the user's designs, and the associated metadata.</td>
    </tr>

    <tr>
      <td>`comment:write`</td>
      <td>Create comments and replies on the user's designs.</td>
    </tr>

    <tr>
      <td>`design:content:read`</td>
      <td>View the contents of the user's designs.</td>
    </tr>

    <tr>
      <td>`design:content:write`</td>
      <td>Create designs on the user's behalf.</td>
    </tr>

    <tr>
      <td>`design:meta:read`</td>
      <td>View the metadata of the user's designs.</td>
    </tr>

    <tr>
      <td>`email`</td>
      <td>Read user email address through OIDC.</td>
    </tr>

    <tr>
      <td>`folder:permission:write`</td>
      <td>Set, update, or remove permissions assigned to the user's folders.</td>
    </tr>

    <tr>
      <td>`folder:read`</td>
      <td>View the metadata and contents of the user's folders, including their **Projects**
      folder.</td>
    </tr>

    <tr>
      <td>`folder:write`</td>
      <td>Add, move, or remove the user's folders. It also lets you edit folder metadata,
      such as the folder's name.</td>
    </tr>

    <tr>
      <td>`openid`</td>
      <td>Read user information through Open ID Connect (OIDC).</td>
    </tr>

    <tr>
      <td>`profile`</td>
      <td>Read user profile information through OIDC.</td>
    </tr>

    <tr>
      <td>`profile:read`</td>
      <td>Read a user's profile and account information.</td>
    </tr>
  </tbody>
</table>

For example, if you just require your app to read design metadata, you can use the `design:meta:read` scope. If you require your app to read designs, as well as write to any folder, you can use both the `design:meta:read` and the `folder:write` scopes.

<Note>
  When enabling and using scopes, you must be explicit.

  For example, the `asset:write` scope doesn't grant `asset:read` permissions. To get both read and write permissions for assets, you must enable both scopes for your app, and request both scopes during the authorization process.
</Note>