build 3.0.0 · aes-256-gcm / ml-kem-768 · eu/de · ram only

Paramant for Outlook — encrypted attachments from within your inbox.

The Paramant Outlook add-in lets you upload a file and insert a burn-on-read link directly from a compose or reply window in Outlook for Microsoft 365, Outlook on the web, and Exchange 2019.

Compatibility

Installation

1

Add from Microsoft AppSource

In Outlook, open any compose or reply window. Click the Apps button in the ribbon (or the three-dot menu on web). Select Get Add-ins. Search for Paramant and click Add.

Alternatively, your Microsoft 365 administrator can deploy the add-in to your entire organisation from the Microsoft 365 admin center under Settings → Integrated apps.

2

Open the Paramant task pane

After installation, open a compose window. A Paramant button appears in the ribbon under the Message tab. Click it to open the task pane on the right side of the window.

If you don't see the Paramant button, close and reopen Outlook. On Outlook for the web, hard-refresh the page (Ctrl+Shift+R).

3

Enter your API key

The task pane shows an API key field on first run. Paste your Paramant API key and click Save. The key is stored in the add-in's local settings — it is not shared with Microsoft or stored on their servers.

Your API key is in Paramant Dashboard → API keys. If you don't have one, generate one there.

Sending a file

1

Open the task pane and select a file

With a compose window open, click Paramant in the ribbon to open the task pane. Click Choose file and select the file you want to send. A progress bar appears during upload.

2

Set expiry and click Send

Choose how long the link should remain active (1 hour to 7 days). Click Upload and insert link. The task pane inserts a formatted line into your email body with the secure download URL.

3

Send your email normally

The Paramant link is now in the email body. Edit surrounding text if needed, then send. Your recipient clicks the link, downloads the file once, and the link and file are deleted.

Organisation-wide deployment

Microsoft 365 administrators can push the add-in to all users without requiring individual installation. In the Microsoft 365 admin center: Settings → Integrated apps → Get apps, search for Paramant, and deploy to specific users, groups, or the entire organisation.

Users receive the add-in on next Outlook restart. API keys must be configured individually by each user unless your organisation provides a shared key via a managed deployment.

Do not use a single shared API key across all users in a large organisation — transfers from all users will appear under one account, and revoking the shared key will lock everyone out simultaneously. Use per-user or per-team keys.


Troubleshooting

The Paramant button does not appear in the ribbon.
Close and reopen Outlook. If the button is still missing, go to File → Manage Add-ins and verify Paramant is listed and enabled. On Outlook for the web, check that pop-ups are not blocked for outlook.office.com.
Task pane opens but shows a blank screen.
This is usually a network issue. The add-in task pane loads from addin.paramant.app. Ensure your firewall or proxy allows outbound HTTPS connections to paramant.app and addin.paramant.app. Check paramant.app/status for any active incidents.
Upload fails with a network error on Exchange on-premises.
Exchange 2019 add-ins require outbound internet access from the client machine (not from the server). The Outlook desktop client makes the upload request directly to paramant.app. Verify that client machines can reach api.paramant.app on port 443.
Our IT policy requires add-ins to be approved before installation.
Ask your Microsoft 365 administrator to approve Paramant in the admin center under Settings → Integrated apps → Add-ins. Alternatively, request admin-deployed installation so the button appears automatically for all users.

Related

Gmail extension

Same workflow for Gmail in Chrome.

API key vs TOTP

Understanding the credentials used by the add-in.