> ## Documentation Index
> Fetch the complete documentation index at: https://support.fieldko.com/llms.txt
> Use this file to discover all available pages before exploring further.
# FieldKo for Admins
> Learn how FieldKo is set up in Salesforce, and how your configuration changes reach reps' devices.
As an admin, you set up FieldKo in your company's Salesforce org and control what reps see in the FieldKo Atlas app. This page explains the 2 managed packages you install and when each kind of configuration change reaches reps' devices. To start setting up, go to [Install and Set Up FieldKo](/admin/installation).
New to FieldKo? Start with [Key Concepts](/getting-started/key-concepts).
| To do this | You need |
| - | - |
| Configure FieldKo on the **FieldKo Configuration** tab | FieldKo Manager Permission Set |
| Run the Metadata Collector | FieldKo Manager Permission Set and FieldKo Native Permission Set |
## The Two Packages
| Package | What It Provides |
| - | - |
| **FieldKo** (Retail Field Management) | The core data model and Salesforce screens: visits, tasks and task types, surveys, call cycles, visit templates, products, price books, orders, ranging, objectives, the **FieldKo Configuration** tab, the visit calendar and planner, and permission sets |
| **FieldKo Native** | Everything the FieldKo Atlas app needs in Salesforce: sync and metadata services, the **Metadata Collector**, mobile menu and visit-action settings, sync logs, attendance, incidents, and pack-outs |
Install the FieldKo package first. The FieldKo Native package depends on it. See [Install and Set Up FieldKo](/admin/installation).
## How Configuration Reaches Devices
Different kinds of changes reach reps' devices at different times.
```mermaid theme={null}
flowchart LR
A[Custom settings and metadata] -->|any sync| D[FieldKo Atlas]
B[Custom labels and translations] -->|manual Sync or Reset Sync| D
C[Objects, fields, layouts, record types] -->|Metadata Collector| M[(Object and Profile Metadata)]
M -->|Reset Sync| D
R[Records] -->|any sync, filtered per user| D
```
In words: custom settings, custom metadata, and records reach the app on any sync. Custom labels and translations reach it on a manual **Sync** or **Reset Sync**. Changes to objects, fields, layouts, and record types reach it only after you run the Metadata Collector and reps run **Reset Sync**. The following table gives the details.
| You Change | What Else You Do | Reaches the Device On |
| - | - | - |
| Custom settings (menu, visit actions, sync, visit configuration) | Nothing | Any sync, including background sync |
| Custom labels and translations | Nothing | Manual **Sync** from the Sync screen, **Reset Sync**, or first login |
| Objects, fields, page layouts, record types, Objects To be Fetched, layout overrides | Run the [Metadata Collector](/admin/offline-data#run-the-metadata-collector) | **Reset Sync** or first login |
| Record data, sharing, account teams, call cycles | Nothing | Any sync |
Layout and field changes reach reps only after you rerun the Metadata Collector **and** reps run **Reset Sync**. Before reps run **Reset Sync**, ask them to tap **Sync** so their unsynced changes upload first and aren't lost.
## Language and Labels
The app shows text in **each user's Salesforce language** (the **Language** field on their user record). The app gets its text from these sources:
1. Custom labels in both FieldKo packages, including your Translation Workbench translations
2. Object, field, picklist, record type, and quick action labels from Salesforce, in the user's language
3. Defaults built into the app
To rename something in the app, such as "Visit" or "Check In", follow these steps:
1. Override the matching custom label, or add a translation.
2. Ask reps to tap **Sync** on the Sync screen. Labels reach the device only on a manual sync, a **Reset Sync**, or first login.
Some screens are English only: the side menu item names, **Sync**, **Settings**, and the logout and login messages.
### Set the Calendar and Map Language
The calendars on FieldKo's Salesforce pages, such as **Visit Calendar**, **Visit Planner**, and **Clone Visits**, use the language in the **Language Support** custom setting, not the user's Salesforce language. This setting doesn't affect the FieldKo Atlas app, which follows each user's Salesforce language.
Language Support is a hierarchy custom setting. You can set it for the whole org, for a profile, or for a user, and the most specific value wins.
| Field | What It Does | After Install |
| - | - | - |
| Calendar | Sets the calendar language. Enter a language code, such as `fr`, `de`, or `en-gb`. | `en` |
| Map | The map language code, in the same format | `en` |
To set the language, follow these steps:
1. From Setup, in the Quick Find box, enter `Custom Settings`, and then select **Custom Settings**.
2. Next to **Language Support**, click **Manage**.
3. Choose the level:
* **Whole org:** In the default organization level section, click **Edit**, or **New** if there's no default yet.
* **A profile or user:** Click **New**, and then select the profile or user in **Location**.
4. Enter the **Calendar** and **Map** language codes.
5. Click **Save**.
You can also choose **Calendar Language** and **Map Language** on the **FieldKo Configuration** tab, under **Calendar and Map**. The tab offers English and English Australia only. For other languages, or if your choice doesn't save, use the custom setting. See [FieldKo Configuration Tab](/admin/configuration-reference#fieldko-configuration-tab).
## Where to Go Next
Packages, permission sets, connected app, Google Maps, and scheduled jobs.
Which records sync to each rep, and how to add objects.
Call cycles, task types, and visit templates.
Every setting the app reads.
## See Also
* [Key Concepts](/getting-started/key-concepts)
* [Install and Set Up FieldKo](/admin/installation)
* [Control What Syncs to the App](/admin/offline-data)
* [Diagnose Rep Issues](/admin/support-diagnostics)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.