Skip to content

Commit 1bfebea

Browse files
Add Use case 5
1 parent 95cfca2 commit 1bfebea

1 file changed

Lines changed: 25 additions & 0 deletions

File tree

docs/specs/organization/10-use-case.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -345,3 +345,28 @@ CREATE UNIQUE INDEX _auth_organization_auto_membership_domain_uniq _auth_organiz
345345

346346
> [!NOTE]
347347
> Fung suggests that we target Use case 4.1 and Use case 4.4 for MVP
348+
349+
## Use case 5: How to dissociate a User from an Organization?
350+
351+
### Use case 5.1: Remove a User from Member of Organization via Admin API
352+
353+
This is trivial.
354+
355+
### Use case 5.2: A User can leave an Organization in the settings page
356+
357+
This is a rabbit hole because there could be many use cases that
358+
the developer may allow a User to leave an Organization.
359+
360+
Let me name a few here.
361+
362+
- Members in an Organization could have Roles. Depending on the Roles a Member has, he may or may not leave as he wishes.
363+
- The developer simply do not want Members to leave in a self-serve way.
364+
- The developer allows Members to leave freely.
365+
366+
> [!NOTE]
367+
> Auth0 support removing members from organizations via the dashboard or the Management API.
368+
> See https://auth0.com/docs/manage-users/organizations/configure-organizations/remove-members
369+
370+
### Use case 5: Design Decision
371+
372+
We implement Use case 5.1 for MVP.

0 commit comments

Comments
 (0)