There are some serious issues and inconsistencies with teams on Cloud:
- If team is deleted, all users will still have memberships in profile. That membership is invalid and can not be fetched or opened in console. Also can not be deleted as well since it does not exists, 404 is returned.
- If user account is deleted, teams are still gonna have that user membership. Both on console and with API, listMemberships returns all user from team, even though user account is delete. Fetching that specific membership or trying to open it in console returns 404, same as trying to delete it. Basically it can not be removed anymore.
This is giving me some very weird issues and wrong states at the moment since I am relying on teams for permissions and memberships.
All this is working perfectly fine on self hosted, also v1.5.7.
This is what I see in console in user profile as an example, there are 4 invalid memberships
TL;DR
Developers reported issues with ghost teams and memberships:
- Deleted teams leave invalid memberships in user profiles that cannot be fetched, opened, or deleted.
- Deleted user accounts remain in team memberships despite being unable to be fetched, opened, or deleted.
This inconsistency in Cloud causes problems with permissions and team states. The issue does not occur on self-hosted v1.5.7.
Solution: Contact Cloud support to address and resolve the ghost team and membership inconsistencies.
