Last updated: July 22, 2026
Quire organizations have five member roles. Admin, Normal+, and Limited+ can access every project in the organization; Normal and Guest cannot. Both Normal+ and Normal can add projects and become Admin of what they create, but Normal members can't open projects they aren't part of. It is Quire's way of scoping who sees what.
Clear roles are not only about security. Gallup found that only about half of employees strongly know what is expected of them at work, and defining who owns and sees what is a big part of closing that gap.

We made a few enhancements in our organization member roles.
Both Normal+ and Normal members can add projects in an organization, and when they do, they become Admins of the projects. The only difference is that Normal members cannot access other projects that they are not members of.
Related: Master Organization: Save on Your Quire Subscription — see how grouping organizations under a master organization interacts with member roles and billing.
In summary, Admin, Normal+ and Limited+ members of an organization can access all projects in this organization. Normal and Guest members cannot.
For more details on roles & permissions, you can check out here.
Related: 5 Easy Steps to Quire's External Team — for outside collaborators like freelancers, Quire's External Team feature offers another way to grant limited project access beyond the Guest role.
Five roles, one question that matters most: who can open what. Here it is in one view.
The practical upshot is control without micromanagement. Give a department head Normal+ and they can spin up and run projects on their own. Give an outside stakeholder Guest and they see only what you hand them. Normal sits in between: people who create and own their own work but shouldn't be browsing everyone else's. Picking the right role up front saves a lot of "who can see this?" questions later.
Why have this many roles at all? Because "everyone can see everything" stops working the moment an organization has more than one team. A marketing lead does not need to browse the engineering backlog, and a contractor certainly should not. Roles let you match visibility to responsibility without setting up a separate organization for every group. The two middle roles do most of the day-to-day work: Normal+ for people you trust to run their own projects and see across the org, and Normal for people who should own their work but stay in their lane. Guest and Limited+ handle the edges, the outsiders and the special cases. Set the role when you invite someone and the access question answers itself from then on. One more practical note: adding a project always makes the creator its Admin, whatever their organization role. So a Normal member who starts a project runs that project fully, they just cannot wander into projects they were never added to. That combination, full ownership of your own work and a closed door on everyone else's, is what keeps a growing organization from turning into a free-for-all where every new hire can read every plan on day one. It is a small setting with an outsized effect on how safe your workspace feels as the team scales. If you are unsure which role fits, start people at Normal and promote them to Normal+ only when they genuinely need the wider view.
Admin, Normal+, and Limited+ can access all projects in the organization. Normal and Guest members cannot.
Both can add projects and become Admins of what they create, but Normal members can't access other projects they're not part of.
They automatically become an Admin of that project.