FieldKo on the Lightning Platform

FieldKo runs inside your company’s Salesforce org. Its 2 managed packages add objects, apps, tabs, permission sets, and automation, and everything you already know about Salesforce still applies: the same users, security, reports, and tools. This page explains what FieldKo adds to your org, what you get because it runs on Salesforce, and how the FieldKo Atlas app fits in. Use the rest of the Salesforce Platform section to run FieldKo with standard Salesforce tools. Most companies run FieldKo on Salesforce Platform licenses. Where a feature needs more than a Platform license, these pages say so. See Licenses and What’s Included.

What the Packages Add to Your Org

The FieldKo package holds the retail execution data model and the Salesforce screens. The FieldKo Native package adds what the FieldKo Atlas app needs. For the split between them, see The Two Packages.

Component	What FieldKo Adds
Apps	The FieldKo app, with the planning, call cycle, survey, product, and order tabs, plus Reports and Dashboards. The FieldKo Builder app, with the Survey and Question tabs.
Tabs	Object tabs, such as Visits, Task Types, and Field Campaign, and page tabs, such as Visit Calendar, Visit Planner, Call Planning, Call Cycles, Objectives, Map, Account Map, Place Order, and FieldKo Configuration. FieldKo Native adds Attendance, Incidents, Pack Outs, Sync Details, Metadata Collector, and FieldKo Theme.
Custom objects	Visits, tasks, task types, surveys and answers, call cycles, visit templates, field campaigns, objectives and targets, FieldKo products, price books, orders, and ranging. FieldKo Native adds attendance, incidents, pack-outs, and sync details. See FieldKo Data Model.
Permission sets	FieldKo Representative Permission Set, FieldKo Manager Permission Set, the Basic versions of both, FieldKo Native Permission Set, and permission sets for Experience Cloud users. See Recommended Access by Role.
Lightning pages	Lightning record pages for objects such as visits, surveys, and questions
Report types	Report types for tasks, survey answers, objectives, targets, orders, and ranging. See Report Types and What They Include.
Settings	Custom settings and custom metadata types that control the app and the Salesforce screens. See Configuration Reference.
Built-in automation	Apex triggers and flows that run when records change. They block visits that have no sales representative, account, or active call cycle, set each visit’s owner to its sales representative, update the account’s Last Check-Out and Next visit plan date when a visit is completed, deactivate price book entries and product set lines when a product becomes inactive, and link visits and pack-outs to the rep’s attendance record for the day.

The packages don’t schedule any background jobs. You schedule the ones you need. See Scheduled Jobs.

What You Get Because FieldKo Runs on Salesforce

Because FieldKo data lives in standard Salesforce objects, you manage it with the same tools you use for the rest of your org.

Salesforce Capability	What It Means for FieldKo
One login and security model	Reps and managers use their Salesforce users. Profiles, permission sets, roles, and sharing control FieldKo data the same way they control any other data. Reps log in to the app with their Salesforce credentials. See Security Model and Sharing and Login and Security.
Reports and dashboards	Measure coverage, call compliance, visit frequency, time in store, out of stocks, and promotion compliance from visits, tasks, and survey answers. See Retail Execution Metrics.
Flow	Automate around field work, such as alerting a manager when a survey answer records an out of stock. See Design Automation for FieldKo.
Lightning App Builder and page layouts	Change record pages, home pages, and list views. Page layouts also decide which fields reps see in the app. See Customize the FieldKo App and Home Page.
Sandboxes	Test package upgrades, new surveys, and automation before you release them to reps. See Manage Releases: Sandboxes, Deployments, and Package Upgrades.
AppExchange	Add other apps alongside FieldKo, such as data quality, document generation, or mapping tools.
APIs	Connect FieldKo to your ERP, data warehouse, or reporting tools with standard Salesforce APIs and connectors. See Integrate FieldKo with Other Systems.

How the FieldKo Atlas App Fits In

The FieldKo Atlas app doesn’t have its own database in the cloud. It keeps an offline copy of part of your org on each rep’s device and syncs changes back to Salesforce. Three things decide what reaches a device:

Records: FieldKo picks each rep’s records from the accounts they own or are on the account team for, their call cycles, and a date window. Salesforce sharing and field-level security apply on top. See Control What Syncs to the App.
Objects, fields, and layouts: The Metadata Collector stores your objects, fields, page layouts, and record types for the app. After you change any of them, rerun it and ask reps to run Reset Sync. See Run the Metadata Collector.
Settings: Custom settings reach the app on the next sync. See How Configuration Reaches Devices.

Everything reps record in the app, such as check-ins, survey answers, photos, and orders, arrives in Salesforce as ordinary records after they sync. Managers report on it like any other data.

Explore Salesforce Platform

Licenses and What's Included

Which Salesforce licenses FieldKo users need, and what a Platform license covers.

FieldKo Data Model

How visits, tasks, surveys, orders, and ranging relate.

Run FieldKo Day to Day

Add reps and stores, move territories, and launch surveys.

Users and Access

Licenses, profiles, permission sets, roles, sharing, and login security.

Customize FieldKo

Pages, fields, record types, and validation rules that work in the app.

Reports and Dashboards for Admins

Report folders, custom report types, and dashboard running users.

Automate with Flow

Flow recipes, approvals, and notifications for field teams.

Integrations and APIs

Connect FieldKo to other systems and stay within platform limits.

Data and Releases

Import data, plan for data volume, and manage sandboxes and upgrades.

Get Started

Configure FieldKo

Reference

Troubleshoot

Salesforce Platform

FieldKo on the Lightning Platform

What the Packages Add to Your Org

What You Get Because FieldKo Runs on Salesforce

How the FieldKo Atlas App Fits In

Explore Salesforce Platform

Licenses and What's Included

FieldKo Data Model

Run FieldKo Day to Day

Users and Access

Customize FieldKo

Reports and Dashboards for Admins

Automate with Flow

Integrations and APIs

Data and Releases

See Also

​What the Packages Add to Your Org

​What You Get Because FieldKo Runs on Salesforce

​How the FieldKo Atlas App Fits In

​Explore Salesforce Platform

Licenses and What's Included

FieldKo Data Model

Run FieldKo Day to Day

Users and Access

Customize FieldKo

Reports and Dashboards for Admins

Automate with Flow

Integrations and APIs

Data and Releases

​See Also

What the Packages Add to Your Org

What You Get Because FieldKo Runs on Salesforce

How the FieldKo Atlas App Fits In

Explore Salesforce Platform

See Also