Vendor portal and authentication

Change the vendor portal language

Switch to an available CRM language. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Vendor contactsPermission: Authenticated active vendor contact and enabled portalModule v1.7.9

Jump to steps

Where to goVendor Portal → Language

Before you start

Use an account with Authenticated active vendor contact and enabled portal and confirm the intended record or setting before making a change.
Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What you’ll accomplish

Switch to an available CRM language. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

Go to Vendor Portal → Language.
Go to the exact setting, option or record named in this guide.
Enter or select the required value; leave unrelated options unchanged.
Save the form and wait for the success response.
Reload the page or open a controlled record to confirm the stored value is being used.

Fields and options to review

Vendor identityCompany/name, code, tax/VAT, phone, website, category/group, address and status as exposed by the vendor form.

Contacts and accessVendor contacts, vendor administrators, portal status, language and welcome/notification settings where applicable.

Rules the system enforces

Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication.

How to confirm it worked

The supported change the vendor portal language flow completes without bypassing permission or validation checks.
The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
Test settings and automated jobs with controlled records before production-wide use.

Was this guide useful?Your response is stored only in this browser.