The Lokalise Vantage Portal is a feature within the Vantage workspace that allows external stakeholders to request translations without accessing Lokalise projects or the full Lokalise interface.

It is designed for trusted users outside your Lokalise team, such as people in marketing, legal, support, or content teams who only need to submit content for translation and download the results.

The localization team controls whether new requests can be submitted and which translation workflows are available. Depending on the configuration, Portal users can request Instant AI translation, AI + human review, or choose between both.

Portal users do not need to work with projects, contributors, tasks, or the editor. They simply upload content and submit a translation request, while the localization team manages the translation workflow, quality settings, and review process in Vantage.

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

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:

Use the New requests setting to control whether Portal users can submit new translation requests.

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

Available options include:

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

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

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.

Next, define the review scope for Reviewed AI translations. The review scope determines how much translated content is sent to human reviewers and works in the same way as review scope in standard Vantage projects.

Available options are:

For the narrower review scopes, Vantage uses translation issues detected by AI and their severity to determine which content needs human review. Vantage does not use a numeric quality score or score threshold for this process.

A broader review scope sends more content to reviewers, while a narrower scope reduces the amount of human review.

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:

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:

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

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.

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.

Portal users are invited from the Requested content page.

To invite someone:

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.

The Vantage Portal is designed for external stakeholders who are not members of your Lokalise team.

Portal access is separate from access to Vantage projects. Different rules apply depending on whether a person is already a Lokalise team user.

Team owners, admins, and billers can access Requested content, manage Portal settings, and invite external users to the Portal.

They do not submit translation requests through the Portal. To upload content for translation, they can create or use regular Vantage projects instead.

Regular Lokalise team members cannot be added as Portal users or submit new translation requests through the Portal. Their access to content and translation workflows is managed through Vantage projects and project permissions instead.

For example:

If you try to invite someone who already belongs to the Lokalise team, Vantage will indicate that the user is already a team member.

Users who are not members of your Lokalise team can be invited to the Portal. This is useful for trusted stakeholders who only need to:

Portal users do not need access to Vantage projects, tasks, contributors, or the editor.

Whether they can submit new requests depends on the New requests setting configured by the localization team. If new requests are disabled, Portal users can still:

However, they cannot upload new content or submit new translation requests.

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

This role has several important characteristics:

Whether Portal users can submit new requests depends on the New requests setting.

To see who currently has Portal access:

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.

When New requests is enabled in the Portal settings, Portal users can click Request translation to submit a new request.

The request form consists of two steps.

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

Fields include:

When using Reviewed AI translations, the localization team defines the review scope and reviewer assignment in advance. Requests are then processed automatically based on these settings, without requiring additional configuration from the requester.

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

Supported formats include:

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 the request, the user is redirected to the request details page.

This page shows:

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.

When New requests is enabled, requesters can upload additional files or updated versions of existing files to the same request.

If New requests is disabled, Portal users can still view existing requests and download completed translations, but they cannot upload new or updated content.

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:

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.

Once translation is complete and any required review tasks are closed, the request status changes to Done and the requester receives an email notification 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.

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

This typically includes:

Each request is processed based on the Portal settings defined by the localisation team, including workflow type, review scope, 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.