Workspace admins can instantly revoke access by removing members from a workspace. This action cannot be undone and permanently deletes all role and team assignments.
This guide covers how workspace admins can remove members from a Baserow workspace, understand what happens when members are removed, and troubleshoot common access issues.
Removing a member is useful when project teams change, contracts end, or access needs to be restricted quickly. The removed member loses immediate access to all workspace databases and tables, but their Baserow account remains active for use in other workspaces.
Only workspace admins can remove members. Regular workspace members cannot remove others from the member list.
You must have workspace admin permissions to remove members.

Use the search feature at the top of the Members page to quickly find members by name or email address.
When you remove a member from a workspace:
The removed member does not receive an automatic notification. Consider informing them directly before removal if appropriate.
| Action | Scope | Account Status | Use Case |
|---|---|---|---|
| Remove member | Single workspace | Account remains active | Revoke access to one workspace |
| Delete user (self-hosted) | Entire instance | Account permanently deleted | Remove user from self-hosted installation |
Removing a member only affects access to one workspace. The user can still access other workspaces they belong to. Deleting a user account is only available to instance admins on self-hosted Baserow and removes the account completely.
Databases can become orphaned when a workspace admin creates a database, restricts access for all other workspace members, and then leaves the workspace. No one can access the database because no remaining workspace members have admin permissions.
This process requires workspace admin permissions to invite and assign roles.
No. Removing a workspace member permanently deletes their role and team assignments within that workspace. To restore access, you must re-invite them and reconfigure all permissions and team memberships.
Baserow does not send automatic notifications when workspace members are removed. Consider communicating with the member before or after removal if appropriate for your situation.
All data, rows, tables, and views created by the removed workspace member remain in the workspace. Only their access is revoked; their contributions are preserved.
Yes, but only if you’re not the last admin. Workspaces must always have at least one admin. If you’re the sole admin, you must either promote another workspace member to admin first or delete the workspace entirely.
Workspace members are users who have access to a workspace with assigned roles (Admin, Editor, etc.). Collaborators refer to the Collaborator field type used to assign specific workspace members to individual rows for task assignment.
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions; we’re ready to assist you.
Contact support for questions about Baserow or help with your account