# Member Roles Explained Qolaba uses role-based access control (RBAC) to keep organizations structured, secure, and easy to manage. Every member of an organization holds one of three roles: **Owner**, **Admin**, or **Member**. *** ### Quick Comparison

Permission	Owner	Admin	Member
Use AI tools (Chatbot, Image, Video, Speech)	✅	✅	✅
View Overview & History	✅	✅	✅ (assigned workspace)
Invite & remove members	✅	✅	❌
Assign & change roles	✅	✅	❌
Create, edit & delete workspaces	✅	✅	❌
Monitor credit usage	✅	✅	❌
Buy credits	✅	✅	❌
Upgrade or cancel subscription	✅	✅	❌
Edit organization profile	✅	✅	❌
Delete the organization	✅	❌	❌

*** ### Owner The Owner is the highest authority in an organization. The account that creates the organization is automatically assigned the Owner role. **What the Owner controls:** * All organization settings * Subscription and billing * Credit management * Member and workspace management * Structural deletion of the organization **The one exclusive permission:** Only the Owner can permanently delete the organization. This restriction exists to prevent accidental or unauthorized removal of the entire account structure. In most cases, an organization has a single Owner. The Owner role cannot be assigned through the standard invite flow — it transfers only through deliberate ownership change. **Best suited for:** Founders, company principals, or whoever holds final accountability for the account. *** ### Admin Admins support the Owner in day-to-day management. They have nearly full operational access, with one hard limit: they cannot delete the organization. **What an Admin can do:** * Invite and remove members * Assign and change member roles (excluding ownership transfer) * Create, edit, and delete workspaces * Monitor credit usage across the organization * Purchase additional credits * Upgrade or cancel the subscription **What an Admin cannot do:** * Delete the organization **Best suited for:** Team leads, operations managers, department heads, or project managers who need to manage people and workspaces without holding ultimate structural authority. *** ### Member The Member role is designed for users who work within Qolaba — not those who manage it. Members have no administrative access. **What a Member can do:** * Access their assigned workspace * Use all AI tools: Chatbot, Image generation, Video, Speech * View the Overview tab * View History within their assigned workspace **What a Member cannot do:** * Invite or remove members * Create or manage workspaces * Modify or cancel the subscription * Purchase credits * Edit organization settings * Delete the organization **Best suited for:** Designers, writers, marketers, developers, or any user whose primary need is to use Qolaba's AI tools. *** ### Why Role Separation Matters Clear role boundaries prevent accidental changes, reduce governance risk, and make accountability straightforward as organizations scale. **Example — Marketing Agency:**

Person	Role
Founder	Owner
Account & Project Managers	Admin
Designers, Copywriters, Strategists	Member

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.qolaba.ai/organization-and-workspaces/members-and-role-based-access/member-roles-explained.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.