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

# User access to Critical System should be valid

> Checks that every user with Cal.com access is an active, authorized employee.

Checks that every user with Cal.com access is an active, authorized employee.

## About

When you connect Cal.com to DSALTA, the platform syncs the connected account using read-only API access. On every sync DSALTA compares the users on the Cal.com Access page against your **People** directory, matched by email within your organization, and activates this check when a Cal.com user is not an active employee on the People page.

<Note>
  Cal.com's free plan is individual, so the Access list is the connecting account rather than a full member roster, and the email-based match may not resolve automatically. Use the Access list as an inventory of who can sign in to Cal.com and confirm each is a current, authorized employee.
</Note>

## Why This Matters

Access to the organization's Cal.com account must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving people with more than they need. Excess access to a scheduling platform that exposes calendars and booking data widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach it is a core control in SOC 2 and ISO 27001.

## How to Fix

**Before you begin**

* Ensure the Cal.com integration is connected so DSALTA has the current account and access list.

**Review Cal.com access**

1. In Cal.com, go to **Settings → Team** (or **Members**) and review the members who can sign in.
2. Remove anyone who is not a current, authorized employee.
3. In DSALTA, open **People** and confirm each Cal.com user exists and is active.
4. Mark each reviewed user as **In Scope** (valid) or **Not in Scope** (to be revoked), and record the reviewer.
5. Set a recurring access review schedule (quarterly is recommended).

Once every Cal.com user is an active employee on the People page, 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="Why does the Access list show one account instead of my whole team?">
    Cal.com's free plan is individual and does not expose a team or members endpoint, so DSALTA lists the connected account identified from `/me`. If an organization roster becomes reachable, the list expands automatically.
  </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>