> ## 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.

# FloQast

<Note>
  This integration is in Beta. Contact your Lumos team to have it enabled for your domain.
</Note>

## After this article

You'll be able to connect FloQast to Lumos and manage it alongside your other integrations.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Accounts | Account | Yes | No | FloQast user accounts are read into Lumos |
| Entitlements | Permission | Yes | No | Entitlements and the accounts holding them are read into Lumos |

### Activity Tracking

Status: Supported. Lumos reads last-activity data for FloQast accounts.

## Required plan and roles

Connect FloQast with credentials generated in your FloQast account. Create them as a FloQast administrator, then enter them on the connector card in Lumos.

## Read-only access vs provisioning

**Is read-only possible?** Yes, and it is the only mode. The FloQast connector reads accounts, entitlements, their associations and last-activity data. It has no provisioning or deprovisioning ability, so the connection can never write back to FloQast.

**What read-only requires.** A FloQast API key, plus an account identifier for this connection and the region your FloQast instance is hosted in. Managers and Admins in FloQast can open the **API Keys** tab in **Admin Settings** to view existing keys and create a new one. Follow the steps below once you have the key.

**Watch out for.** Provisioning is not available for FloQast, so do not build an offboarding or access-request workflow that expects Lumos to remove or grant FloQast access. Access Reviews and visibility work, and any revocation has to be done in FloQast itself. Two other points on the credential. If your key is held by a Sys Admin user, an Admin has to turn on the setting on the API Keys page that allows Sys Admin users access, otherwise the key will not authenticate. And the region you pick has to match where your FloQast instance actually runs, because it decides which regional endpoint Lumos calls, and a mismatch will fail the connection rather than return partial data.

## Instructions

**Phase 1: Prepare FloQast credentials**

1. Log in to FloQast as an administrator.
2. Generate API Key
   1. Managers and Admins in FloQast can access the API Keys settings tab in their Admin Settings. Once there, they can see any previously created API Keys and create new Keys. Admins must toggle a setting on this page to allow Sys Admin users access.

**Phase 2: Connect in Lumos**

1. Find the FloQast card in your Lumos integrations (reconnect an existing card or add a new one).
2. Enter your FloQast credentials.
3. Click **Connect**.

## Troubleshooting

**Connection fails.** Confirm the credentials are current and were created by a FloQast administrator, then reconnect.