---
title: "SCIM login issues"
slug: "scim-login-issues"
description: "Sync issues with SCIM in Document360? Learn how to resolve user provisioning errors and manage groups effectively from your IdP."
updated: 2026-06-03T11:14:03Z
published: 2026-06-03T11:14:03Z
canonical: "docs.document360.com/scim-login-issues"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.document360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SCIM login issues

## Sync failed due to a SCIM server error

When adding new users from Okta or Entra, this error indicates that one or more users could not be synced to Document360. This may be caused by:

- Duplicate users provisioning
- User limit reached based on your current subscription plan
- Other validation or processing errors.

Click **View details** to see which users failed to sync.

![User management interface displaying sync error and user account details.](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/sync%20error.png)

---

## User already available in the project

If SCIM returns a "user already available in the project" error, it means the email address is already registered as a User in Document360. If your intent is to convert them to a Reader, follow these steps:

1. In your IdP, locate the user's profile and navigate to the `isTeamAccount `attribute.
2. Set `isTeamAccount = True`, this lets the system recognize the existing email as a User.
3. Save the changes and allow the sync to complete. Once synced, go back to the user's profile in your IdP.
4. Set `isTeamAccount = False`, this converts them to a Reader automatically.
5. Save the changes and allow the sync to complete.
6. To verify, navigate to **Document360** > **Settings** > **Users & permissions** > **Readers & groups** and confirm the user now appears as a Reader.

---

## SCIM group is manually deleted in Document360

If a SCIM-provisioned group is manually deleted in Document360, re-pushing the same group from your IdP will fail because the group no longer exists on the application side.

To resolve this:

1. Remove or unlink the affected group from your IdP.
2. Sync the group again from the IdP to create it fresh in Document360.

Avoid deleting SCIM-managed groups directly in Document360. Always manage SCIM groups from your IdP to avoid sync issues.

Disabling and re-enabling SCIM does not automatically restore groups that were previously synced. If any SCIM-managed groups were deleted while SCIM was disabled, you must push those groups again from your IdP.

> [!NOTE]
> NOTE
> 
> If your user license limit has already been reached, re-syncing or re-pushing groups may fail because group linking depends on successful user provisioning. Before re-syncing groups, make sure your user limit has available capacity.