Imagine your company carries out two jobs for the same manufacturer. One is at its northern plant and the other at its southern plant. You need two projects, but you do not need two copies of the customer.
Four names, four different jobs
- Workspace: the working area that brings your organization’s records together.
- Client: the customer you work for.
- Site: the physical location, such as the northern plant.
- Project: a defined job, such as upgrading that plant’s packaging line.
Check what already exists
Search Clients for the manufacturer before adding it. Use the customer’s recognizable name, and distinguish locations by plant or city. A new contract with the same customer usually calls for another project, not another customer entry.
Organize the next job
- 01
Open Clients and find the existing customer. If it is genuinely new, create its record in the correct workspace.
- 02
Write the actual plant or location in the project title or description. The current creation form asks for the client and category; you do not need to create each internal level by hand.
- 03
Create the project, select that client and category, and name the work itself: for example, Northern plant — packaging-line upgrade.
- 04
Before inviting the team, reopen the project and check the customer and location shown in its context.
Can a colleague tell the jobs apart?
Someone scanning the project list should be able to distinguish the two jobs without opening every card. Keep customer names consistent and project titles specific. The structure is useful when it helps you find the right work, not when it creates more entries to maintain.
Avoid confusing duplicates
- Two spellings for one customer? Inspect the existing records before adding a third.
- An invitation is not a customer record. People’s project access must still be set separately.
- If a busy project is linked incorrectly, review its current relationships before changing them; do not delete records just to tidy the list.
Frequently asked questions
Do project categories replace clients?
No. A category describes the kind of work; a client identifies who it is for.
Should I put every project into a separate workspace?
Not simply because it is a new job. Use a separate workspace when you need a genuinely separate organizational context.
Does adding a client give that customer access?
No. A client entry does not sign anyone in or grant project membership.
Can I put confidential commercial terms in the project title?
Avoid it. Use a short operational title and keep sensitive details in the appropriately restricted section.