Skip to main content
Workspace members collaborate without sharing an account or API key. Each member receives a role that determines which settings and resources they can read or change. Use built-in roles for common access patterns. Use a custom role when a person needs a more specific combination of permissions. Review membership regularly and remove access that is no longer required.

​
Member lifecycle

An authorized user sends an invitation with an initial role. The recipient must accept it before becoming an active member. Administrators can later change the role or remove the membership, subject to ownership safeguards.

​
Choose a role

Admin, Editor, and Member cover common patterns. Custom roles let you configure resource categories more precisely. Give people the least access required for their work and separate content editing from billing, security, and member administration.

​
Review regularly

Check pending invitations, active members, custom role assignments, and owners. Remove unused invitations and departed members. Confirm that at least one eligible administrator remains available for recovery. Membership is workspace specific. The same person can have different roles in different workspaces.

​
Frequently asked questions

​
Should teammates share one account?

No. Invite each person separately so roles, sessions, two-factor authentication, and activity records remain attributable.

​
Do members need an API key?

No. API keys are for server-side integrations. Members use their own Biqli accounts and assigned workspace roles.