Quible user permissions and roles are 2 tier: Company Level, and Project Level.
On a Company Level:
* These are responsible for what happens within Quible as a tool, they do not necessarily mimic your roles within your companies, but intended to ensure proper management of Quible.
Company Admin:
Has full control over the entire Quible system.
Can manage all Knowledge Bases on the company level, Company Settings, Connectors, Billing, Permissions, and all Users.
Can create or remove Admins.
Has the highest‑level authority.
Multiple Users can be assigned Company Admin access.
Project Admin:
Has high‑level control, but not as much as a Company Admin.
Can manage their own Knowledge Bases, Projects, and Users, but cannot manage Knowledge Bases and Projects not created by them, and cannot manage Connectors access.
Cannot change system‑wide settings or billing.
Cannot remove or modify the Company Admin.
User:
A regular user.
Can access and use the features they’re allowed to.
Cannot manage other users or system settings.
Focuses on participating, contributing, or using Quible - not managing it.
On a Project Level:
* Roles within the project reflect real life project management regardless of roles assigned in Quible on a Company level. The intent is to have you and your team assign the roles within the Quible Project level as they are in your workplace.
i.e A Quible Company User can be assigned as a Project Manager within Quible to comply with real life project assignments.
Project Manager:
Has high‑level control on the Project by adding and removing Knowledge Bases and Members.
Can create Projects and Knowledge Bases but cannot manage Knowledge Bases and Projects not created by them.
Member:
Is a teammate in a project, contributing to a project, but is not the person(s) managing the project in the real world.
Cannot create Knowledge Bases in the Project to not pollute the data.
Cannot share project conversations if access is not granted to them.