# Members and Role-Based Access

## Members & Role-Based Access

Qolaba uses a structured, role-based access system to help organizations collaborate securely, manage credits transparently, and keep workspaces isolated. This section covers everything you need to know about managing who has access to your organization — and what they can do once they're in.

***

### What's in This Section

<table><thead><tr><th width="240.57421875">Page</th><th>Description</th></tr></thead><tbody><tr><td><a href="/pages/u0FWrK29aw1Xkwm5P5Tv">Inviting Members</a></td><td>How to add team members, assign roles, and select workspaces</td></tr><tr><td><a href="/pages/ty7QrDf1saw287GvEayZ">Member Activation Flow</a></td><td>What a new member does after receiving an invitation</td></tr><tr><td><a href="/pages/AGJQlT2d3CiVRO7RFJys">Roles Explained</a></td><td>Full breakdown of Owner, Admin, and Member permissions</td></tr></tbody></table>

***

### How It Works — At a Glance

Every Qolaba organization has three role tiers:

* **Owner** — Full control, including the ability to delete the organization
* **Admin** — Manages members, workspaces, and credits; cannot delete the organization
* **Member** — Uses AI tools within their assigned workspace; no administrative access

Members are invited by email, assigned a role and workspace, and gain access after logging in with the invited address. All activity and credit usage is tracked per member, per workspace.

***

### Key Concepts

1. **Workspace Isolation** : Each member is assigned to a specific workspace. They can only see and use the workspace(s) assigned to them. This keeps project history clean and credit usage clearly attributed.
2. **Email-Matched Access :**  Invitations are tied to a specific email address. The invited user must log in — or create an account — using that exact email.
3. **Role-Controlled Governance :** Only Owners and Admins can invite members, modify roles, or manage workspaces. Members have no administrative access, ensuring a clear separation between usage and management.

***

### Who Should Read This

* **Owners** setting up their organization for the first time
* **Admins** managing a growing team
* **Anyone** troubleshooting access or onboarding a new team 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.md?ask=<question>
```

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.