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

# Assembla

> Create an Assembla OAuth application so Voltai can read tickets from a space.

**You'll create:** an OAuth application on your Assembla account.

**We'll be able to read:** tickets in the space you nominate, limited to what the connecting user can see.

## Steps

<Steps>
  <Step title="Create the OAuth application">
    Sign in to [app.assembla.com](https://app.assembla.com/).

    Click your avatar in the top right → **Profile**, then open the **OAuth** tab.

    Click **Create new application** and fill in:

    * **Name**: `Voltai`
    * **Redirect URL**: the [redirect URI](/connectors/introduction#redirect-uri-used-by-every-connector)

    Save the application.
  </Step>

  <Step title="Copy the credentials">
    Open the application's **Edit** page. The **Client ID** and **Client Secret** are shown there.
  </Step>

  <Step title="Find the Space Wiki ID">
    Open the Assembla space you want connected — its URL looks like `https://app.assembla.com/spaces/<space-name>/...`.

    The **Space Wiki ID** is under **Space Admin → General → Identifiers**. If you cannot find it, send us the space slug and we will look it up.
  </Step>
</Steps>

## Send us

| Value           | Where to find it                                                 |
| --------------- | ---------------------------------------------------------------- |
| `client_id`     | OAuth application → Edit page                                    |
| `client_secret` | OAuth application → Edit page                                    |
| `space_id`      | The Space Wiki ID (a UUID-style string) for the space to connect |

## Things to know

* Assembla has **no per-app scope picker**. The token inherits the permissions of whoever connects, so make sure connecting users have at least **Read** access to the tickets you want surfaced.
* Assembla's API has no global ticket-search endpoint, so we page through recent tickets and filter on our side. Slightly slower results are expected behaviour, not a setup problem.