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

# Offboarded users should not have active access

> Checks that offboarded employees no longer have active Granola access.

Checks that offboarded employees no longer have active Granola access.

## About

When you connect Granola to DSALTA, the platform records the connected Granola account using read-only access. On every sync DSALTA matches the account with active Granola access to your **People** page by email and flags it when the matched person is offboarded — terminated or in offboarding — but still has active access.

<Note>
  Granola does not provide a team member list, so the Access page shows a single row for the connected account. If the account's email does not match a person in your directory, this match may not resolve automatically — review the account that can sign in to Granola against your list of offboarded employees.
</Note>

## Why This Matters

When someone leaves and their access is not revoked, their account becomes an unmonitored door into your systems — and a meeting-notes tool can hold sensitive conversation content. Timely access removal on termination is explicitly required by SOC 2, ISO 27001, and GDPR.

## How to Fix

**Before you begin**

* Identify offboarded employees by cross-referencing your HRMS (or the DSALTA **People** module) with the account that can sign in to Granola.

**Remove access for offboarded users**

1. In **Granola → Settings**, remove access for any account that has been offboarded.
2. In DSALTA, open **People** and confirm offboarded employees are marked terminated.

Once no offboarded employee retains active Granola access, DSALTA retrieves the change on the next sync and sets the check status to **Passing**.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    This check runs automatically every 24 hours while the Granola integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="What happens if it keeps failing?">
    A failing check appears in your **Data Library → Tests** dashboard. Work through the steps above; once offboarded accounts no longer have access, the status updates automatically on the next sync.
  </Accordion>

  <Accordion title="Can I exclude this check?">
    Yes. If it does not apply to your environment, mark it as **Not Applicable** with a justification. The exclusion is documented for auditors.
  </Accordion>

  <Accordion title="Does DSALTA change my Granola configuration?">
    No. DSALTA uses **read-only access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Granola.
  </Accordion>
</AccordionGroup>