Skip to main content

Lokalise Vantage: Portal

Learn how to use the Lokalise Vantage Portal to invite users, submit translation requests, upload files, track request status, and download translated content.

Written by Ilya Krukowski

The Lokalise Vantage Portal is a feature within the Vantage workspace that allows stakeholders to request translations without accessing the full Lokalise interface. It acts as a self-serve request interface for teams such as marketing, legal, or content, enabling them to submit content for translation without learning a TMS.

Requests can include AI-only translation or AI + human review, depending on your team’s setup. The localisation team configures the workflow once, and incoming requests are processed automatically based on those settings.

Instead of working with projects, editors, or files directly, portal users simply submit translation requests. This makes it easier for non-localisation teams to request translations, while localisation managers retain control over quality, workflows, and review.

When to use Portal vs Vantage projects

  • Use the Portal when you want to enable simple, ad-hoc translation requests from stakeholders who are not part of the localisation workflow. This is ideal for teams like marketing, legal, or content who just need to submit files and get translations without working in Vantage directly.

  • Create a Vantage project when you need more control over the process. This is better suited for recurring workflows, structured content, or cases where you want to manage files, tasks, contributors, and settings directly within the Vantage workspace.

In short, the Portal is designed for ease of use and accessibility, while Vantage projects are designed for control and flexibility.


Request creation settings

You must be at least a team admin to access the Requested content page.

Before inviting stakeholders to use the Portal, a localisation champion configures how incoming requests should be handled. These settings define the workflow that will be applied to future requests, including the available translation modes, review behaviour, and reviewer assignment rules.

To get started, proceed to Requested content and click Request creation settings:

Choose which workflows requesters can use

In Request creation settings, you can decide which workflow options stakeholders will be allowed to choose when submitting a request.

Available options include:

  • Instant AI translations — the request is translated using translation memory, glossary, and Pro AI, then made available for download once processing is complete. This is best for internal or lower-risk content where speed is the main priority.

  • Reviewed AI translations — the request is translated using translation memory, glossary, and Pro AI, then evaluated with AI-powered quality checks. Segments that fall below the selected review threshold are routed to human reviewers before the file is marked as complete.

You can make both options available, allowing requesters to choose per request, or you can restrict the Portal to just one workflow. These workflow types follow the same logic as the workflows available during project setup in Vantage.

The settings described below apply only to the Reviewed AI translations workflow. When Instant AI translations is used, no additional configuration is required.

At the moment, the only available configuration for Reviewed AI translations is automatic assignment of reviewers.

Configure Automatic assignment for Reviewed AI translations

When Reviewed AI translations is enabled, you can configure Automatic assignment to automatically assign review tasks to contributors based on predefined rules.

Define the expected base language

First, define the expected base language for incoming requests.

This is the source language that Portal requests are expected to use. For example, if your team typically submits English content, you can configure English as the expected base language.

When a request uses this language, it will follow the settings defined for that language group. If a request uses a different base language, a separate fallback configuration can be used instead.

In the current version, the Portal does not detect whether the uploaded file actually matches the selected base language. If the requester chooses the wrong base language, the file will still be processed using that selection.

To help reduce errors, the language picker prioritizes the base languages configured by the localization team, making it easier for requesters to select the correct option.

Set the review scope

Next, you can define the review scope for the Reviewed AI translations. The review scope determines which segments are sent to human reviewers. This works in the same way as review scope during normal Vantage project setup.

The decision is based on AI LQA (Linguistic Quality Assurance). Instead of showing a numeric score, Vantage evaluates segments based on translation issues such as:

  • accuracy

  • fluency

  • terminology

These issues are classified by severity, such as:

  • critical

  • major

  • minor

Segments that do not contain issues at or above the selected threshold are automatically approved and do not appear in review tasks. This allows you to control how much content goes to reviewers while keeping the workflow efficient.

Configure automatic reviewer assignment

You can assign default reviewers for one or more target languages.

When a request creates review tasks, reviewers are assigned automatically based on these rules.

For example, you can assign:

  • German reviewers for de and de_de

  • Spanish reviewers for es and es_es

  • French reviewers for fr

Fallbacks

You can also define a fallback reviewer for any target languages that are not explicitly configured. If a requester selects a language outside of your defined rules, the request will be assigned to this fallback reviewer.

In addition, if a request is submitted with a base language different from the expected one, you can define a separate set of rules for handling those cases, including:

  • review scope

  • reviewer assignment

  • fallback handling

This ensures that all requests are processed correctly, even when they don’t match your primary configuration.

Save and apply settings

Once your configuration is complete, click Save. These settings apply to all future requests submitted through the Portal. Changes do not affect requests that are already in progress.

Reviewer experience

When a request includes human review, reviewers are assigned automatically based on the Portal settings.

Reviewers receive an email notification with a direct link to their task. The request-based project also appears in their Projects dashboard, just like any other Vantage project.

From there, reviewers can open the project, access tasks from the Tasks tab, and review translations in the editor.

The review process works the same as in standard Vantage projects. For more details, see the Lokalise Vantage: Editor guide.


Invite users to the Portal

You must be at least team admin to access the Requested content page.

Portal users are invited from the Requested content page.

