> ## 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. # Recommended Access by Role > Use a recommended license, profile, permission set, and role combination for each type of FieldKo user. Give each type of FieldKo user the same combination of license, profile, permission sets, and role, so access stays predictable as your field team grows. This page recommends a starting setup for each persona. Adjust it to your company's security policy. ## User Permissions Needed | To do this | You need | | - | - | | Create profiles and permission set groups | Manage Profiles and Permission Sets | | Assign permission sets, permission set groups, and roles | Assign Permission Sets and Manage Users | ## Recommended Setup by Persona The suggested permission set groups are groups you create. See [Create a Permission Set Group for Reps](/platform/access/permission-sets#create-a-permission-set-group-for-reps). | Persona | Salesforce License | Profile | FieldKo Permission Sets | Suggested Permission Set Group | Role | | - | - | - | - | - | - | | Field rep | Salesforce Platform | A custom profile, such as `FieldKo Rep`, cloned from a Platform profile and trimmed to the minimum | **FieldKo Representative Permission Set** and **FieldKo Native Permission Set** | `FieldKo Field Rep`: both FieldKo permission sets plus your own rep permission set | Field rep role, under the rep's area | | Merchandiser (rep variant) | Salesforce Platform | `FieldKo Rep`, or a separate `FieldKo Merchandiser` profile if merchandisers need different page layouts | Same as field rep | `FieldKo Field Rep`, or `FieldKo Merchandiser` with a muting permission set | Same as field rep | | Manager | Salesforce Platform | A custom profile, such as `FieldKo Manager`, cloned from a Platform profile | **FieldKo Manager Permission Set** and **FieldKo Native Permission Set** | `FieldKo Manager`: both FieldKo permission sets plus your own manager permission set | Area, region, or national role above the manager's reps | | FieldKo admin | Usually a full Salesforce license | System Administrator, or your own admin profile | **FieldKo Manager Permission Set** and **FieldKo Native Permission Set** | Not needed | A role at the top of the hierarchy, or none | | Read-only executive (reports only) | Salesforce Platform | A read-only custom profile | None | `FieldKo Executive Reporting`: your own permission set with read access to FieldKo objects and report access | A national or executive role | | Integration user | Salesforce integration user license, where available | An API-only profile | None | Not needed. Use one permission set with only the access the integration needs. | None | | Portal user | Experience Cloud | Your community profile | **Community Place/Edit FieldKo Order**, or **Community View FieldKo Orders** and **Community View FieldKo Pricebooks and Products**. Partner-licensed reps use **FieldKo Community Permission Set**. | Not needed | Assigned by the portal account | If your org assigns FieldKo package licenses per user, every persona that reads or writes FieldKo objects also needs a package license, including executives and integration users. See [Licenses and What's Included](/platform/licenses). ## Why Each Choice Matters in FieldKo ### Profiles Decide the Layouts Reps See in the App In most orgs, profiles matter less than they used to. In FieldKo, they still matter: the FieldKo Atlas app shows the page layout assigned to each rep's **profile** and record type, and the Metadata Collector collects layouts by profile. Give reps their own profile so you can change the app's layouts without affecting office users. See [Choose the Layout Reps See](/admin/offline-data#choose-the-layout-reps-see). Many app settings are hierarchy custom settings, so you can also set them per profile. For example, set **Visit Actions Configuration** on the `FieldKo Merchandiser` profile to hide **Place Order** for merchandisers. See [Visit Actions](/admin/configuration-reference#visit-actions). ### Permission Sets Decide Who Is a Rep or a Manager FieldKo treats a user as a rep or a manager based on which FieldKo permission set they have, directly or through a permission set group. Give each user one or the other: * **Reps** appear in managers' rep lists, and the `CallCycleBatchscheduler` job creates call cycles for them. * **Managers** can plan visits for their team and see the manager views of the **Objectives** and **Call Planning** tabs. Give a manager the **FieldKo Representative Permission Set** as well only if they also complete their own visits in the app. They then appear in rep lists and get call cycles like a rep. See [Profiles, Permission Sets, and Permission Set Groups](/platform/access/permission-sets). Don't give executives or integration users a FieldKo Representative permission set to grant them access. They would appear in managers' rep lists, and the call cycle job would create call cycles for them. Use your own permission set with the object access they need instead. ### Roles Decide What Managers See in Salesforce The FieldKo Manager Permission Set doesn't grant access to every record. Managers see their reps' visits, tasks, and orders through the role hierarchy or sharing rules. Put each manager's role above their reps' roles. See [Roles and the Role Hierarchy](/platform/access/roles). ## Set Up a New Persona To set up a type of user, work through these pages in order: 1. Choose the license. See [Licenses and What's Included](/platform/licenses). 2. Create or clone the profile, and assign page layouts to it. 3. Create the permission set group. See [Profiles, Permission Sets, and Permission Set Groups](/platform/access/permission-sets). 4. Add the role to your hierarchy. See [Roles and the Role Hierarchy](/platform/access/roles). 5. Decide how managers find their reps. See [Set Up Manager Visibility](/platform/access/manager-visibility). 6. Run the Metadata Collector so the app knows the new profile's layouts. See [Run the Metadata Collector](/admin/offline-data#run-the-metadata-collector). To add one person, see [Add a New Rep](/platform/day-to-day/add-a-rep). ## See Also * [Profiles, Permission Sets, and Permission Set Groups](/platform/access/permission-sets) * [Security Model and Sharing](/platform/access/security-model) * [Permission Sets](/admin/installation#permission-sets) * [Customer Portal (Optional)](/admin/installation#customer-portal-optional) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.