---
schema_version: "1"
id: 7a58bf2ceb51bd474e511d1c1bc885057ed78e2a45d04ab7d5a69d62d7488122
title: Inactive User Freezing
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/data_sandbox_inactive_user_freezing.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.data_sandbox_inactive_user_freezing.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8d87b52894a0e298015b54fa1f5fd6575ecdece92921c05291c838d657c58243
description: Users who haven’t logged in to a Developer or Developer Pro sandbox within the first 60 days based on the time the user was created are frozen. This feature can’t be disabled.
products:
  - Salesforce Platform
release: "264"
---
# Inactive User Freezing

Users who haven’t logged in to a Developer or Developer Pro sandbox within the first 60 days based on the time the user was created are frozen. This feature can’t be disabled.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Database.com</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d9295e73">User Permissions
            Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d9295e73 ">To view a sandbox:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d9295e73 ">View Setup and Configuration</td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d9295e73 ">To freeze or unfreeze user accounts:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d9295e73 ">Freeze Users or Manage Users</td>

        </tr>
      </tbody>
    </table>

## Why Is Salesforce Running This Process?

Salesforce is running this process for two main reasons:

- Security—Most production users have login access to sandboxes but don’t require it. Security is improved by limiting access to only active users.
- Performance—Inactive users impact the login experience for sandboxes. By limiting access to only active users, the login experience is faster in existing and new sandboxes.

## Who’s Impacted by This Change?

Users who have login access to a sandbox, including admins, are subject to freezing if they don’t log in within the first 60 days of the user being created in the sandbox. This change also applies to users created by the sandbox refresh process and users created by an admin in the sandbox after a sandbox was created, refreshed, or cloned. For existing sandboxes older than 60 days, users that logged in at least one time aren’t frozen.

## Are Any Users Exempt From the Freezing Process?

No. Any user who can log in to a sandbox is eligible for freezing. After a sandbox is created, refreshed, or cloned, users must log in within 60 days to retain access.

Users are exempted from freezing if they’ve logged in using any of these authentication methods:

- Basic authentication
- API key authentication
- OAuth 1.0
- OAuth 2.0

## Which Sandboxes Are Impacted?

This change applies to all new and existing Dev and Dev Pro sandboxes on all instances (Salesforce first-party and Hyperforce) regardless of their creation method.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-deploy_sandboxes-264-0-0-production-enus/654e51d1-6795-49fe-bd43-b5385950cf4a/images/icon_note.png)

Note This process doesn’t affect Partial Copy and Full sandboxes. We’ll provide advanced notice when we enable this feature for these sandbox types.

## Can I Opt Out of This Process?

No. Users that need access to a sandbox must log in at least one time in the 60 days following the date the user was added to the sandbox.

## If I Log into the Sandbox and Don’t Log In Again for 60 or More Days, Will I Be Frozen?

No. After you log in to a sandbox, you’re exempt from being frozen when the process runs again in the future.

## Is There a Way to Unfreeze a User?

Yes. A user with access to the sandbox who has the appropriate user permissions can unfreeze other users. After a user is unfrozen, we strongly recommend that the user logs in to the sandbox that same day to avoid getting frozen again. See Salesforce Help: [Freeze or Unfreeze User Accounts](https://help.salesforce.com/s/articleView?id=platform.users_freeze.htm&type=5&language=en_US) for details.

## What Can I Do If All Admin Users Are Frozen? What If No One Can Access the Sandbox?

We strongly recommend that at least one admin user logs in to a sandbox after creation, refresh, or cloning. If all users with the appropriate user permissions to manage or unfreeze users are frozen, you have some options:

- If the existing sandbox is outdated or not being actively used, you can refresh it. Users must log in within 60 days to retain access.
- If you want to regain access to the existing sandbox, contact Salesforce Customer Support, who can unfreeze the desired user accounts.

## How Do I Know That the Process Has Run on a Sandbox?

The Setup Audit Trail in the sandbox provides information about the number of users that were frozen due to inactivity. Salesforce isn’t sending any email notifications before or after the process runs.

#### See Also

- [_Salesforce Help:_ Freeze or Unfreeze User Accounts](https://help.salesforce.com/s/articleView?id=platform.users_freeze.htm&type=5&language=en_US)
- [_Salesforce Help:_ Monitor Setup Changes with Setup Audit Trail](https://help.salesforce.com/s/articleView?id=xcloud.admin_monitorsetup.htm&type=5&language=en_US)