Question 1

What's the first thing I should set up in Quire?

Accepted Answer

Start by creating an organization, which is the top-level workspace in Quire. Use the Add Organization guide to set that up first, since every project needs to live inside an organization. Once the organization exists, create your first project inside it using the Add Project guide. With the organization and project in place, you can invite your team, either at the organization level so members can access every project, or at the project level for access to just that one project. After members are in, the last step is bringing in any existing data through copy and paste, a Quire CSV file, or a JSON import, or simply skipping that and adding tasks manually. Following this order, organization, then project, then team, then data, gives you a working workspace ready for daily task tracking.

Question 2

What's the difference between an organization and a project in Quire?

Accepted Answer

An organization is the top-level workspace in Quire and can hold multiple projects, while a project lives inside a single organization and is where you actually create and manage tasks. Setting up a new workspace starts with creating the organization first, since a project cannot exist without one, then adding a project inside it. This structure also affects how you organize and find your work: you can group related projects inside an organization using Folders, or use Smart Folders to group projects together across multiple organizations into a single view. Membership works at both levels too. Organization Members controls access across every project in that organization, while Project Members controls access to a single project only. Understanding this distinction matters when deciding who to invite and at what level, and when deciding how to structure folders and smart folders for navigating your projects later.

Question 3

Do I need to invite my team before or after creating a project?

Accepted Answer

Either order works in Quire. There is no required sequence that forces you to invite members before or after creating a project. That said, many teams find it easier to first create the organization and the first project, getting the basic workspace structure in place, and only then invite members once that structure is ready for people to join. This way, new members land in a workspace that already has its organization and project set up rather than an empty shell. When you are ready to invite people, you can do so at two levels: use Organization Members to give someone access across every project in the organization, or use Project Members to limit their access to a single project. Either approach, inviting early or inviting after setup, ends with the same end state: an organization, a project, and a team that can start assigning and tracking tasks together.

Question 4

Can I invite members at both the organization and project level?

Accepted Answer

Yes. Quire lets you manage membership at two separate levels. Organization Members controls access across every project within that organization, so anyone added there can potentially work across all the projects it contains. Project Members, on the other hand, controls access to a single project only, so you can add someone to one specific project without giving them visibility into everything else in the organization. This two-level system is useful when setting up a new workspace: you might invite a core team at the organization level so they can move between projects freely, while inviting external collaborators or clients only to the specific project they need through Project Members. You can set up either level first, there's no required order, and you can keep adjusting membership at both levels as your organization grows and adds more projects over time.

Question 5

Can I bring in tasks from another tool when I set up Quire?

Accepted Answer

Yes. Quire supports three ways to bring in existing data when you are setting up a new workspace. You can copy and paste directly from a spreadsheet or list for a quick manual import, upload a Quire-formatted CSV file if you already have one exported, or import a JSON file when migrating structured data from another project management tool. All three options are meant to save you from having to manually recreate tasks one by one after switching tools. This step fits naturally after you have created your organization and project and invited your team, since importing populates the project with real task data right away. If none of these methods fit what you're moving from, or you simply don't have existing data to bring over, importing is entirely optional and you can skip it and add tasks manually instead.

Question 6

Which import method should I use when moving from another tool?

Accepted Answer

Which import method fits best depends on what data you're starting with. Use copy and paste for a quick manual import when you have a spreadsheet or a simple list you want to bring into a project without much setup. Use a Quire CSV file if you already have a Quire-formatted export, for example from another Quire project or organization, since that format maps directly to Quire's structure. Use a JSON file when you are migrating structured data from another project management tool entirely, since JSON can preserve more complex relationships between tasks than a flat spreadsheet or CSV can. All three import options exist so you don't have to manually recreate your existing tasks after setting up a new organization and project. If none of them match your situation, importing is optional and you can always add tasks manually instead.

Question 7

Can I skip the import step if I don't have existing data?

Accepted Answer

Yes. Importing existing data is entirely optional in Quire's workspace setup. If you don't have tasks sitting in a spreadsheet, a CSV export, or another project management tool, there's nothing you need to bring in, so you can skip the import step altogether. Instead, you can go straight from creating your organization and first project to inviting your team, and then start adding tasks manually inside the project as work comes up. This is a normal path for teams that are starting fresh rather than migrating from an existing system. If you later end up with data you want to bring in, whether through copy and paste from a spreadsheet, a Quire CSV file, or a JSON file, those import options are still available at any time, not just during initial setup.

Setting Up Your Workspace in Quire Permalink

Create Your Organization and First Project

Invite Your Team

Bring In Existing Data

Organize Your Sidebar

Frequently Asked Questions

What’s the difference between an organization and a project in Quire?

What’s the first thing I should set up in Quire?

Do I need to invite my team before or after creating a project?

Can I invite members at both the organization and project level?

Can I bring in tasks from another tool when I set up Quire?

Which import method should I use when moving from another tool?

Can I skip the import step if I don’t have existing data?