> ## 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.

# Add a New Rep

> Create a Salesforce user for a new rep and give them everything FieldKo needs before their first visit.

A new rep needs more than a Salesforce user to work in the FieldKo Atlas app. FieldKo also looks for a FieldKo permission set, a manager or role it can use to show the rep to their manager, an active call cycle, and accounts the rep owns or shares through an account team. If any of these is missing, the rep can often still log in, but sees no visits. Work through this checklist each time a rep joins.

## User Permissions Needed

| To do this | You need |
| - | - |
| Create users and assign permission sets | Manage Internal Users and Assign Permission Sets |
| Create call cycles | FieldKo Manager Permission Set |
| Change account owners and account teams | Edit access to the accounts, and Transfer Record to change owners |

## Before You Begin

* Decide which Salesforce license the rep gets. Most reps use a Salesforce Platform license. See [Licenses and What's Included](/platform/licenses).
* Find out who the rep's manager is, and which stores the rep covers.
* Make sure FieldKo setup is complete, including the Metadata Collector. See [Install and Set Up FieldKo](/admin/installation).

## Add the Rep

Complete these steps in order. Each step links to the full instructions.

<Steps>
  <Step title="Create the Salesforce User">
    From Setup, in the Quick Find box, enter `Users`, and then select **Users**. Click **New User**, and then select the user license and a profile. See [Add a Single User](https://help.salesforce.com/s/articleView?id=sf.adding_new_users.htm\&type=5) in Salesforce Help.

    If your org assigns licenses for the FieldKo packages, also assign them. From Setup, in the Quick Find box, enter `Installed Packages`, and then select **Installed Packages**. Next to each FieldKo package, click **Manage Licenses**, and then add the rep.
  </Step>

  <Step title="Assign the FieldKo Permission Sets">
    Assign the **FieldKo Representative Permission Set** and the **FieldKo Native Permission Set**. You can assign them directly, or through a permission set group that contains them. FieldKo recognizes a rep through either.

    Without a FieldKo permission set, sync fails with "Insufficient Privilege: User does not have access to FieldKo". See [Permission Sets](/admin/installation#permission-sets) and [Profiles, Permission Sets, and Permission Set Groups](/platform/access/permission-sets).
  </Step>

  <Step title="Connect the Rep to Their Manager">
    FieldKo decides which reps a manager can plan for and review from the **User Reporting Hierarchy** option on the **FieldKo Configuration** tab, under **Basic**. Set up the rep to match the option your org uses.

    | User Reporting Hierarchy | What to Set on the Rep |
    | - | - |
    | **Manager** (the default after install) | Set the **Manager** field on the rep's user record. Managers see their direct reports. |
    | **Role** | Assign the rep a role below their manager's role. |
    | **Public Group** | Add the rep to the same public group as their manager. In this mode, the rep's accounts also come from account sharing to that group. |

    See [Set Up Manager Visibility](/platform/access/manager-visibility) and [Roles and the Role Hierarchy](/platform/access/roles).
  </Step>

  <Step title="Create and Activate a Call Cycle">
    On the **Call Cycles** tab, generate the rep's call cycles for the current fiscal year, and then check that each cycle's **Active** checkbox is selected. If you schedule `CallCycleBatchscheduler`, it creates cycles for reps who don't have them on its next run. See [Call Cycles](/admin/call-cycles-and-visits#call-cycles).
  </Step>

  <Step title="Give the Rep Their Accounts">
    Make the rep the owner of their stores, or add them to each store's account team. The app syncs only the accounts a rep owns or shares through an account team. Access through the role hierarchy or sharing rules alone isn't enough. See [Add Members to Account Teams](https://help.salesforce.com/s/articleView?id=sf.accountteam_add.htm\&type=5) in Salesforce Help and [Accounts in Scope](/admin/offline-data#accounts-in-scope).

    If you're moving stores from another rep, see [Move a Rep to a New Territory](/platform/day-to-day/move-a-rep) for what FieldKo transfers when the owner changes.
  </Step>

  <Step title="Optional: Add the Rep to Brand Teams">
    Do this only if your org uses brands. From Setup, in the Quick Find box, enter `Custom Settings`, and then select **Custom Settings**. Next to **Branding**, click **Manage**. If the **Brands** record has **Enabled** selected, the rep receives only accounts that are linked to a brand where they're a **Brand Team Member**.

    To add the rep, open each brand account (record type Brand). In the **Brand Team Members** related list, add the rep as the **Member**, or click **Manage Brand Team** if your layout has it.
  </Step>

  <Step title="Send the Rep the App">
    Share the FieldKo Atlas app links: [App Store](https://apps.apple.com/us/app/fieldko-atlas/id1605506891) for iPhone and iPad, and [Google Play](https://play.google.com/store/apps/details?id=com.fieldko.reactnative) for Android. If you use My Domain or single sign-on, also share your login URL. See [Install the FieldKo Atlas App](/getting-started/install).
  </Step>

  <Step title="Test the First Login">
    Plan a visit for today for the rep, and then ask them to log in and wait for the first sync to finish. See [Send Reps the App](/admin/installation#send-reps-the-app) for the test steps and what to do if the visit doesn't appear.
  </Step>
</Steps>

**To confirm:** The test visit appears on the rep's **My Visits** screen with its tasks. In Salesforce, the **Sync Details** tab lists a sync for the rep with the status **Success**. The rep's manager can select the rep on the **Visit Calendar**.

## See Also

* [Install and Set Up FieldKo](/admin/installation)
* [Recommended Access by Role](/platform/access/recommended-access)
* [Control What Syncs to the App](/admin/offline-data)
* [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.