
Last updated: May 29, 2026
TL;DR: Quire's Permissions and Roles system has 5 default organization-level roles (Admin, Normal+, Normal, Limited+, Guest) and 4 project-level roles (Admin, Normal, Limited, Guest). Custom roles on Premium+, External Team scope on Professional+. Organization-level permissions override project-level.
Teamwork is all about collaboration, but not everyone has the same role in your organization. That is the reason why we decided to enhance permissions in Quire. Besides the default roles, you can now customize and add more roles to your organization and projects.
The case for role-based access control is well-established in security and information governance literature. According to NIST's RBAC (Role-Based Access Control) standard, the reference model most modern SaaS platforms implement, roles should be defined once and then assigned to members, instead of permissions being granted ad hoc per user. That's exactly the design Quire's permission system follows. The benefit is consistency. Two members with the same role have exactly the same access, every time.
Whether you are an admin, a team leader, or a collaborator, here is how permissions control works in Quire.
There is one thing you should know beforehand. Organization level members have more power than Project level members. To put in other words, Organization Admin has the ultimate permissions, including managing every project within that organization and its members.
| Admin | Normal+ | Normal | Limited+ | Guest | |
|---|---|---|---|---|---|
| Member management Invite memebers, manage member's permission |
V | ||||
| Global access Access to all projects in this organization if granted in organization-level |
V | V | V | ||
| Create projects in the organization | V | V | V | ||
| Delete projects in the organization | V |
Normal+ and Limited+ are only applicable for the organization level. These two roles can access all projects in the organization.
| Admin | Normal | Limited | Guest | |
|---|---|---|---|---|
| Member management Invite members, manage member's permission |
V | |||
| Manages project tags Create, edit and delete tags in the projects |
V | V | ||
| Manage project's statuses Create, edit and delete statuses in the projects |
V | V | ||
| Change statuses Complete and change tasks' statuses |
V | V | V¹ | |
| Schedule Manage start, due, priority, assignee |
V | V | V² | |
| Install apps | V | V | ||
| Edit Add and edit any tasks (inclucing task's name, description, attachments, and tags), add and remove sublists |
V | V | ||
| Edit with limitations Add tasks, edit assigned tasks, write comments to any tasks |
V | V | V³ ⁴ ⁵ | |
| Delete tasks⁶ Delete the tasks that are created by others |
V | V |
Note:
¹ Can only change the task's status when it is assigned to that particular member.
² Can only edit the task's date, status and priority when the task is assigned to that particular member. Cannot edit the task's assignee.
³ Can only edit and delete the comment when it is added by that particular member.
⁴ Edit the task's name and description when the task is assigned to or created by that particular member.
⁵ Change the tags when the task is assigned to or created by that particular member.
⁶ Without this permission, the user can still delete the tasks that he/she created.
Most modern PM tools have a permission system. The differences come down to whether roles are fully customizable, the granularity of project-level vs. organization-level scope, and whether external collaborators get a separate access tier.
| Tool | Custom roles | External collaborator scope | Plan tier required |
|---|---|---|---|
| Quire | Yes (Premium+); customize defaults on Professional+ | External Team (Professional+) | Free roles; custom on Premium+ |
| Asana | Custom on Enterprise | Guest seats with limited access | Enterprise for fully custom |
| ClickUp | Permission tiers + Custom (Business+) | Guest accounts (Unlimited+) | Business and above for custom |
| Monday | Custom on Enterprise | Viewer seats | Enterprise for custom |
| Notion | Page-level + Group-based | Guest access on workspace pages | Plus and above for full controls |
The pattern: most tools support permissions; custom roles are usually an enterprise-tier feature. Quire's custom-role support on the Premium tier (one step below Enterprise) is the unusual part of this row.
Customizing the permission roles is only available in Professional, Premium, Enterprise plans. More information can be found at our Pricing page.
On the Organization Members settings page, scroll down to the Permission Control section to customize what each permission role can do. Click the pen icon on the right-hand side.
The Admin role cannot be edited or deleted.
To change the customize permission role back to the default settings, click Reset to default and select a role you want to change back to.
Of course, the default roles cannot be enough if you are working on a complicated project. You can add new roles to your organization. The good news is you can add as many roles as you wish! Stay creative!
Creating new permission roles is only available in Premium, Enterprise plans. More information can be found at our Pricing page.
When you want to outsource your tasks to other team members without giving them the full access to your projects, you can create an External team. The External team can only view and manage the tasks that are assigned to them.
External team is only available in Professional, Premium, Enterprise plans. More information can be found at our Pricing page.
That's all for today's blog post. For more details, you can visit our guide.
If your Quire organization has more than five members, the default roles usually need at least a small tweak. Pick the project where the role question is most contentious (usually the one with cross-team collaborators), customize the Limited or Normal role to match what your team actually needs, and test with one person before rolling it out. Most permission setups settle within an afternoon once you've tried one configuration on a real project.