> ## 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 Cal.com access.

Checks that offboarded employees no longer have active Cal.com access.

## About

When you connect Cal.com to DSALTA, the platform syncs the connected account using read-only API access. On every sync DSALTA matches each user with active Cal.com access to your **People** directory by email and flags anyone whose employee record is terminated or offboarding but still has active access.

<Note>
  Because Cal.com's free plan is individual, the Access list is the connecting account rather than a full member roster, and this match may not resolve automatically. Review who can sign in to Cal.com against your list of offboarded employees.
</Note>

## Why This Matters

Offboarded employees must not retain access to the organization's Cal.com account. When someone leaves and their access is not revoked, their account becomes an unmonitored door into your systems — and a scheduling platform exposes calendars, booking data, and customer contact details. 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 members who can sign in to Cal.com.

**Remove access for offboarded users**

1. In Cal.com, go to **Settings → Team** (or **Members**) and remove members who have been offboarded.
2. Rotate the Cal.com **API key** if a departing employee had access to it.
3. In DSALTA, open **People** and confirm offboarded employees are marked terminated.

Once no offboarded employee retains active Cal.com 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 Cal.com 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 users 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 Cal.com configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Cal.com.
  </Accordion>
</AccordionGroup>