Presentation Studio keys
Every Presentation Studio installed from Diligence gets these keys. Someone who sets their own key in Studio keeps theirs.
Two-step sign-in
After the emailed code, a code from the person’s phone (authenticator app or text message). Face ID sign-in counts as two steps. Anyone who has set it up always uses it.
App Store review
Apple’s reviewers sign in to check the Diligence app before it goes on the App Store, and again for each new version.
What the review sign-in sees
Only what’s ticked. Never People, private documents, questionnaires, anyone’s numbers, the Team Assistant or Presentation Studio.
For App Store Connect › App Review Information › Sign-in required:
User name
Password
Copy it now: Diligence shows this passcode only once. A new passcode replaces it.
CRM (Microsoft Dynamics)
The Prospecting Tracker can take each person’s calls and call-backs from the CRM, so they’re logged once.
Microsoft sign-in (from Microsoft Entra)
From the app registration “Diligence Online” (README: THE CRM). No password or secret.
What counts, from Power Automate
Empty: a completed Phone Call is a call; a Phone Call the flow’s Ahead step sends is a call-back (in the team’s flow: marked Call Back or Call to Book); a Phone Call its Booked step sends is a booking (marked Booked; for flows with that fourth step). Change it only with the text from whoever set up the flows.
One flow for the team
Your own flow sends everyone’s counts at once, so recruits have no flow to set up or change. Its key goes in that flow’s HTTP step (guide: Power Automate: CRM numbers to the Prospecting Tracker). It covers whoever is in Diligence with the tracker, or one location’s people only: when each location’s calls are read with a different CRM account, each flow has its own key for its location. Each person in the CRM is paired once with someone in Diligence: most by their name, automatically; you pair the others below. Anyone not paired is left out.
Check someone’s bookingsEach booked call the flows’ last runs sent with them on it, and what Diligence did with it.
For the flow’s HTTP step, under Headers: Authorization
Copy it now: Diligence shows this key only once.