Overview

Commonly asked questions about how PeopleGlass handles security and permissions:

Currently, PeopleGlass only works for Salesforce users with API access. If you do not have API access, please check with your Salesforce Admin or IT team for support.

We use Salesforce SSO for authentication, meaning we follow the Salesforce OAUTH protocol defined by each organization's Salesforce admin or IT team. If SSO via Okta is enforced on your Salesforce, then the Salesforce OAUTH process will also enforce it.

If you would like to prompt users to go through Okta after they install the Chrome extension, please reach out to your organization's Salesforce admin or IT department to implement Okta on the Salesforce side.

PeopleGlass will obey whatever MFA or SSO settings you have set up with your Salesforce instance. Salesforce handles all SSO requirements.

For example, if your company uses a third-party app such as Okta, you need to type in the custom domain for your account on the Salesforce login page. Then, it should redirect you to log in using the right app.

If your company uses Okta or another third-party authenticator to log in to Salesforce, you will need to enter your company's custom domain instead of using your username and password.

If you are using Sandbox Replica, make sure to click the "Click Here" text in blue underneath "Continue with Salesforce.” Note that sometimes your Sandbox account may look very similar to your production account.

Alternatively, you can log into your Salesforce account first and then go through the PeopleGlass login flow. Once you log in, Salesforce will save your credentials on their login page, so you will not need the custom domain name.

--

Need help? Drop us a line on Intercom in our app!