Configure organisation policies
These settings apply across the whole organisation rather than to one document. The policies are under Settings → Policies, split across four sub-tabs: Signatures, Automation, Chat and Document search. 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 → Signatures, 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 outside the browser start as drafts
Section titled “Documents created outside the browser start as drafts”Settings → Policies → Automation governs “Rules for documents created by external systems and AI agents.”
The policy is Documents created outside the browser start as drafts:
With this policy on, documents created through the public API, by AI agents (MCP) or in the Telegram chat are saved as Drafts for a person to review and send in the browser — they never go out directly. With it off, sending from Telegram always asks for a final confirmation. Documents already sent are unaffected.
Senders may choose the signing order
Section titled “Senders may choose the signing order”Under Signatures, right after recipient verification, comes 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.
Chat interaction
Section titled “Chat interaction”Settings → Policies → Chat decides what members can do in a Telegram chat linked to their account. The Chat interaction card puts it this way:
What members of this organization can do in a chat linked to their account (Telegram). Everything is off by default.
| Policy | What it allows |
|---|---|
| Allow notifications in chat | “Invitations, reminders and completions of this organization’s documents reach the linked chat of whoever receives them, per each person’s notification matrix.” |
| Allow creating and sending documents in chat | “Members who can send documents create them in the chat (/criar) and send the drafts (/enviar), always with a final confirmation.” |
| Allow document files in chat | “Anyone who can see a document can ask the bot for the signed PDF and the completion report. Files stay on Telegram’s servers.” |
| Allow signing in chat | “Simple, initials, OTP SMS and identity-confirmation documents can be signed in the chat, with a code by email. CMD and Chave Móvel never.” |
Each policy applies to this organisation’s documents, whoever receives them: an outside signer gets the alert in their own chat if this organisation allows it.
Creating in the chat works together with Documents created outside the browser start as drafts: with that policy on, whatever is created in the chat stays a draft and is sent from the browser. What each person sees and does on their side is in Use AssinaJá in Telegram.
Search inside document content
Section titled “Search inside document content”Under the Document search sub-tab, Search inside document content turns on searching for words that are inside the documents, not only in the name, the subject or the people. It ships off, and only members who manage permissions can change it.
When it is on, the platform stores the text of every page of published documents — drafts are left out — and indexes them in the background. The panel keeps track: “Indexing: 12 of 40 documents”, and Cancel everything in the queue stops what has not started yet. Scanned pages, with no text, are read by a text-recognition service; the panel counts the Paid OCR pages. Without that service configured, a document made only of scanned pages ends up Skipped — in a mixed document the text pages are indexed and the scanned ones have no searchable text — and the panel says so:
No OCR configured: scanned documents (without a text layer) are marked “Skipped”.
Turning it off asks for confirmation — Turn off and delete — because it is a deletion:
Turning this off cancels any indexing in progress and deletes the stored text of every document, including text-recognition results already paid for. Turning it back on indexes everything again.
The switch may be blocked, and the panel says why:
This organization’s plan does not include content search.
The database has no search index — this feature cannot be turned on in this environment.
Indexed text only serves people who can already see the document. Searching for a word never shows, or lets anyone infer, a document they have no access to — not in the list, not in the counts, not in the excerpts.
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.