Client portal for translation & localization agencies

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: Requests

Describe 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.”

Viewing as

My translation jobs

My translation jobs

Questions from your linguists

Does "drop" mean a new release or a price cut?Fall campaign landing pagesOct 19, 2026Open
Keep the app name in English in the store title?App store listingOct 21, 2026Open
Can "free cancellation" stay in the German emails?Fall campaign emailsOct 8, 2026Answered

Showing 1–3 of 3

Due dates — October 2026

MonthWeekToday
ReceivedQuotedIn translationProofreadingDeliveredCanceled
Sun
Mon
Tue
Wed
Thu
Fri
Sat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Powered by Pory

In plain English

How Pory sets it up

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

01

Clients send source files, target language and deadline in one go

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.

Forms to submit a recordDone by: Client
02

Clients follow each job from translation to proofreading to delivered

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.

Status tracker for the submitterDone by: Client
03

Translated files come back attached to the job that asked for them

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.

File attachmentsDone by: Project manager

Who sees what in a translation & localization portal

Every person signs in to their own view. This is what each role in the demo gets.

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

Project manager

Sees every translation job in the portal.

Pages
Home, Deliveries, Jobs board, Due dates, Invoices, Team
Can start
Deliver files

What’s in the translation & localization portal template

The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.

Translation jobs

  • Job (text)
  • Source files (file)
  • Target language (choice: French, German, Japanese, Spanish (Latin America), Brazilian Portuguese)
  • Content type (choice: Marketing, Legal, Software strings, Technical manual)
  • Due date (date)
  • Client (link)
  • Status (choice: Received, Quoted, In translation, Proofreading, Delivered, Canceled)
  • What happens next (text)
  • Words (number)
  • Quote ($) (number)
  • Linguist (link)
  • Instructions (long text)

Deliveries

  • Name (text)
  • Client (link)
  • Job (link)
  • Language (choice: French, German, Japanese, Spanish (Latin America), Brazilian Portuguese)
  • Delivered (date)
  • Translated files (file)

Questions from linguists

  • Question (text)
  • Job (link)
  • Answer by (date)
  • From (link)
  • Client (link)
  • Status (choice: Open, Answered)
  • Your answer (long text)

Invoices

  • Invoice (text)
  • Job (link)
  • Issued (date)
  • Due (date)
  • Amount ($) (number)
  • Client (link)
  • Status (choice: Issued, Paid, Overdue)

Team

  • Name (text)
  • Role (text)
  • Specialty (text)
  • Based in (text)

The parts behind this portal

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

Collect

2 parts
  • Forms

    Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

  • File attachments

    Upload and view files on the record they belong to, not in a folder named FINAL v2.

Decide

1 part
  • Status tracker

    “Where's my request?” answered as a progress bar on the submitter's own page.

Control

3 parts
  • Who sees which records

    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.

  • Passwordless sign-in

    A sign-in link by email, by default. Password sign-in if you'd rather.

  • Your brand

    Your domain, your colors, your logo. Members see you.

Frequently asked questions

A client signs in with a link sent to their email and lands on Home. They see Home, My translation jobs, Translated files, Invoices, Style & glossary and Your team, and only the translation jobs that are theirs. From there they can use “Submit a job” and “New translation job”.

You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.

Build your translation & localization portal with Pory

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.

See pricing · How Pory builds a portal