Access and logging
Who can sign in and how, why Proxara cannot, how support works without access, and what the logs record and never record.
Updated 2026-10-16
Only the people your shop assigns can open a loan, and only through your own sign-in. Proxara is not one of them.
Signing in
- Your identity provider: people sign in with their work Microsoft accounts through your Microsoft Entra ID. Your MFA and conditional access rules apply to every sign-in, because they are your rules on your tenant.
- Inside Encompass: Proxara opens as a Custom Tool your administrator switches on. Encompass hands over the officer’s own sign-in, which Proxara checks with ICE before it opens the loan.
- Assignment required: the install is an enterprise application in your Entra ID that only assigned people can open. Removing someone from it, or disabling their account, refuses their next sign-in, and a sign-in they already hold lapses within the hour.
- Two roles: an officer works loans; an administrator also sees the install’s settings and its records. Your shop decides who holds each.
Proxara’s access
None. Proxara has no account, credential, role or standing access in your environment, and the installer confirms that no identity outside your tenant holds a role when it finishes. There is no temporary access to grant either: nothing in the install is built to let Proxara in.
Support without access
When something needs Proxara’s help, your IT exports a diagnostics bundle from the install and decides whether to send it. It carries versions, timings, error types, rule identifiers and health, and never document text, borrower details or anything that identifies a loan. If a screen share helps, your team shares its own screen, on its own terms, and nothing is installed or left behind.
What is logged
| Event | What the record holds |
|---|---|
| A sign-in | Who, when, and from which application |
| A document or page opened | Who, which loan and document, and when |
| An export or a result written to your LOS | Who, what, where it went, and when |
| A deletion | What was deleted, when, and whether a person closed the loan or it went untouched too long |
| A setting or role changed | Who changed what, from what to what, and when |
| An outbound call | The destination, from the list in Every connection, and when |
The logs stay in your tenant, in your own Log Analytics workspace, where your security team can search them, keep them as long as your policy requires and send them to the monitoring you already run.
What a log never holds
Document text, borrower names, Social Security numbers, account numbers, addresses or any other fact read from a page. Operational logs carry a loan’s reference, versions, timings, rule identifiers and error types, enough to trace a problem without seeing the file.