Question 1

What's the difference between Permission Roles and feature-specific permissions in Quire?

Accepted Answer

Permission Roles are the general roles in Quire that control access at the project and organization level, setting what a member can do across a workspace overall. Feature-specific permissions add a narrower layer on top of that for particular tools: Document Permission controls access to documents, Sublist Permission controls access to sublists, Chat Permission controls access to chat, and Insight Permission controls access to insights. Each of these four settings is configured separately from Permission Roles and from one another, so an admin can grant broad project access through Permission Roles while still restricting or opening up one specific feature on its own. In practice, you set the overall access level first with Permission Roles, then fine-tune document, sublist, chat, and insight access as needed. This two-layer approach lets an organization apply one general access policy while still tailoring individual features to different teams or roles.

Question 2

Where do I control what different members can see or edit in Quire?

Accepted Answer

Start by setting overall access with Permission Roles, which control what members can do across a project and organization. From there, check the feature-specific permission settings for anything that needs finer control: Document Permission for documents, Sublist Permission for sublists, Chat Permission for chat, and Insight Permission for insights. Each of these four is configured on its own, separate from Permission Roles, so you can open up or restrict one feature without changing a member's overall project access. This layered setup is useful when a member needs broad visibility into a project but should not edit certain documents, or when a team should see chat but not insights. Review Permission Roles first for the big picture, then work through the feature-specific settings one at a time to match what each member or team actually needs to see or edit within the workspace.

Question 3

Can I set different permissions for documents than for chat in Quire?

Accepted Answer

Yes. Document Permission and Chat Permission are two separate, feature-specific settings in Quire, so adjusting one does not affect the other. You can restrict who can view or edit documents through Document Permission while leaving Chat Permission open, or the reverse, depending on what a team needs. This separation exists because documents, sublists, chat, and insights each have their own dedicated permission setting, sitting alongside the broader Permission Roles that control general project and organization access. Configuring them independently means an admin can, for example, keep a project's chat open to every member for general discussion while limiting document access to a smaller group working on sensitive material. Because each feature-specific permission is managed on its own screen, changes to Document Permission take effect only for documents, and changes to Chat Permission take effect only for chat, with no overlap between the two.

Question 4

Does Quire support logging in through our company's identity provider?

Accepted Answer

Yes. Quire offers Single Sign-On (SSO), which lets your organization's members log in using your company's identity provider instead of a separate Quire username and password. This means access to Quire can be managed through the same identity system your organization already uses for other tools, rather than maintaining a distinct set of Quire credentials for every member. SSO falls under Quire's access security features alongside IP Allowlists, giving organizations more than one way to control and secure how members reach a workspace. Setting up SSO is handled separately from Permission Roles and the feature-specific permissions for documents, sublists, chat, and insights. Those settings still determine what a member can do once logged in. SSO simply governs how they log in in the first place, making it a login-security layer rather than an access-level or content-permission control within the workspace itself.

Question 5

Can I restrict Quire access to specific IP addresses?

Accepted Answer

Yes. Quire supports IP Addresses Allowlists, which restrict workspace access to a set of approved IP addresses that you specify. Any login attempt coming from an IP address not on the allowlist can be blocked, which is useful for organizations that want to limit Quire access to a corporate network, office location, or VPN. IP Allowlists sit alongside Single Sign-On (SSO) as one of the two access-security controls covered on this page, and the two are configured independently of each other. IP Allowlists control where a login can come from, while Permission Roles and the feature-specific permissions for documents, sublists, chat, and insights control what a member can see or edit once they are already logged in. Setting an IP Allowlist does not change any of those permission settings. It only adds a network-level restriction on top of them.

Question 6

Can I use SSO and still restrict access by IP address in Quire?

Accepted Answer

Yes. Single Sign-On and IP Allowlists in Quire are configured independently of each other, which means you can turn on both at the same time for layered access control. SSO handles how members log in, routing authentication through your organization's identity provider instead of separate Quire credentials. IP Allowlists handle where a login can come from, restricting access to a set of approved IP addresses such as a corporate network or VPN. Combining both means a member must both authenticate through your identity provider and connect from an approved IP address before reaching the workspace, which is stronger than relying on either control alone. Neither setting affects Permission Roles or the feature-specific permissions for documents, sublists, chat, and insights. Those still separately determine what a member can see or edit once they have successfully logged in through SSO and from an allowlisted IP address.

Question 7

Where do I manage billing for my organization?

Accepted Answer

Organization billing in Quire is managed through the Billing and Payment settings, where you handle your subscription plan and payment details in one place. This is separate from Permission Roles and the feature-specific permissions for documents, sublists, chat, and insights, as well as from the access-security settings for Single Sign-On and IP Allowlists. Billing and Payment covers the administrative and financial side of running a Quire organization, rather than what members can see, edit, or how they log in. If you are setting up a brand-new workspace rather than managing an existing one, the related page on Setting Up Your Workspace covers the initial setup steps. For ongoing administration, Billing and Payment is where you go whenever you need to review or update your organization's subscription and payment information.

Securing and Administering Your Quire Workspace Permalink

Set Permissions

Secure Access

Manage Billing

Frequently Asked Questions

What’s the difference between Permission Roles and feature-specific permissions in Quire?

Where do I control what different members can see or edit in Quire?

Can I set different permissions for documents than for chat in Quire?

Does Quire support logging in through our company’s identity provider?

Can I restrict Quire access to specific IP addresses?

Can I use SSO and still restrict access by IP address in Quire?

Where do I manage billing for my organization?