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
How to add team members, assign roles, and select workspaces
What a new member does after receiving an invitation
Full breakdown of Owner, Admin, and Member permissions
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
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.
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. No exceptions.
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
Last updated