To invite someone:

  1. Open the Requested content page.

  2. Click Invite to portal.

  3. Enter one or more email addresses.

  4. Send the invitation.

Each invited user receives an email with a link to join the portal. After following the link, they create a password and gain access to the portal interface.


Portal access model

Three types of users can interact with the Portal, each with different access levels. This determines who can request translations, who manages the portal, and who has access to Vantage projects.

Admins and team owners

Admins and team owners have full access to Vantage and automatically get access to the Portal when it is enabled. They do not submit requests through the Portal. Instead, they manage it from the administrative side.

They can:

  • configure workflows and request behavior

  • invite or remove portal-only users

  • monitor requests and progress

  • access projects, editor, and assets

Team members

All team members automatically have access to the Portal. They can open the Requested content page and submit translation requests without needing an invite.

They can:

  • create and track their own requests

  • access Vantage projects if added as contributors

Portal access is enabled by default for all team members and cannot be disabled separately.

Portal-only users (invited)

These are external stakeholders invited via email. They get access only to the Portal interface and do not see projects, editor, or other parts of Vantage.

They can:

  • submit requests

  • track request status

  • download completed translations

Portal users cannot access:

  • Lokalise Vantage or Expert projects

  • Editor

  • Files

  • Tasks

  • Translation assets

Portal role

Users invited through the portal are added to the team with a special Portal role.

This role has several important characteristics:

  • it cannot be changed to another team role

  • portal users cannot become members, admins, billers, or owners

  • portal users do not consume advanced seats

  • their access is limited to submitting and managing translation requests

Identifying Portal users

To see who currently has Portal access:

  • click Invite to portal

  • then click the X users link in the dialog

You will see a list of portal-only users and can remove them if needed.

Alternatively, you can find them on the Team members page (under Team settings) by filtering for users with the Portal role.

Note

Team members already in your workspace can access the Requested content page by default and are not listed in this dialog. The Portal users list only includes users who were explicitly invited to the portal and do not yet have a full team role.

Summary

  • Admins manage the Portal but do not use it to submit requests

  • Team members automatically get Portal access and can submit requests

  • Portal-only users have limited access focused only on requests and downloads


Submit a translation request

Requesters can only see their own requests in the Portal. They do not have visibility into requests submitted by other users.

Admins and team owners, however, can see all requests across the team from the Portal back office.

To request a translation, portal users click Request translation.

The request form consists of two steps.

Step 1: Request details

First, the requester provides basic information about the translation request.

Fields include:

  • Request name — a descriptive name for the request.

  • Base language — the language the content is written in.

  • Target languages — one or more languages to translate into.

  • Translation type

    • Instant AI translations — translations are generated automatically and delivered quickly.

    • Reviewed AI translations — translations are generated automatically and then reviewed based on predefined quality rules. Segments that require attention are routed to human reviewers before completion.

When using Reviewed AI translations, the localisation team defines the workflow, quality thresholds, and reviewer assignment in advance. Requests are then processed automatically based on these settings, ensuring consistent quality without adding complexity for requesters.

Step 2: Upload files

Next, the requester uploads the files that should be translated. File size cannot exceed 50 MB.

Supported formats include:

  • HTML

  • DOCX

  • PPTX

  • IDML

  • MD

Files can be uploaded by clicking the upload area or by dragging and dropping them.

Once the files are uploaded, the requester clicks Submit request.

After submitting a request

After submitting the request, the user is redirected to the request details page.

This page shows:

  • base and target languages

  • number of uploaded files

  • approximate word count

  • request author

  • translation status

Each uploaded file appears in a list with its current status (for example, In progress or Done). Users can also upload additional files to the request if needed.

Updating files in a request

Requesters can upload additional files or updated versions of existing files to the same request.

  • If you upload a file with the same name as an existing one, Vantage will detect the changes and process only the updated (diff) segments. Existing translations will be reused where possible.

  • If you upload a file with a different name, it will be treated as a new file and processed from scratch.

This allows you to update content without restarting the entire workflow while keeping translation progress intact.


View requests

Portal users can access the Requests page from the left navigation. This page displays all requests they have submitted.

For each request, the page shows:

  • request name

  • translation status

  • languages

  • approximate word count

Users can expand a request to view individual files or click Open request to see request details.


Non-portal users with at least team admin role can view all the submitted requests from the Requested content page that shows similar information.


Download translated files for completed requests

Once translation is complete and all the corresponding tasks are closed, the request status changes to Done and the requester receives an email notification informing them that the translated files are ready to download.

At that point, users can download translated files directly from the request list or the request details page.


How requests are handled internally

When a portal user submits a request, Vantage automatically creates and runs the required translation workflow in the background.

This typically includes:

  • creating a dedicated Vantage project for the request

  • starting AI translation using translation memory and glossary

  • creating review tasks if the selected workflow includes human review

Each request is processed based on the Portal settings defined by the localisation team, including workflow type, quality thresholds, and reviewer assignment.

Once submitted, the requester can track progress from their request dashboard and download the translated files when processing is complete.

Meanwhile, the localisation team has full visibility and control within Vantage — they can access the underlying project, review translations, manage tasks, and make adjustments if needed.

Did this answer your question?