Summary #
When you delete a tenant user, the user is no longer considered active in the regular team management.
However, the platform applies anti-abuse protection on the reuse of user seats, also called seat cooldown.
This means that the seat freed by deletion is not immediately reusable in all cases.
In the current configuration, the standard waiting time is:
24 hours
After this period, the released seat can be reused to create a new user, if the tenant still has availability within the assigned limits.
Why a grace period exists #
The grace period serves to prevent users from being continuously created and deleted to circumvent plan limits.
Without this protection, a tenant could:
- create a user;
- have it used for a short period;
- delete it;
- immediately create another user;
- repeat the cycle many times.
This behavior would make the count of assigned users unreliable and could turn a user limit into unlimited use over time.
For this reason, when a user is deleted, the released seat may remain temporarily locked before being reusable.
What happens when I delete a user #
When the Tenant Admin deletes a user:
- the user is removed from the operational list of active users;
- the user can no longer access the platform;
- the system records the deletion;
- the seat linked to that user enters a cooldown window;
- the tenant may need to wait before reusing that seat to create a new user.
How long do you need to wait #
In the current configuration, the standard cooldown is:
24 hours
This means that, after deleting a user, the tenant may need to wait up to 24 hours before being able to reuse that seat to create a new user, if they are trying to reuse the seat just freed.
Can I re-enter the same email address? #
From the perspective of the technical constraint on email, a deleted user is no longer considered an active user.
This means that, after a true deletion, the same email address can be used again to create a new user, if other rules allow it.
However, re-entry may still be subject to seat cooldown.
So you need to distinguish two aspects:
- email reuse: technically possible after deletion;
- user seat reuse: may require waiting for the grace period.
Difference between deleting and deactivating #
It is important to distinguish between a deleted user and a simply deactivated user.
Deleted user #
The user is removed from the operational list and is no longer considered active.
In this case, the email does not remain locked as the email of an active user.
Deactivated user #
The user remains present in the system, but cannot access.
In this case, the email may remain associated with that user and it may not be possible to create another user with the same email.
If the goal is to free the email or completely remove the user from the operational team, you must use the correct action provided by the platform.
Anti-churn limit #
In addition to individual seat cooldown, the platform also applies a check on the number of user creations and deletions in a time period.
In the current configuration, the standard limit is:
30 user creation/deletion events in 24 hours
This means that, if too many users are created and deleted in a short time in a tenant, the system may temporarily block new operations.
This check serves to prevent anomalous or overly frequent use of user management.
Practical example #
A tenant has 50 assigned users and has already used them all.
The Tenant Admin deletes a Player to free a seat.
Immediately after, they try to create a new Player.
In this case, the system may block the creation because the seat just freed is still in the cooldown period.
The Tenant Admin will need to wait for the end of the grace period, or check with the Provider if other users assignable to the tenant are available.
What the administrator sees #
If the cooldown is still active, the system may prevent the creation of the new user.
The block does not mean that the tenant is broken or that the email is necessarily incorrect.
It means that the system is protecting the immediate reuse of user seats just freed.
Why this rule is useful #
This rule allows for more correct resource management.
It helps prevent:
- user limits from being circumvented;
- users from being created and deleted excessively;
- the tenant’s plan from being used beyond the intended capacity;
- administrative data from becoming inconsistent;
- the Provider from losing control over the actual use of resources.
What to do if you need to create a new user immediately #
If the tenant needs to create a new user immediately but the seat just freed is still in cooldown, the options are:
- wait for the end of the grace period;
- check if the tenant still has unused available users;
- ask the Provider for a temporary or permanent increase in the number of assigned users;
- avoid repeated deletions and creations in close succession.
Best practices #
To avoid blocks in user management, it is advisable to:
- delete users only when they no longer need to use the platform;
- avoid continuously deleting and recreating users;
- plan ahead for the number of Players needed;
- use CSV import only when the tenant has sufficient capacity;
- check the Resources and Limits section before creating many users;
- ask the Provider for more assigned users if the tenant is growing steadily;
- consider the cooldown when replacing users close to a training session.
Final result #
If you delete a user, their account is removed from operational use and can no longer access.
The same email can be reused after deletion, but the freed seat may be subject to a grace period.
In the current configuration, the standard cooldown is 24 hours.
Additionally, if too many creations and deletions are performed in a short time, the system may temporarily block new operations to protect the correct management of tenant resources.
