How it works

Sign in to OrgPulse, then sign in to Salesforce as an admin of the org, through Salesforce's own login page. That proves the org is yours. OrgPulse never sees your password, and your Salesforce sign-in is used for that one request and then discarded.

You choose:

• A dedicated integration user (recommended), with the OrgPulse_Monitor permission set from the OrgPulse package. It holds API access, View Setup and View Roles, and nothing that changes data.
• Quick start: you, with your own permissions. Good for a first look; switch to an integration user later.

Either way it signs in with a signed assertion from OrgPulse, never a password.

Three things, only when you ask, all about OrgPulse's own access:

1. Create a permission set named OrgPulse App Access. It grants no permissions; it only lets a user use the OrgPulse app.
2. Assign it and OrgPulse Monitor to the integration user.
3. Set the OrgPulse app to admin pre-authorised, for OrgPulse App Access. Profiles and permission sets already listed stay.

With quick start the second change assigns the access permission set to you instead. Nothing else in the org is touched, then or later.

On Pro, about every 24 hours; the first check within an hour of connecting. Run now checks an org on demand: 30 a day on Pro, 5 on Free, where it is the only way to check.

On Pro, a watch says what to look for and how many days ahead, and where to send it: email, Slack or both. You get one alert when an item crosses a threshold and one when it clears, never the same alert twice. Watches live in OrgPulse, not in Salesforce.

Sign out of an org to stop its checks, or forget it to delete everything OrgPulse holds for it at once. Neither changes Salesforce; to end access there too, remove the OrgPulse App Access assignment or uninstall the package. Security and data