> ## 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. # Licenses and What's Included > Understand which Salesforce and FieldKo licenses each user needs, what a Platform license covers, and which features need another license. Every FieldKo user needs 2 things: a Salesforce user license, which lets them log in to your org, and access to FieldKo, which comes from the FieldKo packages and their permission sets. This page explains how the two fit together, what a Salesforce Platform license covers for FieldKo, and which features need a different license. License entitlements and limits depend on your Salesforce contract and change over time. This page doesn't list numeric limits. To confirm what your licenses include, check your Salesforce contract or ask your Salesforce account executive, and see [User Licenses](https://help.salesforce.com/s/articleView?id=sf.users_understanding_license_types.htm\&type=5) and [Salesforce Editions](https://help.salesforce.com/s/articleView?id=sf.overview_edition.htm\&type=5) in Salesforce Help. ## Two Kinds of Licenses | License | What It Controls | Where to Manage It | | - | - | - | | **Salesforce user license** | Whether a person can log in to Salesforce, and which standard objects and features they can use. Most FieldKo reps and managers use a Salesforce Platform license. | From Setup, in the Quick Find box, enter `Company Information`, and then select **Company Information**. The **User Licenses** related list shows what you have and what's used. | | **FieldKo package license** | Whether a user can use the FieldKo packages' objects, tabs, and code. Your FieldKo agreement sets whether licenses are assigned to specific users or available to everyone in the org. | From Setup, in the Quick Find box, enter `Installed Packages`, and then select **Installed Packages**. If your org assigns licenses per user, click **Manage Licenses** next to each FieldKo package. | A user license alone doesn't make someone a FieldKo user. FieldKo also checks for one of its permission sets. See [Profiles, Permission Sets, and Permission Set Groups](/platform/access/permission-sets). ## What a Platform License Covers for FieldKo Salesforce Platform licenses, also called Lightning Platform licenses, come in Starter and Plus versions. They're designed for custom apps built on your org's data, which is how FieldKo works: almost everything a rep or manager touches is a FieldKo custom object. | Capability | How FieldKo Uses It | | - | - | | Custom objects | Visits, tasks, surveys, call cycles, orders, ranging, attendance, and the rest of the [FieldKo data model](/platform/data-model) | | Accounts and contacts | Accounts are the stores reps visit. FieldKo syncs each rep's accounts and their contacts to the app. | | Activities | FieldKo can create a Salesforce event for each planned visit, and the app syncs each rep's events | | Reports and dashboards | All FieldKo report types and your own reports and dashboards | | Flow | Your own automation on FieldKo objects | | Chatter | FieldKo posts check-ins and check-outs to the account's Chatter feed by default | Platform Starter and Plus differ in how many custom objects each user can access and in other entitlements. Because FieldKo uses many custom objects, confirm with your FieldKo contact and your Salesforce account executive which Platform license fits each type of user before you buy. ## Features That Need Another License Platform licenses don't include the main Sales Cloud and Service Cloud objects. Users need a license that includes these objects, such as a Sales Cloud or Service Cloud license, to use them. | Feature | Notes for FieldKo | | - | - | | Opportunities | The app can sync opportunities, and you can let reps create visits from opportunities, but only for users whose license includes them | | Leads | Not used by FieldKo | | Cases | The app can sync cases for users whose license includes them | | Forecasts | Not used by FieldKo. Use reports on FieldKo orders instead. | | Campaigns | Not the same as FieldKo field campaigns. FieldKo field campaigns are a custom object and work on a Platform license. | | Standard Products, Price Books, and Orders | Not needed. FieldKo uses its own product, price book, and order objects. See [Set Up Products, Ordering, and Ranging](/admin/products-ordering-ranging). | To check what a user's license includes, open their user record and look at the **User License** field, and then compare it with your contract. ## Integration Users Integrations that load products, accounts, or orders, or that read survey answers into a data warehouse, should log in as a dedicated integration user, not as a person. Salesforce offers an integration user license for API-only access in many editions. Check whether it's available in your org on the **Company Information** page, and give the integration user only the object access it needs. See [Integrate FieldKo with Other Systems](/platform/integrations/integrate). ## Portal Users Retailers or distributors who view or place FieldKo orders in a portal need Experience Cloud licenses, such as Customer Community or Partner Community. FieldKo includes separate permission sets for them. See [Customer Portal (Optional)](/admin/installation#customer-portal-optional). ## Who Needs Which License Use this table as a starting point, and confirm each row against your contract. | User | Salesforce User License | FieldKo Package License | FieldKo Permission Sets | | - | - | - | - | | Rep or merchandiser | Salesforce Platform | Yes, if your org assigns them per user | **FieldKo Representative Permission Set** and **FieldKo Native Permission Set** | | Manager | Salesforce Platform. Add a Sales Cloud license only if the manager also works with opportunities or forecasts. | Yes, if your org assigns them per user | **FieldKo Manager Permission Set** and **FieldKo Native Permission Set** | | Admin | Usually a full Salesforce license, so the admin can work with every object in the org | Yes, if your org assigns them per user | **FieldKo Manager Permission Set** and **FieldKo Native Permission Set** | | Integration | Salesforce integration user license, where available | Yes, if the integration reads or writes FieldKo objects and your org assigns licenses per user | None. Use your own permission set with only the access the integration needs. | | Portal user | Experience Cloud | Ask your FieldKo contact | The FieldKo community permission sets. See [Customer Portal (Optional)](/admin/installation#customer-portal-optional). | For the full setup of each type of user, including profiles and roles, see [Recommended Access by Role](/platform/access/recommended-access). ## See Also * [FieldKo on the Lightning Platform](/platform/overview) * [Recommended Access by Role](/platform/access/recommended-access) * [Install and Set Up FieldKo](/admin/installation) * [Remove a Rep's Access](/platform/day-to-day/remove-a-rep) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.