Member settings
Member settings control workspace roles and who can invite, remove, or manage other members and shared resources.
Category
Product feature
See all terms
What are member settings?
Member settings govern who belongs to a workspace and what they're allowed to do in it. Every workspace has exactly one owner, plus any number of admins and members, and each role carries a different set of permissions over shared resources like source credentials, API keys, MCP authorization, and data sources.
Why member settings exist
A workspace usually has more than one person touching it, and not everyone should have the same reach. Without role-based limits, any member could remove another person, change someone's role, or delete resources they didn't create. Member settings draw that line up front: an owner has full control including deleting the workspace itself, an admin can manage members and shared resources but not delete the workspace, and a regular member can create and use resources but only update or delete the ones they made themselves.
How do member settings work?
Owners and admins can view, create, update, and delete workspace resources. Members can create and view the same resource types but are limited to updating or deleting their own creations, regardless of role.
Only owners and admins can invite new members, remove existing ones, or change someone's role. To invite someone, an owner or admin goes to Settings, opens the Members tab, enters the invitee's email, and assigns a role, which sends an invitation link. Removing a member means finding them in the same tab, selecting Revoke access, and confirming. Changing a role works the same way: find the member and pick Admin or Member.
Admins can't demote themselves; that has to go through the owner. Editing the workspace name or URL requires owner or admin status, and only the owner can delete the workspace outright. These roles set the baseline that access controls then refine at the file and folder level.