The systems Connect joins

One accounting job rarely lives in one application. Proxara Connect draws the exact context an approved piece of work needs from the systems the firm already runs, then acts back through those same systems. Each connection stays separately governed, and activating one is not blanket permission to read it.

The systems a Work Definition may draw on

Which of these a firm connects is the firm's decision. Each connection is separate, and none is a precondition for another.

Activating a connector is not permission to read the system

Authority is assigned to an exact source capability, for one role, inside one approved kind of work, at one revision. A provider does not become the firm's policy authority because its connector is active, and a system that supplies a role in one approved kind of work supplies nothing in another.

The definition names the role it needs. A versioned normalizer translates the provider's records into that role's neutral facts, so requirement, evidence, scope, relationship and status semantics belong to the firm rather than to one vendor's field names.

Each connection is governed on its own terms

Every connection carries:

• its own credentials, held inside the firm's environment;
• its own approval, and its own withdrawal;
• its own closed set of registered reads and typed writes;
• its own capability revision, health state and reauthorization;
• its own budget for how much one piece of work may query.

Several connections to the same provider family can coexist. No firm-wide switch stands in for a source.

The Microsoft permission boundary

Every Microsoft permission Proxara requests is delegated. Every read carries the signed-in employee's own credential, and there is no application-only permission anywhere in the read path.

The granted set is held by two independent checks: the infrastructure definition refuses to build an environment whose permission list falls outside the reviewed set, and the setup runner fails the run if the environment it has just built reports any other set. Acting is a separate consent. The consent screen the administrator approves is the authoritative list, and For the Microsoft administrator shows it as written.

Proxara does not invent a capability a provider does not offer

Each read and each write is a pinned descriptor for that provider, proven against its actual contract. Where a tax system exposes no safe supported write for a change, the result is a review artifact the preparer can act on rather than a fabricated mutation. A generic create-or-update tool pointed at a tax engine is refused.

When a source is unavailable

An absent system produces an honest partial result: what is known, which source is missing, which conclusion cannot be drawn, and what resumes when authority returns.

Where to go next