> ## Documentation Index > Fetch the complete documentation index at: https://docs.simpleuat.com/llms.txt > Use this file to discover all available pages before exploring further. # How SimpleUAT is organized > Org to project to environments, personas, suites, cases, cycles, runs. Recipients use applications, inbox, and archive. Think folders, not a new science. ## Your side (doing the testing) **Organization:** the company or freelance account you signed in with. Team members, billing, a Delivery ID for *receiving* work live here. [Organization](/account/organization). **Project:** one job. Types: `web` | `ios` | `android` | `admin_portal` | `api` | `wordpress` | `saas` | `other`. Inside a project you can have: * **Surfaces** and **features:** product slices, when you use them * **Environments:** URLs (staging, and so on) * **Personas:** who you log in as * **Suites** and **cases:** the checklist * **Cycles** and **runs:** the round and the execution * **Findings:** bugs That's the spreadsheet workbook, bug tab, and testing-round dates, in a tree you don't have to maintain by hand. ## Their side (receiving UAT) When you deliver, the client (recipient) sees **Applications** (UI for products), **Providers**, **Portfolio**, **Inbox**, **Archive**. You may also use **Clients** and **Deliver UAT** on the provider side. You often only need a **project** plus a **connection**. Don't create an Application unless you're actually on the receiving/product catalog workflow. [Projects vs products](/concepts/projects-products). ## Sidebar labels you'll see Dashboard, UAT Inbox, Projects, Test Suite Packs, Deliver UAT, Clients, Applications, Providers, Findings, Test Suites, Test Cycles, Test Runs, Assignments, Environments, Personas, Import, Reports & Quality, Retest requests, Receiving UAT, Team Members, Integrations, Billing & Plan. Not every item appears for every role or plan. Checklist in the project vs reusable catalog. The round vs the execution.