Lacking basic CRUD for user management

[she0305]

1. When you create a test user and delete the user with the admin right (from supabase), you cannot create the same user with the deleted email address. It seems like there's a disconnection between supabase user management and cal.com user management. The newly created user has "NULL" for calAccount and calAccessToken, which prevents the user from using the full feature

2. You cannot edit category options that you select from "Step 2". There's no UI for users to update. Even when you try to delete/update the relation with the Admin right on supabase, you get an error

[supalarry]

About deleting user - if a managed user is deleted from Supabase, then it's also necessary to delete in on our end by sending a DELETE request to v2/oauth-clients/{clientId}/users/{userId} with Authorization: Bearer access-token header.

[she0305]

About deleting user - if a managed user is deleted from Supabase, then it's also necessary to delete in on our end by sending a DELETE request to v2/oauth-clients/{clientId}/users/{userId} with Authorization: Bearer access-token header.

Great, thank you. Is the implementation of this feature in the UI planned for the near future? Having 3 places to delete is not so convenient. But glad to learn that there's a quick fix for this though. Thank you