> ## Documentation Index > Fetch the complete documentation index at: https://learn.biq.li/llms.txt > Use this file to discover all available pages before exploring further. # Understand workspace ownership and member access > Understand actions reserved for owners and authorized members. Workspace ownership carries responsibilities that ordinary resource permissions do not replace. Actions such as destructive workspace changes, ownership transfer, and some billing or security settings can require owner-level authority. A member with write access to links does not automatically gain member administration or billing access. Keep these responsibilities separated unless the person's role truly requires both. Before an owner leaves or is removed, assign the required ownership or administrative coverage to another eligible member. ## Owner responsibilities Owners protect workspace continuity. They should maintain valid account security, understand billing and domain dependencies, and make sure another eligible administrator can respond when the primary owner is unavailable. ## Transfer or hand over access Before an ownership change, review members, billing, API keys, SSO, custom domains, and integrations. Confirm the receiving person can access every external provider needed to operate the workspace. ## Permission boundaries A member can create or edit resources without owning the workspace. An API key can manage permitted resources without gaining owner authority. SAML or SCIM provisioning can create membership but should not be assumed to replace the workspace's ownership safeguards. Do not leave one inactive account as the only administrative recovery path. ## Frequently asked questions ### Does an Admin automatically become an owner? No. Administrative permissions and ownership are related but distinct concepts. ### What should happen before an owner departs? Transfer the required responsibility, verify billing and security access, and test that another authorized person can operate external providers.