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

# Fastly

Fastly is a read-only integration that syncs users and roles to Lumos.

## After this article

You'll be able to connect Fastly to Lumos to sync users and their roles for visibility and Access Reviews.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | No | User account |
| Roles | Permission | Yes | No | Roles |

This integration is read-only, so it doesn't provision or deprovision accounts.

**Activity tracking:** Supported (last login only). The Fastly integration tracks the last login timestamp for users.

## Required plan and roles

* **Fastly plan:** Requires access to Fastly API
* **Authentication:** Lumos connects with a Fastly API token (User Token) scoped `global:read`. Create the token from a Fastly account that has access to the services you want to sync.
* **Account note:** be sure you're creating tokens for the right account. If you've been invited as a user on multiple accounts, switch to the appropriate account first.

## Read-only access vs provisioning

**Is read-only possible?** Yes, and it's the only mode. Fastly connects with a User Token scoped `global:read`, and the integration doesn't provision or deprovision accounts.

**What read-only requires.** A Fastly User Token created with **Scope** set to `global:read` and **Access** set to **All services**, generated from an account that has access to the services you want to sync. Follow the steps below to connect.

**Watch out for.** If you belong to more than one Fastly account, create the token while switched to the account you actually want to sync, since a token from the wrong account will connect but sync the wrong data. Unrecognized Fastly role values (for example Next-Gen WAF imported roles) can also fail the entire user listing.

## Instructions

**Phase 1: Create an API token in Fastly**

1. Log in to the Fastly web interface.
2. Go to **Account > API tokens > Personal tokens**.
3. Click **Create token**.
4. When prompted, enter your password to re-authenticate your permissions.
5. Fill out the fields:
   * **Name:** a descriptive name for the token
   * **Type:** User Token
   * **Scope:** `global:read`
   * **Access:** All services
   * **Expiration:** Never Expire (you can revoke the token at any time)
6. Click **Create Token**.
7. Copy the token.

**Phase 2: Connect in Lumos**

1. Click the Fastly card in your Lumos integrations (reconnect an existing card or add a new one).
2. Paste the API token into the **API Key** field.
3. Click **Connect**.

## API Endpoints Used

<Note>
  The API endpoints this integration uses are available to logged-in Lumos customers. [Log in](/login) to view them.
</Note>

## Troubleshooting

**Connection fails after pasting the token.** Confirm the token is a User Token with the `global:read` scope and **All services** access. If you belong to more than one Fastly account, make sure you created the token while switched to the account you want to sync.

**A user's roles don't sync and the user list is empty.** Fastly can return role values that the connector doesn't recognize, such as Next-Gen WAF imported roles (`ngwaf_observer_imported`, `ngwaf_owner_imported`). A single unexpected role value can fail the whole user listing. Reach out to Lumos support if you see this so the role handling can be extended.
