HighLevel in Portuguese: Give Clients a Portuguese Dashboard

A dental clinic in São Paulo signs up for your platform. The receptionist switches HighLevel to Portuguese, and most of the screen changes. Then part of the Conversations page stays in English, the menu says Assinaturas for the clinic’s membership area and for the payment subscriptions tab alike, and the colors look exactly like the software another agency in town resells. The owner asks two questions: “Isso está mesmo em português?” and “Esse sistema é mesmo de vocês?”

This guide answers both for HighLevel in Portuguese. It covers what HighLevel (also called GoHighLevel or GHL) shows in Portuguese natively today, where the native translation stops, what a branded Portuguese menu adds, how to choose between Brazilian and European Portuguese, which words to use for each industry, how Brazil and Portugal write prices and dates, what Brazil’s LGPD (Lei Geral de Proteção de Dados, the general data protection law) means for demos, why Portuguese SMS often cost more than English ones, and a step-by-step setup. GHL Dashboard Builder is an independent design service and is not affiliated with HighLevel; where our product helps, we say exactly what it does and where it stops.

Can HighLevel be used in Portuguese today?

Yes. HighLevel offers Portuguese as a built-in platform language, and it lists two variants: Portuguese (Brazil) and Portuguese (Portugal). Each sub-account has a default language and each user can choose their own. Where part of the interface has no translation yet, HighLevel shows English, so the result is mostly Portuguese rather than completely Portuguese.

Where the native setting lives

HighLevel’s help center article on internationalization describes two levels of language setting:

1. The sub-account default. In a client’s sub-account, open Settings, Business Profile and choose Platform Language. Everyone in that sub-account sees this language unless they pick another one.
2. The user’s own choice. Each user can open Settings, My Profile and choose their own Platform Language. The user’s choice takes priority over the sub-account default.

A sub-account is one client’s workspace in HighLevel; HighLevel also calls it a location. At the time of writing, the article lists Portuguese (Brazil) and Portuguese (Portugal) as separate entries next to languages such as Spanish, French, German, Italian and Dutch, and it explains that text without a translation falls back to English. That two-variant choice is useful: a team in Lisbon can read HighLevel’s own pages in European Portuguese while a team in Recife reads the Brazilian version.

What Brazilian users have reported

Brazilian agencies are among the most active Portuguese-speaking HighLevel users, and their posts on HighLevel’s ideas board show where the native translation is still thin. One request asks HighLevel to finish the Brazilian Portuguese translation of the Conversations module, calling the inbox one of the main features of any CRM in the Brazilian market and describing its current translation as incomplete. In a separate SaaS-mode thread asking HighLevel to improve translations and allow custom translation, a commenter says the same problem applies to Brazilian Portuguese.

Those reports matter for one reason. Portuguese-speaking clients do not only want Portuguese; they want correct, consistent Portuguese that sounds like their trade and that their agency can fix. At the time of writing, HighLevel’s native setting does not let an agency rewrite its translated labels, so a wrong or ambiguous word stays until HighLevel changes it.

Who reads Portuguese, and why it matters to your agency

Portuguese is the working language of one very large market and several smaller ones. Brazil alone counted about 203 million residents in the 2022 census, according to the first IBGE census results reported by Rádio Senado. Portugal, Angola, Mozambique and the other Portuguese-speaking countries add tens of millions more readers, and Agência Brasil reported Portugal’s then foreign minister estimating about 250 million Portuguese speakers in 2019, with most future growth expected in Africa.

For an agency, that means two things. First, Brazil is a market where a Portuguese dashboard is expected, not a bonus: front-desk staff, sales teams and course creators work in Portuguese all day. Second, the variants are different enough that a dashboard written for Brazil reads slightly foreign in Portugal, and the other way round.

Infographic

Portuguese and your HighLevel clientsby the numbers

203M

residents counted in Brazil's 2022 census

(IBGE, via Rádio Senado)

2

Portuguese options in HighLevel's Platform Language: Brazil and Portugal

(HighLevel Help Center)

56 of 98

menu and tab labels in our Portuguese pack are longer than in English

(GHL Dashboard Builder)

15

dashboard languages in GHL Dashboard Builder, Portuguese among them

(GHL Dashboard Builder)

Sources: IBGE 2022 Census first results, reported by Rádio Senado (June 2023); HighLevel Help Center; GHL Dashboard Builder language packs, counted November 2026.

