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

# Float

> Resource scheduling — accounts & projects

<Tabs>
  <Tab title="Overview">
    Connect Float with an API key to sync login-enabled team accounts and projects, and run access reviews. Read-only.

    <Info>
      **Read-only access.** DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
    </Info>

    <Note>
      DSALTA collects this integration's data when you connect it — you can refresh it at any time with **Sync from integrations** on the **Integrations** page. The compliance checks below re-run once a day at 02:00 America/New\_York.
    </Note>

    ## What DSALTA reads

    DSALTA reads your Float accounts — name, email address, role, active status and the account's creation date — which appear on your **Access** page; and your Float projects, which appear on your **Inventory** page carrying each project's code and whether it is active. Access is built from Float's login-enabled accounts, so scheduled resources that cannot sign in to Float — placeholders and contractors — are left out.

    It calls these Float endpoints:

    * `/v3/accounts`
    * `/v3/projects`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Float environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="Someone who appears in Float is missing from the Access page">
        Check whether they are an account or only a scheduled resource. The Access page lists Float accounts — the people who can sign in — so a resource you schedule work for but who has no Float login does not appear.
      </Accordion>

      <Accordion title="The connection fails to validate">
        An invalid, revoked or truncated API key. Float shows the full key exactly once, so a partial copy is the common cause.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        Open **Integrations** in the DSALTA sidebar, stay on the **Connected** tab, and click **Manage** on the integration's card. Open the **Status** tab: it shows either **Connected and working properly** or **Connection issues detected**.

        Use the **Status** tab, not **Overview** — Overview always reports **Connected** regardless of the real state.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        On an integration-powered check, **Failed** normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to **Source Data**, and read the result code: **403** is a missing permission, **428** is a setting DSALTA still needs, **500** is a failure on DSALTA's side.

        A real compliance gap shows **207** and leaves the test looking **Completed**. See [Understanding Test Results](/guides/data-library/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        Compliance checks re-run once a day at 02:00 America/New\_York. To refresh sooner, open **Integrations → Connected** and click **Sync from integrations** at the top right — it refreshes every connected integration at once.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **Disconnecting is destructive and cannot be undone.** DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see [Integration errors](/troubleshooting/integration-errors).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        That is expected. **Configure scope** is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    A Float API key, entered in Nango's secure connect window. Read-only.

    **Before you begin**

    * A Float account with the **Account Owner** or **Admin** role — only those roles can generate API keys.
    * Somewhere safe to hold the key between generating it and pasting it. Float shows the full key only once.

    You will need:

    | Field       | Where to find it                                | Example                            |
    | ----------- | ----------------------------------------------- | ---------------------------------- |
    | **API key** | Float → **Admin Settings → Integrations → API** | `Shown once, when you generate it` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Float**, and click **Connect** to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
      </Step>

      <Step title="Generate a Float API key">
        In Float, go to **Admin Settings → Integrations → API**, and generate a new personal access token.

        <Note>
          Only Account Owners and Admins can generate API keys. If that screen is not available to you, ask an Account Owner or Admin to generate the key.
        </Note>

        <img src="https://mintcdn.com/dsalta/50UUP7lNdp3gnRd3/images/integrations/float/01-team-settings-api-key.png?fit=max&auto=format&n=50UUP7lNdp3gnRd3&q=85&s=237e41b7a922a648989832c0ee461664" alt="Float's Team settings Integrations page, Connect to anything section, showing the API Key row with its Regenerate button and the key field" style={{maxWidth:"720px",width:"100%",borderRadius:"8px"}} width="1100" height="474" data-path="images/integrations/float/01-team-settings-api-key.png" />
      </Step>

      <Step title="Copy the key immediately">
        Float only shows the full key once. Copy it somewhere safe — you will paste it into the next step.

        <Warning>
          **This key is a live credential.** Anyone holding it can read your Float accounts and projects for as long as it exists. Keep it out of tickets, chat messages and shared documents, and delete your copy once the connection is saved. If it does leak, revoke the key in Float and connect again with a new one.
        </Warning>
      </Step>

      <Step title="Connect Float">
        Enter your Float credentials in the secure Nango window. DSALTA never stores them directly — it keeps only a connection reference.

        <Info>
          DSALTA only reads data — accounts and projects — and never modifies your Float schedule.
        </Info>

        <img src="https://mintcdn.com/dsalta/50UUP7lNdp3gnRd3/images/integrations/float/02-connect-window.png?fit=max&auto=format&n=50UUP7lNdp3gnRd3&q=85&s=0cf25d722b7c0b4a8bdb88d615c86a17" alt="The Link Float Account window with its API Key field and Connect button" style={{maxWidth:"720px",width:"100%",borderRadius:"8px"}} width="500" height="767" data-path="images/integrations/float/02-connect-window.png" />
      </Step>
    </Steps>

    <Check>
      DSALTA validates the credential when you finish the connect window, by requesting a single record from `/v3/accounts` through the Nango proxy. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync.
    </Check>

    <Warning>
      **If the connection is rejected.** An invalid, revoked or truncated API key — Float shows the key once, so a partial copy is the usual cause.

      The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages).
    </Warning>
  </Tab>

  <Tab title="Automated checks">
    Each check below re-runs once a day, at 02:00 America/New\_York, while this integration is connected. Click any check for step-by-step remediation guidance.

    | Check                                                                                                                | Severity | What it verifies                                                                                  |
    | -------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------- |
    | [User access to Critical System should be valid](/integrations/float/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with a login-enabled Float account is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/float/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Float access.                              |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                                |
    | ------- | ----------------------------------------------------------------------------------- |
    | Setup   | [Float: access rights](https://support.float.com/en/articles/5215287-access-rights) |
    | General | [Float website](https://float.com)                                                  |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)             |
  </Tab>
</Tabs>