Fix: “Account suspended due to storage” (Admin Triage)

When a Google Workspace user or an entire domain remains over its allocated storage limit past Google’s grace period, Google automatically places the account into an enforcement state. For an individual user, this results in an account suspension or an immediate read-only lock. When this occurs, the user cannot send or receive Gmail messages, cannot upload new Drive files, and cannot edit existing Docs or Sheets.

Quick Answer

To restore access, open the Google Admin Console, go to Directory > Users, select the suspended user, and click Reactivate (or Restore). Next, immediately increase the user’s Organizational Unit (OU) storage limit to prevent re-suspension. Once unblocked, have the user permanently empty their Drive Trash and remove large files.

---

Understanding the Suspension Triggers

Google Workspace enforces storage limits through progressive warning stages before shutting down service access:

1. Warning Phase: The user sees in-app warnings in Drive and Gmail indicating storage is full. Files can still be viewed, edited, and downloaded.
2. Upload Block & Email Disruption: If no action is taken, upload permissions are revoked. Incoming emails bounce back to senders with error code 552 5.2.2: The email account that you tried to reach is over quota.
3. Account Suspension / Administrative Lock: If the account remains severely over quota or violates domain-wide overage policies for extended periods, Google flags the account. In some enterprise configurations, automated admin policies or security monitors suspend the user entirely to protect tenant compliance.

---

Step 1: Reactivate the Suspended User

If the user account is marked with a red “Suspended” tag in the Admin Console:

1. Sign in to the Google Admin Console as a Super Admin.
2. Navigate to Directory > Users.
3. Locate the suspended user.
4. On the user’s profile card, click More options (or look under the user status banner) and click Reactivate (or Restore).
5. Confirm the prompt.

Note: Reactivating the account removes the login block, but if the storage condition that triggered the suspension is still present, the user will be locked out again within minutes or hours.

---

Step 2: Apply an Emergency Storage Allocation

Before instructing the user to clean up their files, you must give the account operational breathing room. If the account remains at 100% capacity, the user cannot even create a temporary archive, process Google Docs, or manage mail effectively.

1. In the Admin Console, go to Storage.
2. Click Storage settings or User storage limit.
3. Select the Organizational Unit (OU) containing the affected user.
4. Temporarily raise the storage cap by 5 GB or 10 GB (or temporarily switch the setting to No limit).
5. Click Save.

This temporary ceiling adjustment propagates across Google’s identity infrastructure, allowing the user to log in, receive critical incoming messages, and begin the cleanup process without system errors.

If your domain as a whole has zero available space to allocate, an administrator must add pooled storage to the tenant. Review “Buy Storage” button missing in Workspace accounts for instructions on adding capacity via Google Workspace Additional Storage.

---

Step 3: Rapid Data Purging & Trash Cleanup

Once access is restored, the user must clear out unneeded data to bring their footprint beneath the organization’s standard policy threshold:

1. Delete Large Attachments in Gmail:
   In Gmail search, enter:
   Select and delete obsolete media, logs, and slide decks. has:attachment larger:10M
2. Purge Drive Files:
   Open drive.google.com/drive/quota to list files in descending order of file size.
3. Empty the Trash Bin Immediately:
   Deleting a file in Google Drive simply moves it to the Trash folder. Files in the Trash continue to consume storage quota until they are permanently removed. The user must open the Trash tab and click Empty trash.

If the user deleted files but their quota meter remains full, consult Why Drive Trash is still counting against your quota.

---

Step 4: Address Domain-Wide Reporting Latency

After clearing gigabytes of data, the user and administrator may still see the red “Storage Full” warning. This is normal.

Google’s storage calculation service does not calculate user storage dynamically on every page load; it uses asynchronous batch indexing. It can take 4 to 24 hours for mass deletions to reflect in the Admin Console.

Do not lower the user’s emergency OU limit back to the restricted level until the Admin Console shows that their reported usage has dropped below the baseline threshold. To track backend propagation, see Resolving the 24-Hour Latency in Storage Reporting.

If you suspect hidden files that do not show up in the user’s active folders are consuming their quota, investigate unlinked data using Troubleshooting “Orphaned” files and storage theft.