Skip to main content
Reps log in to the FieldKo Atlas app with their Salesforce credentials, so your org’s login settings apply to the app as well as to Salesforce. This page covers the settings that matter most for field teams and links to Salesforce Help for the details.

User Permissions Needed

Settings at a Glance

Refresh Tokens for Offline Reps

Reps often work for hours, or days, without a connection. The app keeps working offline and uses its refresh token to start a new session the next time it connects. After install, the FieldKo Native App connected app keeps refresh tokens until they’re revoked. If your policy requires refresh tokens to expire, set the expiry longer than the longest time a rep might work without logging in again, such as a holiday or a long trip. When a refresh token expires or is revoked, the app asks the rep to log in again the next time it connects. The rep needs a connection to log in.
Before you shorten the refresh token policy, revoke a rep’s access, or reset a rep’s password, ask the rep to tap Sync and wait for it to finish, so their offline work reaches Salesforce first. See Log Out Safely.
To change the policy, see Connected App. For Salesforce’s options, see Manage OAuth Access Policies for a Connected App in Salesforce Help.

Restrict IP Ranges for Reps

Login IP ranges on a profile block logins from any address outside the ranges. Because reps’ addresses change with every network, don’t set login IP ranges on rep profiles unless reps always connect through a company VPN. After install, the FieldKo Native App connected app relaxes IP restrictions, so the app keeps working outside your trusted IP ranges. If you enforce IP restrictions on the connected app, reps can sync only from the networks you allow. For details, see Restrict Login IP Addresses in Profiles in Salesforce Help. Your network must also allow status.salesforce.com. If it doesn’t, first-time setup fails with “Network Required” on the office network. See Rep Can’t Sync at All.

Troubleshoot Logins with Login History

When a rep can’t log in to the app, check their login history first:
  1. From Setup, in the Quick Find box, enter Login History, and then select Login History.
  2. Find the rep’s username, and then read the Status column for the reason, such as an invalid password, a restricted IP address, or a failed verification.
You can also open the rep’s user record and view the Login History related list. For more about the columns, see Monitor Login History in Salesforce Help. If the login succeeds but sync fails, the cause is usually access, not login security. See Diagnose Rep Issues.

See Also

Last modified on October 20, 2026