> ## 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 retain active Render access.

Checks that offboarded employees no longer retain active Render access.

## About

When you connect Render to DSALTA, the platform lists your Render workspace members using read-only API access. DSALTA compares the Render Access-page members against your People page and flags anyone with active access whose employee record is terminated or offboarding. DSALTA evaluates this control on every sync.

## Why This Matters

When someone leaves and their access is not revoked, their credentials become an unmonitored door into your hosting platform — a common cause of data theft and accidental damage. Access for terminated or offboarding employees must be revoked promptly. Timely access removal on termination is explicitly required by SOC 2, ISO 27001:2022, and UK GDPR.

## How to Fix

**Before you begin**

* Identify all offboarded employees by cross-referencing your People page in DSALTA with active Render members.
* Ensure you have **admin** access to the Render workspace.

**Revoke Render access for offboarded users**

1. In Render, go to **Workspace settings → Members**.
2. Remove each offboarded employee from the workspace so they can no longer authenticate.
3. Revoke any API keys or service credentials tied to that person.
4. To automate this going forward, connect your HRMS to DSALTA so that an "Offboarded" status automatically flags any lingering access.

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