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

# Fireflies

> Meeting notes — users & access

<Tabs>
  <Tab title="Overview">
    Connect Fireflies with an API key to sync workspace users 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 the Fireflies workspace roster — each user's name, email address, user id and whether they are an admin, recorded as the role **Admin** or **Member** — which appears on your **Access** page. Meeting transcripts, recordings and notes are never read, and no other DSALTA page is populated from Fireflies. The Fireflies user record carries no status or MFA field, so every Access row is recorded as **Active** with MFA `Unknown`.

    It calls these Fireflies endpoints:

    * `POST /graphql` — `{ user { name email } }`, used to confirm the credential
    * `POST /graphql` — `{ users { name email user_id is_admin } }`, used to fill the **Access** page

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

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The Access page shows fewer people than I expect">
        A Fireflies API key is issued per user, so the roster DSALTA sees is the one that key can see. Connect with a key from an account that sees the full workspace roster.
      </Accordion>

      <Accordion title="The connection fails to validate">
        An invalid or regenerated API key. Regenerating the key in Fireflies invalidates the one DSALTA holds — copy the current key and connect again.
      </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 Fireflies API key, entered in Nango's secure connect window. Read-only.

    **Before you begin**

    * A Fireflies account — a free account works, no paid plan is required
    * Access to the **Fireflies API** settings page for that account

    You will need:

    | Field       | Where to find it    | Example             |
    | ----------- | ------------------- | ------------------- |
    | **API key** | See the steps below | `Fireflies API key` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Fireflies**, 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="Open Fireflies API settings">
        In Fireflies, click your profile picture (top-right) → **Integrations** → **Fireflies API**. A free Fireflies account works; no paid plan is required.

        <Tip>
          The same developer key is also reachable from the account's **Settings → Developer Settings → API Key** screen — one key, two routes through the app. Use whichever path your version of the Fireflies UI shows.
        </Tip>
      </Step>

      <Step title="Copy your API key">
        Copy the API key shown on that page. You'll paste it in the next step.

        <Warning>
          **This key is a live credential.** Anyone holding it can query your Fireflies workspace — including meeting transcripts, which DSALTA itself never reads. Keep it out of chat messages, tickets and shared documents, and delete your copy once the connection is saved. If it does leak, regenerate the key in Fireflies and connect again.
        </Warning>
      </Step>

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

        DSALTA reads the workspace roster and nothing else. It never opens a meeting, recording, note or transcript.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the credential when you finish the connect window. 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 API key, a key that was regenerated after you copied it, or a key that was never fully copied.

      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/fireflies/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Fireflies access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/fireflies/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Fireflies access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                    |
    | ------- | ----------------------------------------------------------------------- |
    | Setup   | [Fireflies API documentation](https://docs.fireflies.ai/)               |
    | General | [Fireflies website](https://fireflies.ai)                               |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages) |
  </Tab>
</Tabs>