Configure organisation policies
These settings apply across the whole organisation rather than to one document. The policies are under Settings → Policies, split across two tabs: Verification and Automation. All of them are restricted — “Only people who manage permissions can change this setting.”
Your own storage and transferring the organisation live on other screens, and each section below says where.
Recipient verification default
Section titled “Recipient verification default”Under Settings → Policies → Verification, Recipient verification sets the starting point for identity checks:
The starting point for every new recipient. Senders can raise or lower it document by document. Documents already sent keep the level they went out with.
Three things follow from that sentence, and each matters:
- It is a default, not a ceiling. Senders can move up or down per document.
- Changing it affects new recipients only.
- Already-sent documents keep the level they went out with. Raising the default does not retroactively strengthen documents in flight.
Set it to the level most of your documents need, rather than the strongest one available — see Signature levels.
What integrations and AI agents may do
Section titled “What integrations and AI agents may do”Documents created by API or AI start as drafts
Section titled “Documents created by API or AI start as drafts”Settings → Policies → Automation governs “Rules for documents created by external systems and AI agents.”
The policy is AI/MCP documents start as drafts:
With this policy on, documents created through the public API or by AI agents (MCP) are saved as Drafts for a person to review and send — they never go out directly. Documents already sent are unaffected.
Senders may choose the signing order
Section titled “Senders may choose the signing order”The second Automation policy is Allow simultaneous signing:
With this policy on, whoever creates a document (wizard, public API or AI agents) can choose to invite every signer at the same time instead of one at a time in list order. The default stays sequential. Turn it off to always impose the order.
Three things worth keeping apart, because they are easily confused:
- It comes switched on, in every organisation. You need do nothing to have it.
- On does not mean “all at once”. It gives senders a choice; each document still defaults to Sequential. A document only goes out simultaneous if someone picks that in the Recipients step — see Send a document for signature.
- Off, and the selector disappears. There is no warning and no error: every document goes out sequential, including those created through the public API and by AI assistants, which read the effective value in the response.
It does not affect documents already sent: each keeps the order it went out with.
AI access to analytics
Section titled “AI access to analytics”Also under Automation, AI access to analytics decides whether MCP-connected assistants can read your organisation’s numbers. It is off by default.
| Option | What it allows |
|---|---|
| Off | No assistant can read this organization’s analytics. |
| Aggregated metrics | Totals, trends and comparisons. Never a named person’s activity. |
| Detailed metrics | Adds per-entity detail, and only for people who already hold the permission to see it. |
The boundaries are explicit:
It never grants access to documents, content or keys — only aggregated metrics, and every request is written to the audit trail.
Detailed metrics does not widen anyone’s access — it only adds detail for people who already had permission to see it.
Store documents in your own Azure account
Section titled “Store documents in your own Azure account”This is not a policy: it is under Settings → Developers → Storage, and the tab only appears to the Owner and the Administrator. Storage connects your own storage:
Connect your own Azure Blob Storage account. Documents will be stored in your tenant’s storage instead of the shared AssinaJa storage.
Provide the Storage account URL (e.g.
https://suaconta.blob.core.windows.net) and the Container name, using
Azure Blob Storage (RBAC / Managed Identity).
Use Test connection before saving — it refuses to test until all fields are filled. The status then reads Connected or Not configured, with Verified on showing when it was last checked.
Transfer the organisation
Section titled “Transfer the organisation”Settings → Organization → Ownership — “Transfer the organization to another member.” Only the Owner sees this tab.