What does HighLevel show in Portuguese, and what stays in English?

HighLevel’s native Portuguese translates much of the web interface for users who choose it, with English wherever a translation is missing. Your clients’ customer-facing content, such as SMS, WhatsApp messages, emails, forms and funnels, is Portuguese only if someone writes it in Portuguese. Branding and industry wording are not part of the language setting at all.

That split matters before a sale. A client who expects every screen in Portuguese will find English somewhere sooner or later, most often in builders, automations, newer features and validation messages. HighLevel ships changes often, so treat any list of untranslated screens as a snapshot and check the screens your client actually uses.

Why the two layers work together

The native setting and a theme do different jobs. HighLevel’s Platform Language decides the text inside HighLevel’s own pages, for each user. A theme decides how the dashboard looks and what the menu and navigation say, for each sub-account it covers. The best Portuguese setup for most clients uses both: the right Portuguese variant as the Platform Language, so inner pages read in Portuguese where HighLevel has translated them, and a branded Portuguese menu, so the screen the team opens every morning carries your brand and their words.

For Portuguese, as for Spanish, French and German, the value of a theme is not translation from nothing. It is control: your brand, your client’s words, and labels short enough for the sidebar. Our overview of GoHighLevel’s languages compares every language side by side, and our guide to a Spanish GoHighLevel dashboard covers the closest comparable case, including the split between Spain and Latin America.

How does GHL Dashboard Builder put GoHighLevel in Portuguese?

GHL Dashboard Builder translates GoHighLevel’s menu and navigation into Portuguese in your brand, lets you rename any menu item in your own Portuguese wording, can limit the Portuguese design to chosen sub-accounts, and installs as one CSS line and one JavaScript line in HighLevel’s custom code settings. Text inside HighLevel’s own pages keeps following each user’s Platform Language.

GHL Dashboard Builder is an independent design service that turns the standard HighLevel (GoHighLevel) dashboard into a branded platform: your colors, menu, login design, privacy mode and your clients’ language, installed with two lines of code. For Portuguese, the relevant pieces are the built-in Portuguese language pack, the menu editor, sub-account targeting, privacy mode, the templates and the install itself. It is the same approach as our GoHighLevel white label dashboard, with Portuguese as the working language.

What the Portuguese setup includes

• A Brazilian Portuguese pack. The menu, the sidebar’s search and sub-account switcher (“Trocar subconta”), the header search box (“Pesquisar contatos, negócios, conversas…”), notifications, the profile menu (“Meu perfil”), common buttons such as Salvar and Cancelar, and the tab names our theme shows are translated. Menu items read Painel, Conversas, Contatos, Oportunidades, Calendários, Pagamentos, Marketing, Automação, Sites, Assinaturas, Reputação, Relatórios and Configurações. Portuguese is one of 15 languages; 3 of them (Arabic, Urdu and Hebrew) read right to left, and Portuguese uses the normal left-to-right layout.
• The friendly você. Where the pack addresses the user, for example in the setup guide’s greeting (“Olá, {name}! Esta é a sua lista de configuração personalizada…”), it uses você, the standard form of address in Brazilian business software.
• Your own wording. Override any translated label, so a clinic’s team sees Pacientes instead of Contatos, and a European Portuguese client sees Definições instead of Configurações.
• Menu editor. Rename, reorder, hide and badge any of HighLevel’s 19 menu items, and add your own items.
• Privacy mode in Portuguese. The eye button in the header is labelled Modo de privacidade and blurs names, emails, phone numbers, the conversation list and deal values before a screen share.
• Templates. Start from one of 27 templates, then set the language to Portuguese. For Brazilian marketing and coaching clients we often suggest the Pulse template, a high-energy magenta with top navigation, and for course creators the Scholar template, indigo and sunny yellow.
• No data access. The builder never connects to your HighLevel account and the installed code does not send data anywhere.

The language section of the builder is where the switch happens: pick Portuguese, and the preview’s menu and navigation change at once, so you and the client can judge the labels before anything is installed.

At a glance: features, what they do, which plan

All three plans are one-time payments with no monthly fee, plus a one-time $100 setup fee on every plan, for which we install and configure the design in your HighLevel. Starter ($280) gives one branded design from any template, without the language section. Pro ($480) adds up to 3 designs, the menu editor, the dashboard in Portuguese or any of the other 14 languages and the branded login page. Agency ($880) adds up to 100 designs, a look designed by our team, custom CSS and JavaScript and lifetime updates. Starter and Pro include 12 months of updates, then optional at $99 a year. The full list of what each feature does is on our features page.

