Configure organisation policies
These settings apply across the whole organisation rather than to one document. All of them are restricted — “Only people who manage permissions can change this setting.”
Recipient verification default
Section titled “Recipient verification default”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”Automation governs “regras para documentos criados por sistemas externos e agentes AI.”
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.
AI access to analytics
Section titled “AI access to analytics”AI access to analytics decides whether MCP-connected assistants can read your organisation’s numbers. It is desligado por defeito.
| 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”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 Verificado em showing when it was last checked.
Transfer the organisation
Section titled “Transfer the organisation”Ownership — “Transfer the organization to another member.”
Your own password
Section titled “Your own password”Settings → Personal → Security is where you change your password. The card also tells you what you cannot change there: “Your account password. Two-step verification by email is always on.”
See Change your password and Two-step verification.