Skip to main content
Two words that sound like “the thing we’re testing.” They are not the same screen.

Project

Where you build suites, run tests, and log findings. Create Client Project / Create First Project. Type is the platform (web, ios, and so on). This is the job folder.

Application / product

On the recipient side, Applications is the UI for products they hold in a portfolio. Portfolio, Inbox, Archive, Providers sit with that world. That’s “we receive UAT packets about our products,” not “freelancer test execution.”

What you should do

If Acme hired you to test checkout: one project. Connect Acme as a client/recipient. Deliver. You do not need to model Acme’s entire product catalog as Applications in your org. If you are the client org receiving a freelancer’s delivery, you’ll spend time in UAT Inbox, Receiving UAT, Applications, and review actions.
Copy in the app sometimes says “product” in empty states and “Applications” in nav. Same mismatch we document internally. When in doubt, execution = Projects.

How it's organized

Full hierarchy.

Connect a client

Delivery ID, code, invitation.