What the client sees afterwards

After installation, a user in the Portuguese sub-account logs in on your white-label domain and sees the sidebar in your colors with labels such as Conversas, Calendários and Contatos, or the renames you chose, such as Pacientes. When they open a settings page or a builder, they see HighLevel’s own text in the Platform Language they chose: Portuguese for most of the interface and English on screens HighLevel has not translated yet. You can click through a live Portuguese preview on our Portuguese language page.

Brazilian or European Portuguese: which one do your clients need?

Use the variant your client’s staff and customers write every day. Brazilian and European Portuguese share grammar and most vocabulary, but everyday software words differ, and so does the way software addresses the user. A Brazilian menu in Lisbon looks like an import; a European menu in Belo Horizonte looks old-fashioned or foreign.

Words that give the variant away

Here are common pairs agencies meet in a CRM. They are typical usage, not strict rules: some Portuguese companies use Brazilian terms that came with their software, and some Brazilian teams use English loanwords such as Leads, Pipeline and Dashboard at work.

Forms of address: você, tu and no address at all

In Brazil, você is the normal, polite form in software and customer messages, and it is what our pack uses. In Portugal the picture is more delicate. Many Portuguese readers find a direct você slightly distant or awkward in writing, tu is informal, and a lot of software in Portugal avoids addressing the user at all, using infinitives and neutral phrases such as “Guardar alterações” or “Introduza o seu email” instead.

The practical rule: for a Brazilian client, write você everywhere, from the menu greeting to the SMS reminder. For a Portuguese client, ask how they write to their own customers and copy that tone; when unsure, choose neutral phrasing that does not address anyone directly. Whatever you choose, keep it the same in the menu, SMS templates, emails and training material.

How to set up each variant

1. For Brazil, set Platform Language to Portuguese (Brazil) and use our Portuguese pack as it is, with only industry renames.
2. For Portugal, set Platform Language to Portuguese (Portugal), then override the labels that read as Brazilian in the builder: Contatos becomes Contactos, Configurações becomes Definições, and so on. Review the result with someone from the client’s team.
3. For Angola, Mozambique and other markets, ask the client which norm their staff learned and which their customers use; many follow European spelling. Start from the European overrides and adjust.

Which Portuguese words should the GoHighLevel menu use for each industry?

Use short, everyday Portuguese and rename the items where your client’s trade has its own word. HighLevel calls every person a contact and every deal an opportunity in every language, while a clinic thinks in Pacientes, a school in Alunos and a real estate agency in Imóveis. When the menu matches the way the business talks, staff find things faster and training takes less time.

Industry renames in Portuguese

Here are renames agencies commonly choose, based on the industry wording in our templates:

• Dental and medical clinics: Contatos becomes Pacientes, Oportunidades becomes Tratamentos.
• Lawyers and accountants: Contatos becomes Clientes, Oportunidades becomes Processos or Casos.
• Real estate: Oportunidades becomes Imóveis or Negócios.
• Gyms and fitness: Contatos becomes Alunos or Membros.
• Restaurants: Calendários becomes Reservas.
• Home services and trades: Oportunidades becomes Serviços or Orçamentos.
• Beauty and aesthetics: Calendários becomes Agenda or Agendamentos.
• Coaches, schools and course creators: Assinaturas becomes Cursos or Área de membros.

Fix the Assinaturas double meaning first

One rename is worth making for almost every Brazilian client. In Brazilian Portuguese, assinatura means both a membership and a recurring subscription, and our own pack, like most Brazilian translations, uses Assinaturas for HighLevel’s Memberships menu item and for the Subscriptions tab under Payments. For a course creator who sells monthly plans, that means two places called Assinaturas with very different jobs. Rename the Memberships item to Cursos, Área de membros or Comunidade, and the confusion disappears.

Why Portuguese labels need extra care

Portuguese labels are often longer than English ones, because Portuguese tends to use a phrase where English stacks two nouns: Custom Reports becomes Relatórios personalizados and Calendar View becomes Visualização do calendário. We counted the characters in our own Portuguese pack: 56 of the 98 menu, sidebar and tab labels are longer in Portuguese than in English, and some are twice as long. The chart shows the clearest cases.

Configurações globais de fluxos (24)31 characters

