> ## Documentation Index > Fetch the complete documentation index at: https://docs.autosage.ai/llms.txt > Use this file to discover all available pages before exploring further. # Members & roles > The roles in an AutoSage organization and exactly what each one can do. Every person in an organization is a **member**, and every member has a **role**. Roles decide what each person can see and change — from reading content to managing billing and the organization itself. Assigning the right role keeps day-to-day work smooth while keeping account administration in the right hands. ## The roles Full control of the organization: managing members and roles, billing, and the organization itself. There is a single owner, and ownership can be transferred to another member. An administrative role just below owner. Manages billing and can create, update, and delete day-to-day resources such as tenants, knowledge bases, documents, agents, and chats. Works with documents and chats without organization-level administration. Developers can inspect knowledge bases and agents, but cannot configure either resource. Read-only access across the organization. ## What each role can do Read (**R**), write/create (**W**), and delete (**D**) by resource: | Resource | Owner | Billing admin | Developer | Viewer | | --------------- | ----- | ------------- | --------- | ------ | | Organization | R W D | R | R | R | | Members & roles | R W D | R | R | R | | Billing | R W | R W | R | R | | Environments | R W D | R W | R | R | | Tenants | R W D | R W D | R | R | | Knowledge bases | R W D | R W D | R | R | | Documents | R W D | R W D | R W | R | | Agents | R W D | R W D | R | R | | Chats | R W D | R W D | R W | R | The Owner always has full access to everything in the organization. Only the Owner can invite or remove members, assign roles, and revoke invitations. ## Ownership and membership Each organization has exactly one owner. To hand over control, **transfer ownership** to another member from the members screen. You can't remove the last owner. Transfer ownership first, and the previous owner can then be reassigned or removed. A single person can be a member of more than one organization, holding a different role in each. Give people who upload documents and work in chats the **Developer** role. Use **Owner** or **Billing admin** for people who need to create or configure knowledge bases and agents, delete working resources, administer the account, or manage billing. ## Next steps Add people by email and assign their role. How organizations, environments, and tenants fit together. How knowledge bases, agents, chat, and memory relate. The API-level view of environments and tenants.