Client
Sees only their own translation jobs.
- Pages
- Home, My translation jobs, Translated files, Invoices, Style & glossary, Your team
- Can start
- Submit a job, New translation job
A translation and localization portal is where clients submit jobs with their source files and follow each one to delivery, and the agency hands back translated files on the job that asked for them.
Pattern: RequestsDescribe it to Pory
“We're a translation agency. Clients should submit jobs with source files and a target language, see each job's status, and download the translated files when we deliver.”
My translation jobs
| Does "drop" mean a new release or a price cut? | Fall campaign landing pages | Oct 19, 2026 | Open | |
| Keep the app name in English in the store title? | App store listing | Oct 21, 2026 | Open | |
| Can "free cancellation" stay in the German emails? | Fall campaign emails | Oct 8, 2026 | Answered |
Showing 1–3 of 3
In plain English
Pory gives every client and project manager a sign-in of their own. Each client sees only their own translation jobs. It covers job submission & delivery. Translation jobs, deliveries, questions from linguists, invoices and team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Jobs used to arrive as an email with six attachments, no deadline and "the usual languages, please". In Pory the client uploads the source files, picks the target language and content type, and sets the due date. Project managers can quote straight away instead of writing back for the missing details.
Clients chased deadlines by email because the only status lived in the project manager's head. Each client sees their own jobs move from Received and Quoted through In translation and Proofreading to Delivered. A launch team in another time zone checks the portal instead of waiting for your office to open.
Deliveries went out as attachments that sank among the client's other suppliers' emails. The project manager uploads the translated files to the job in Pory, labeled by language, and the client downloads them from their own page. Nobody asks for the German files to be sent again in launch week.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own translation jobs.
Sees every translation job in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Upload and view files on the record they belong to, not in a folder named FINAL v2.
“Where's my request?” answered as a progress bar on the submitter's own page.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited clients.