Configurações do calendário (17)27 characters

Visualização do calendário (13)26 characters

Relatórios personalizados (14)25 characters

Gerenciador de anúncios (10)23 characters

Armazenamento de mídia (13)22 characters

English character counts in brackets. Source: GHL Dashboard Builder Portuguese and English language packs, counted November 2026.

Three habits keep a Portuguese menu tidy. First, shorten where meaning allows: Armazenamento de mídia can become Arquivos, and Fluxos de trabalho can become Automações or simply Workflows, a word many Brazilian marketing teams already use. Second, hide the items a client never uses, so the menu shows six short words instead of nineteen long ones. Third, check the menu at the width your client actually uses, including a laptop at 125% zoom, where long labels wrap first.

How to choose the words with your client

1. List the items each role uses. A front desk may need only Conversas, Calendários and Contatos. Hide the rest for that client so the menu stays short.
2. Ask what they call each thing today. If a clinic says Pacientes in every meeting, the menu should too.
3. Confirm the variant. Brazil or Portugal, and whether the team uses English loanwords such as Leads, Funil or Pipeline at work.
4. Agree the form of address once, and use it everywhere the client’s customers and staff read.
5. Review with a native speaker on the client’s team before launch, not after.

Our guide to renaming GoHighLevel menu items walks through the menu editor in detail, and the GHL sidebar and menu customization page shows everything you can change in the sidebar.

The menu editor is where those decisions become real: each of HighLevel’s menu items has its own field, so typing Pacientes, Cursos or Imóveis replaces the generic word for every user of that client.

The menu editor writes the same wording into every sub-account the design covers, so the renames above appear for every user of that client. Users who prefer English inner pages can still set their own Platform Language; the menu keeps your Portuguese wording.

How should numbers, dates and prices appear for Brazilian and Portuguese clients?

Brazil writes 12.345,5 with a point between thousands and a comma for decimals, and prices as R$ 1.234,50. Portugal uses a space between thousands and puts the euro sign after the amount: 1234,50 €. Both write dates day first, both use the 24-hour clock, and an English-formatted price such as 1,234.50 looks wrong to readers in either country.

What locale data says

Browsers and most software take number and date formats from the Unicode Common Locale Data Repository (CLDR), a shared database of how each language and country writes numbers, dates and currencies. We checked Portuguese locales in Node.js 22 with ICU 78.3, which ships CLDR version 48:

Four details matter in practice. First, a Brazilian or Portuguese reader sees 1.234 as one thousand two hundred and thirty-four, so an English-formatted price reads like a typo. Second, CLDR’s European Portuguese data does not group four-digit amounts, so 1234,50 € is correct and 1 234,50 € appears only from five digits. Third, month names are written in lower case in Portuguese, as in “13 de novembro”, and a capitalized “Novembro” in a reminder looks translated. Fourth, Brazilian short dates in CLDR use a four-digit year, which avoids confusion in contracts and invoices.

Weeks, holidays and business hours

CLDR gives Sunday as the first day of the week for both Brazil and Portugal, and weekdays in Portuguese are counted from Sunday: segunda-feira (Monday) is literally “the second day”. Many offices still plan Monday to Friday, so ask each client how their team reads a week view and set calendars to match. Public holidays differ by Brazilian state and municipality as well as nationally, and Portugal has municipal holidays too, so set each calendar’s availability for the client’s own city rather than the country as a whole.

Brazil also spans several time zones, from Brasília time in São Paulo and Rio de Janeiro to earlier zones in Manaus and the far west. Set each sub-account’s time zone to the client’s city, not to “Brazil”, and check reminders for clients that serve customers in other states.

What follows HighLevel’s settings

Invoices, payment links, products, reports and calendar pages are generated by HighLevel, so their currency and formats follow HighLevel’s own settings for the sub-account. In each Portuguese-speaking client’s sub-account:

1. Set the business address and time zone under Settings, Business Profile. Portugal changes its clocks in spring and autumn; Brazil currently does not, so confirm reminder times after each change in Portugal.
2. Set the client’s currency (BRL, EUR or the local currency) in the payment settings so invoices and payment links show the right one, and check which payment methods your connected payment provider supports in that country.
3. Add the fields your client’s customers expect, such as a CPF or CNPJ number for Brazilian invoices or a NIF for Portuguese ones, as custom fields where the client needs them.
4. Check the date and price format on a sample invoice and a booking confirmation, and write dates out in full in your own templates, such as “13 de novembro de 2026”, which reads correctly everywhere Portuguese is spoken.

