For admins and security reviewers
Connect a Salesforce sandbox
Salesforce sandboxes and scratch orgs only — never production. Connecting Milita is a short, guided process. You stay in control of access the whole way, and nothing is ever installed inside your org.
1. Sandbox-first by default
We connect only to Salesforce sandboxes and scratch orgs, never production. Production orgs are rejected at connect time by an org-type check, so a misconfiguration can’t point us at live data. A full or partial sandbox that mirrors your real configuration gives the most faithful coverage.
2. A least-privilege automation user
You create a dedicated integration user for Milita with the minimum permissions needed to exercise the processes in scope — not an administrator. This keeps the blast radius small and makes access easy to review and revoke.
3. JWT authentication
We authenticate using the OAuth 2.0 JWT Bearer flow with a connected app and a per-environment signing key. No long-lived refresh tokens are stored on our side, and short-lived access tokens live in memory only.
4. A scoped permission set
We’ll provide a permission set tailored to the objects, fields and tabs your in-scope processes touch. You assign it to the automation user — and nothing more.
5. Certificate revocation is the kill switch
Because access hinges on the JWT signing certificate, you can sever Milita’s access to your org instantly and unilaterally by revoking that certificate in Setup. No tickets, no waiting on us.
You don’t do this alone. Onboarding includes a working session where we walk your admin through each step and verify the connection before any Proof runs.
Connect a sandbox and prove one process.
Free for one Promise, forever. Revoke our access any time from Setup.