Skip to main content
From the members list, authorized administrators can change a member’s role or remove the member. Permission changes affect future access as soon as Biqli applies them. Before removing an administrator, check whether they are responsible for integrations or ownership tasks. Removing a member does not delete the workspace resources they created. Biqli prevents role and removal actions that would violate required ownership safeguards.

​
Change a role

Open the member row, choose the new built-in or custom role, review its permissions, and save. The member’s future access follows the new role after the change is applied.

​
Remove a member

Confirm that the member is not the sole required owner or administrator. Hand over integration, domain, billing, and security responsibilities, then remove the membership. Workspace resources they created remain with the workspace.

​
Respond to unexpected access

Remove or reduce access promptly, then review workspace activity and API keys. Membership removal does not necessarily revoke credentials held by an external service, so disconnect integrations and rotate shared provider secrets where needed. Use a custom role rather than repeated role changes when several people need the same limited access pattern.

​
Frequently asked questions

No. Workspace resources remain in the workspace.

​
Why is the remove action unavailable?

Ownership safeguards or your own role can prevent it. Confirm that another eligible owner or administrator exists and that you have member-management authority.