The language and format choices in our builder shape its live preview and the menu, but a theme does not change how HighLevel formats an invoice. Our market page lists the conventions and templates we suggest for clients in Brazil, including real formatting and a Sunday week.

How do LGPD and GDPR affect a Portuguese-language dashboard?

They affect how you show client data more than how the dashboard looks. Brazilian clients fall under the LGPD, and clients in Portugal under the EU’s General Data Protection Regulation (GDPR, in Portuguese RGPD). A theme that only restyles the browser does not change your legal position, but demos and support calls that show real customer data can. This section is background for a conversation with your client, not legal advice.

What Brazilian and Portuguese clients ask

Brazil’s Lei nº 13.709/2018, the LGPD, sets rules for processing personal data and gives the national data protection authority, the ANPD, the power to sanction companies; Article 52 sets fines of up to 2% of a company’s revenue in Brazil, capped at R$ 50 million per infraction. Expect Brazilian clinics, schools and law firms to ask where their data is stored, who can see it, and what their software providers do with it. Clients in Portugal ask the same questions under the GDPR.

Answer the storage and contract questions from HighLevel’s own documentation and your agreements with the client. GHL Dashboard Builder does not store, process or transmit your clients’ data, because the builder never connects to your HighLevel account and the installed code does not send data anywhere. If a client needs a formal opinion on what the LGPD or GDPR requires of them, they should ask their own data protection officer (in Brazil, the encarregado) or lawyer.

Screen shares are where data leaks

The everyday risk is simpler than any regulation. A sales demo, an onboarding call or a recorded training video can show real names, phone numbers, email addresses and deal values to people who should not see them. Many agencies train clients’ teams in recorded video calls and share the recordings afterwards, and every such recording is a chance to capture a real patient’s or student’s details.

Privacy mode handles that moment. An eye button in HighLevel’s header, labelled Modo de privacidade in Portuguese, blurs contact names, emails, phone numbers, the conversation list and deal values with one click, and a second click shows them again. Our guide to hiding client data on screen shares explains when to use it and what it covers.

Why do Portuguese SMS messages cost more, and what about WhatsApp?

Because most Portuguese accents are outside the basic SMS alphabet. One ã, ç, ê or á in a message switches the whole SMS to UCS-2 encoding, where a single message holds 70 characters instead of 160. WhatsApp templates avoid that problem but need approval in the right Portuguese variant, and emails need careful writing but no layout changes.

SMS: which accents fit and which do not

A normal SMS uses the GSM-7 character set from the GSM 03.38 standard. The GSM 03.38 table shows a basic alphabet with Latin letters, digits, common symbols and a short list of accented letters: é, à and an uppercase Ç are in it, but ã, õ, á, í, ó, ú, â, ê, ô and a lowercase ç are not. Later versions of the standard added a Portuguese “national language shift table” that keeps more accents in 7 bits, but support depends on the carrier and handset, and many senders still fall back to UCS-2.

When a message contains any character outside GSM-7, the whole message is sent as UCS-2. Twilio’s page on how long an SMS can be gives the limits: 160 characters for a single GSM-7 message and 153 per segment of a longer one, against 70 and 67 for UCS-2. Portuguese makes this hard to avoid, because the most common words carry the accents: não, você, informação, amanhã, horário.

The practical effect: a 140-character appointment reminder in correct Portuguese almost always contains an accent outside GSM-7, so it needs three UCS-2 segments (67 + 67 + 6) instead of one. If your SMS provider bills per segment, that triples the cost of each reminder. You have three choices:

• Write short. Keep reminders under 70 characters so they fit one UCS-2 segment: “Consulta amanhã às 10h na Clínica Sorriso. Responda NÃO p/ cancelar.” That is 68 characters.
• Budget for segments. Accept two segments for longer messages and plan the client’s monthly message budget around them.
• Remove accents only with the client’s agreement. “Sua consulta e amanha as 10h” fits GSM-7 but reads as careless to many readers. Some clients accept it for internal alerts; few accept it for patients or students.

Paste each Portuguese template into your provider’s segment calculator before you set a client’s monthly budget.

WhatsApp: approved templates in the right variant

