English Intranet for Teams in Korea
When Korean groupware is enough for a mixed English and Korean team, where bilingual teams hit gaps, and how a custom portal fits on top of existing tools.
A team in Korea that works in both English and Korean can usually run on off-the-shelf groupware for mail, chat and calendars, and needs a custom intranet only for the parts that tools handle badly in two languages: approvals, HR documents, policies and reports for head office. The practical setup is to keep the groupware your staff already use and add a small bilingual portal on top, with single sign-on and the same data shown in each person's language. This guide covers when groupware is enough, where the gaps are, and how to build the portal without creating a second system to maintain.
When is off-the-shelf groupware enough?
For many foreign-owned teams in Korea, a standard suite covers most daily work:
| Need | Usually covered by groupware? | Notes |
|---|---|---|
| Email, calendar, chat, video calls | Yes | Google Workspace, Microsoft 365 and Korean suites such as NAVER WORKS all work in English |
| Shared documents and drives | Yes | Agree which language each folder is in |
| Announcements | Mostly | Bilingual posts are manual unless you use built-in translation |
| Leave requests and simple approvals | Depends | Korean suites commonly include electronic approval; global suites may need an add-on |
| HR records, wage statements, policies | Rarely in two languages | This is where gaps appear |
| Head office reporting | No | Usually spreadsheets until someone builds a view |
Korean groupware has improved for mixed teams. NAVER WORKS, for example, publishes an English help centre and includes built-in translation for posts and email, so a manager can read a Korean announcement in English without copying it into a translator. If your team is small and most work happens in chat and mail, start there and add nothing until a specific process breaks.
Where do bilingual teams hit gaps?
The friction is predictable. It shows up in five places:
- Approvals. Korean companies route many decisions through formal electronic approval (전자결재): purchase requests, expense claims, contracts. Head office wants to see and sometimes approve these in English, with the amounts and attachments, not a translated summary.
- HR documents. Employment contracts, wage statements and leave balances are prepared in Korean for Korean law and Korean staff. Foreign managers and head office HR need to read them.
- Policies and rules. A company handbook that exists only in English is hard for Korean staff to rely on; one that exists only in Korean is opaque to head office. Keeping two versions in step is a content problem, not a translation problem.
- Names, dates and holidays. Korean names are family name first, Korean public holidays follow the lunar calendar for Seollal and Chuseok, and dates are written year-month-day. Tools that assume Western conventions produce small errors that add up.
- Reporting. Head office wants a monthly summary in its own format. Someone ends up copying numbers from Korean screens into an English spreadsheet.
What HR records does Korean law expect?
An intranet that handles HR touches records the Labor Standards Act regulates. In summary, from the statute text (not legal advice):
- Employee register. An employer keeps a register for each workplace with each employee's name, date of birth, career history and other items set by decree, and updates it without delay when details change (Article 41).
- Retention. The register and key documents relating to employment contracts are kept for three years (Article 42).
- Wage statements. At every payment, the employer gives each employee a wage statement showing the components of pay, how they were calculated and any deductions. It can be delivered electronically (Article 48(2)).
- Working hours. The standard week is 40 hours and the standard day 8 hours, excluding breaks, with up to 12 hours of overtime a week by agreement (Articles 50 and 53).
- Rules of employment. An employer with 10 or more regular employees writes rules of employment covering hours, pay, leave, retirement, workplace harassment and other listed items, and reports them to the Ministry of Employment and Labor (Article 93).
The Korea Legislation Research Institute publishes an English translation of the Act, which is a convenient reference for head office. Your labour attorney should confirm how each rule applies to your entity, and payroll itself is often handled by a payroll package or an outside service rather than the intranet.
For a portal, these rules translate into design requirements: records you cannot delete before the retention period ends, a delivery log showing that each wage statement was issued, access limited to the people who need it, and Korean documents shown alongside an English reference version where head office needs one.
How does a custom portal fit on top of existing tools?
The aim is one small system that fills the gaps, not a replacement for the groupware. A typical design:
- Single sign-on. Staff sign in with the same account they use for mail and chat. No second password, and leavers lose access when their main account is closed.
- Bilingual content fields. Each policy, announcement or form has a Korean and an English version stored side by side, with a visible flag when one is newer than the other.
- Approvals with both languages. Requests carry structured fields (amount, supplier, cost centre) that display in each viewer's language, plus the original attachments.
- HR views, not an HR system. Payroll stays where it is. The portal shows each employee their own documents and gives managers the English view head office asks for, pulling data from the payroll or HR source rather than retyping it.
- Reports for head office. A monthly summary in English, built from the same records the Korean team uses.
- Notifications where people look. Korean staff are more likely to see a KakaoTalk message than an email; see KakaoTalk Channel and AlimTalk for how business messages work.
If the portal grows into quotes, orders and invoices, it becomes an ERP question; see ERP for foreign companies in Korea.
How should security and access be handled?
An intranet that holds HR records holds personal information under Korea's Personal Information Protection Act. Plan for it from the first version:
- Role-based access, so an employee sees only their own records and a manager sees only their team.
- An audit log of who viewed or changed sensitive records.
- A clear list of what personal data the portal stores and why, which feeds your internal privacy documentation.
- A decision on where the data is stored. If the servers or any outside service sit outside Korea, raise the cross-border transfer rules with your privacy adviser before launch.
- Sensible defaults for leavers, retention and deletion, matched to the three-year retention rule above.
Build or buy?
| Situation | Recommendation |
|---|---|
| Fewer than about 20 people, mostly chat and mail | Groupware only; use built-in translation |
| Formal approvals that head office must see | Groupware plus a small approval portal, or a Korean suite with strong approvals |
| HR documents in two languages, retention rules, head office reporting | Custom portal on top of groupware and the payroll source |
| Several Korean and global systems that need one bilingual view | Custom portal with integrations |
What does a custom portal cost?
In our pricing catalogue (version 1.1, 23 September 2026), a base business system covering one workflow is KRW 2.0M–6.0M and takes 4–10 weeks. Extended admin with three or more roles, Excel export and an audit log is KRW 0.6M–1.5M, and each two-way data sync with another system KRW 0.8M–1.5M, all excluding VAT. A first version that covers approvals or HR documents for one team is usually one workflow plus the admin item. The full breakdown is in custom ERP development cost in Korea.
If your head office is abroad, the scoping can be done in English with our English-speaking founder, and we can meet your Korean team in person in Korea.
Frequently asked questions
Does NAVER WORKS have English?
Yes. NAVER WORKS publishes an English help centre, and its mail and posts include built-in translation, so a manager can read a Korean message in English.
Can we build an English portal on top of Korean groupware?
Yes. The usual approach is a small portal that uses the groupware account for sign-in and adds what the groupware lacks: bilingual policies, approvals with structured fields, HR document views and English reports for head office.
Can wage statements be delivered electronically in Korea?
Yes. Article 48(2) of the Labor Standards Act requires a wage statement at each payment and allows it to be given as an electronic document. A portal should keep a record that each statement was issued.
How long must employee records be kept in Korea?
Article 42 of the Labor Standards Act requires the employee register and key documents relating to employment contracts to be kept for three years. Build retention rules into the portal so these records cannot be deleted early.
How long does it take to build a bilingual intranet?
In our catalogue, a base business system covering one workflow takes 4–10 weeks. A first version that handles one process, such as approvals or HR documents, usually fits that range; each integration adds time.
Sources
All checked October 2026.
- Korea Legislation Research Institute, Labor Standards Act (English translation)
- Korea Ministry of Government Legislation, Labor Standards Act (Articles 41, 42, 48, 50, 53, 93)
- NAVER WORKS Help Center, Translate emails
- Korea Ministry of Government Legislation, Personal Information Protection Act
- NQ Solution pricing catalogue v1.1 (23 September 2026): business system, admin and integration line items, in KRW excluding VAT
Need a bilingual portal for your Korean team?
Tell us which process your team handles in two languages today, and where it breaks, through the project request form. See what we build on the software development in Korea page, and how internal systems fit a wider launch on the Korea market entry page.