Hi @Kaneel_Dias1 and welcome to the Forum!
Many thanks @lpb and @Phil_Seeman !
I did some research and found a few resources that should help. First off, I’d recommend checking out the User deprovisioning and Provisioning and deprovisioning users with SCIM articles in our Help Center. It explains how SCIM deprovisioning works — which is very similar to the endpoint you’re using. The only key difference is:
- If you use a Service Account Token (SAT), the behavior matches SCIM exactly.
- If you use a Personal Access Token (PAT), the PAT owner becomes the fallback recipient of permissions instead of the user specified in the Admin Console.
Here’s what happens across different resource types:
- Projects → The user is removed/hidden. If they were the only admin of a
private_to_membersproject, permissions need to be reassigned manually to keep access. - Tasks → A project called Previously assigned tasks is created, with the PAT owner set as admin.
- Rules, Templates, Bundles → Ownership is transferred to the PAT owner (or the user specified in the Admin Console if using SCIM/SAT).
Note: If you’re using SCIM or SAT and don’t specify Member Removal Settings in the Admin Console, permissions default to all Super Admins. I’m not 100% sure which Super Admin would be selected for Rules, Templates, and Bundles specifically, so this is one edge case worth keeping in mind.
Hope this helps clarify things!
Best,
Dominik