Many Brazilian clients will ask for WhatsApp as well as, or instead of, SMS. Messages that start a WhatsApp conversation need pre-approved templates, and Meta’s list of supported languages for WhatsApp templates has separate codes for Portuguese (BR), pt_BR, and Portuguese (POR), pt_PT. Each language version is its own template and is reviewed on its own, so submit Brazilian clients’ templates as pt_BR and Portuguese clients’ as pt_PT. Store a preferred-language field on each contact and use it in workflows to choose the right version.

Email: write it, then test it

HighLevel’s email builder handles Portuguese text without special settings. The work is in the writing:

1. Build one Portuguese master template and have a native speaker from the client’s country read it before you copy it.
2. Keep the form of address consistent with the menu and the SMS templates.
3. Check that accents in subject lines and the sender name display correctly in Gmail and Outlook on desktop and phone.
4. Translate the footer, unsubscribe text and any button labels you wrote yourself, using the client’s variant.

Can you give Portuguese to some clients and keep English for the rest?

Yes. Many agencies serve a mix: English-speaking clients, Brazilian clients and perhaps one client in Portugal. Give each client the menu language its team reads best, and remember that one design shows one menu wording for everyone in the sub-accounts it covers.

Bilingual teams in one sub-account

HighLevel’s native setting handles bilingual teams per user: an American owner can keep English while the Brazilian office team picks Portuguese (Brazil) in Settings, My Profile. A theme works per sub-account, so for a bilingual team, decide which menu everyone will share:

• Portuguese menu, Platform Language per user. The menu reads in Portuguese for everyone, and each user’s inner pages follow their own Platform Language. This suits a clinic or school where most daily users work in Portuguese.
• English menu, Portuguese inner pages per user. The menu stays in English, and Portuguese-speaking users set their Platform Language for inner pages. This suits an international team whose working language is English.
• Words that work in both languages. Several menu items are the same or close in English and Portuguese: Marketing, Sites, Dashboard, Launchpad, Workflows. For a bilingual team, favor those where you can.

Different clients, different designs

HighLevel’s Custom CSS and Custom JavaScript boxes sit at agency level, so whatever you paste applies across all sub-accounts by default. To give one client a Portuguese design, the theme must know which sub-accounts to target. GHL Dashboard Builder does this with an “Only these sub-accounts” option: you add the client’s sub-account by its link or Location ID, that sub-account gets the design, and every other sub-account and the agency view keep plain HighLevel. You still paste one install code. Our guide to finding a HighLevel Location ID shows where that ID lives.

Picture an agency with forty English-speaking sub-accounts and three Brazilian clinics. The agency adds the three clinics’ sub-accounts to the design’s list, and only those three see the Portuguese menu in their brand.

Be precise about what one install covers. One design is shown in the chosen sub-accounts; Pro includes up to 3 designs and Agency up to 100. If you need different looks for different clients, for example a Brazilian design for clinics in São Paulo and a European Portuguese variant for a client in Porto, contact us and we will plan how to set that up. Our guide to GoHighLevel sub-account branding explains the options in more depth.

How do you set up a Portuguese GoHighLevel dashboard, step by step?

Agree the variant, the form of address and the scope with the client, set HighLevel’s native language and sub-account basics, write the Portuguese content, design and install the theme, then test with the people who will use it. The steps assume agency admin access and that your agency’s logo and domain are already set; our guide to white-labeling HighLevel covers those first. Menu paths follow HighLevel’s help center at the time of writing.

Infographic

A Portuguese GoHighLevel dashboardin five steps

1. 1

   Agree the variant

   Brazil or Portugal, você or neutral, and what will be Portuguese.

2. 2

   Set native Portuguese

   Platform Language, time zone and currency per sub-account.

3. 3

   Write the content

   Short SMS, pt_BR or pt_PT WhatsApp templates, tested emails.

4. 4

   Design and install

   Template, colors, short Portuguese labels, two install lines.

5. 5

   Test like a user

   Daily screens, a language switch and SMS segments.

Step 1: Agree the variant and the scope

1. Write down who logs in and which language each person reads best: Portuguese, English or both.
2. Agree the variant: Brazilian or European Portuguese, and for other countries, which norm the team follows. Agree the form of address: você for Brazil, the client’s own tone for Portugal.
3. Agree in writing what will be Portuguese: the menu and navigation, HighLevel’s inner pages where HighLevel has translated them, and all customer messages, forms and booking pages. Name what may stay in English: some inner screens, parts of the builders and the Conversations views, some validation messages, system emails and the mobile app, depending on HighLevel’s current translation.
4. Ask which words they use for their customers, appointments and deals, and whether they prefer Portuguese terms or English loanwords such as Leads and Pipeline.

Step 2: Set HighLevel’s native language and the sub-account basics

1. Open the client’s sub-account and go to Settings, Business Profile.
2. Set Platform Language to Portuguese (Brazil) or Portuguese (Portugal) as the sub-account default.
3. Ask English-preferring users to set their own language under Settings, My Profile.
4. Enter the business name and address the way the client writes them, including the legal form (Ltda., S.A., Lda., Unipessoal), and set the correct time zone for the client’s city.
5. Set the currency in the payment settings, and add custom fields such as CPF, CNPJ or NIF if the client’s invoices need them.
6. Set each calendar’s availability to the client’s real week, local holidays and opening hours.

Step 3: Write the Portuguese content

1. Create the Portuguese SMS templates, count their segments, and keep the most frequent ones, such as reminders, under 70 characters.
2. Submit WhatsApp templates for approval with the code pt_BR or pt_PT.
3. Build one Portuguese email template and test it in two mail apps.
4. Translate forms, surveys and booking pages, including the confirmation and error messages you control. Write your own required-field hints in Portuguese where the form builder allows it, since some of HighLevel’s own messages may still appear in English.
5. Add a contact field for preferred language and use it in workflows to pick the Portuguese or English version.

Step 4: Design and install the theme

1. Open the free builder in Portuguese, choose a template, and set the client’s colors, logo and fonts.
2. Rename the menu items you agreed in Step 1, rename Assinaturas to Cursos or Área de membros if the client uses memberships, shorten long labels, apply European Portuguese overrides for clients in Portugal, and hide the items the client does not use.
3. If only this client should get the Portuguese design, limit the design to their sub-account.
4. In the agency view, open Settings, Company, Whitelabel and find the custom code area. Copy whatever is already in Custom CSS and Custom JavaScript into a text file as your rollback.
5. Paste the theme’s CSS line and JavaScript line and save. HighLevel warns about third-party scripts; confirm only if you trust the code. On every plan, we do this step for you as part of the setup.

Step 5: Test like an office user

1. Open the sub-account in a new tab and hard-refresh.
2. Walk through the dashboard, conversations, calendars, contacts and the opportunities board, on a laptop screen and at 125% browser zoom, and look for labels that wrap.
3. Switch a test user’s Platform Language between Portuguese and English and check that the menu keeps your wording.
4. Send yourself a Portuguese SMS reminder and check its segment count with your provider.
5. Ask two staff members to use it for a morning and tell you which labels confuse them.

What can go wrong, and what doesn’t a Portuguese theme solve?

Most problems come from unclear promises, the wrong variant, long labels nobody tested and SMS costs nobody planned for. A theme changes how HighLevel’s menu and main screens look and read; it does not translate HighLevel’s inner pages, it does not correct HighLevel’s own translation, and it does not write your clients’ content.

There are also limits no theme removes. HighLevel does not officially support custom code, so a platform update can require a theme refresh; Starter and Pro include 12 months of updates for this, and Agency includes lifetime updates. A theme works in the web browser; it does not change HighLevel’s mobile app, its system emails or its builders. The installed code does not change HighLevel’s login page yet; on Pro and Agency we design the branded sign-in page with you. One design shows one menu wording, so a bilingual team shares one menu. A Portuguese menu does not by itself answer a client’s LGPD or GDPR questions; those depend on HighLevel, your contracts and how the client uses the platform. And no menu translation makes up for poorly written content: budget for a native writer from the client’s country, and see our FAQ for questions about installing, removing and data.

What to do next

1. List your Portuguese-speaking clients and, for each one, who logs in, which country they are in, whether they write Brazilian or European Portuguese, and how they address their own customers.
2. Set HighLevel’s Platform Language to the right Portuguese variant in each of those sub-accounts today; it is free and covers the inner pages a theme never touches.
3. Fix the sub-account basics: time zone by city, currency, local holidays, and custom fields such as CPF, CNPJ or NIF.
4. Count the segments of your Portuguese SMS templates, shorten the reminders, and submit WhatsApp templates as pt_BR or pt_PT.
5. Try the client’s colors and a Portuguese menu in the builder, install on one sub-account first, and compare the plans when you are ready to roll it out.