Skip to content

Add "Leave Brain" Option for Invited Users #84

@rutvi-weam-ai

Description

@rutvi-weam-ai

Overview

Currently, invited users do not have the ability to leave a Brain on their own. This creates a poor user experience, especially when users want to exit shared workspaces they no longer wish to participate in. The only workaround is to archive or delete the Brain (if they have permissions), which is not a clean or intuitive solution.

This feature allows users to voluntarily leave a Brain they’ve been invited to, improving autonomy and reducing clutter in their dashboard.


User Story / Use Case

As a user who has been invited to a Brain,
I want the ability to leave the Brain at any time,
so that I can manage which Brains I participate in and reduce clutter in my dashboard.

Proposed Solution

* Add a "Leave Brain" option in the Brain settings menu for invited users.
* On click, show a confirmation modal: "Are you sure you want to leave this Brain?"
* If confirmed:
    - Call backend API
    - Remove user’s association with the Brain.
    - Redirect user to the dashboard or previous page.


Acceptance Criteria

* [ ] "Leave Brain" option is visible to invited users in the Brain settings.
* [ ] Clicking "Leave Brain" prompts a confirmation modal.
* [ ] On confirmation, user is removed from the Brain and redirected.
* [ ] Option is hidden/disabled for Brain creators or admins.
* [ ] Backend correctly removes Brain membership and updates DB.
* [ ] Proper error handling (e.g. if the user is the last admin or if the Brain no longer exists).

Impact

* Improves user control and experience.
* Reduces dashboard clutter for users who are part of many Brains.
* Aligns functionality with user expectations from collaborative platforms.
* Avoids misuse of archive/delete functions just to exit a Brain.

Alternatives Considered

* Keeping current behavior (no "Leave" option) — rejected due to poor UX.
* Allowing users to request removal from the owner — adds friction and is not scalable.

Additional Notes

* This feature should be tested across both web view and mobile view versions.
* Consider edge cases like users who are the only member of the Brain.
* May require UI adjustments if roles/permissions are tightly coupled to Brain membership.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions