Agent security checklist

An agent with a JustDocs key can prepare documents and ask to email them to people. Work through this list before you connect one in production.

Before you make the key

• [ ] Use an agent key, not an API key. Its sends always wait for a person.
• [ ] One key per agent and per place it runs. Then you can revoke one without the others, and last used shows which one acted.
• [ ] Only the permissions it needs. An agent that answers questions needs read only. One that drafts, or saves templates, needs documents. Give send only if it should ask to send. send also lets it void requests at once, without approval.
• [ ] Recipient domains, if it only deals with known companies, such as your own domain for internal agreements.
• [ ] A low daily send limit. Start with a few a day and raise it when you trust the pattern.
• [ ] A short expiry. 30 to 90 days, then make a new key on purpose.

Where the key lives

• [ ] In the client's secret settings, a secret manager, or an environment variable. Never in a prompt, a document, a template, or a file you commit.
• [ ] Never in a browser or a mobile app. Anyone who can open it can read the key.
• [ ] If you run a connector for many users, keep each workspace's key separate and encrypted.

Approvals

• [ ] Decide who approves. Every owner and admin can. Keep that group small and aware.
• [ ] Read before approving. The approval shows the title and every address. Open the request to check the document.
• [ ] Alert on approval.requested with a webhook on Teams & Platform, so sends don't sit for days. Approvals expire after seven days.

Prompt injection

Documents, answers and emails can contain text written to steer an agent. JustDocs limits what that text can achieve:

• No tool can sign, or return a signing link.
• Every send waits for a person, who sees the real addresses. The one action that doesn't wait, voiding, can only cancel.
• Recipient domains and daily limits apply, and are checked again when a person approves.

Still, tell your agent to treat document content as data, not instructions. Approve only what you expected.

Watch it

• [ ] Check each key's last used time and address now and then. An address you don't recognise means the key is being used from somewhere you don't know about.
• [ ] On Teams & Platform, send webhooks to your logs or security tooling: approval.requested, approval.decided, request.sent.

If a key leaks

1. Revoke it on the API & agents page. It stops working at once.
2. Decline any pending approvals it asked for under Approvals.
3. Void any requests it shouldn't have sent.
4. Make a new key with the same limits, and update the client.
5. Tell us at security@tryjustdocs.com if you think JustDocs itself is involved.