Roll out Word in Microsoft 365

As a Microsoft 365 administrator, you deploy Redact in Word from the Microsoft 365 admin center with komplai's manifest file. The people you assign then find it in Word without installing anything. Redact in Word describes what they see and what is sent.

Before you deploy

In komplai:

Your organisation's agreement includes Redact's API and Word add-in. Contact us if it does not.
Everyone who should use Word is invited to komplai, under Organisation → People → Invitations (/team/invitations) in the hub. See Invitations.
They have access to Redact. An administrator assigns it under Organisation → People → Tool access (/settings/apps).
People sign in through komplai's sign-in. If your organisation signs in with Entra ID, see Sign-in with Entra ID and AD FS.
Until your agreement covers personal data, Word shows Test data only, and people must use test data. See Processing approval.

In your network, allow HTTPS to:

Address	Used for
`https://hub.komplai.dk`	The task pane and the sign-in and connection pages
`https://auth.komplai.dk`	Sign-in
`https://api.komplai.dk`	Scans
`https://word.komplai.dk`	The manifest file and the icons

In Microsoft 365, your setup must support centralized deployment of add-ins. See Microsoft's requirements.

The manifest

What	Value
Manifest URL	`https://word.komplai.dk/manifest.xml`
Installation guide	word.komplai.dk
Name in Word and the admin center	[PROD] komplai for Word
Provider	[PROD] Progressify ApS
Ribbon	The [PROD] komplai tab with the Open Redact button
Host	Word only
Permission	Read and write the document

The hub also links the manifest and the installation guide under APIs and integrations → Connect a tool (/api-access/clients).

The manifest loads the task pane from https://hub.komplai.dk/office/word. Changes to Redact in Word therefore reach your users with the hub, without a new manifest.

Deploy the add-in

Go to admin.microsoft.com.
Open Settings → Integrated apps.
Choose Upload custom apps.
Choose Provide link to manifest file and paste https://word.komplai.dk/manifest.xml, or upload the downloaded manifest.xml.
Assign the add-in to the users or groups it applies to. Start with a few pilot users.
Accept the permissions and finish the deployment.

Microsoft can take a while to show the add-in to every user. A user who has Word open must quit it completely and open it again.

Test with pilot users

Test installation, sign-in and a scan in the versions of Word your organisation uses before people start using the add-in. Test Word for Windows and Word on the web separately: one working does not show that the other does. Use a document with fictional information.

Open Word and check that the [PROD] komplai tab has the Open Redact button.
Choose Open Redact, then Sign in, and sign in with a komplai account.
On Connect Word, check the organisation's name and choose Connect Word.
Choose Scan document, review the findings and apply a few replacements.
Read the document through, then choose Disconnect.

If the task pane says Update Word to use this add-in, that version of Word lacks WordApi 1.6, DialogApi 1.1 or DialogOrigin 1.1.

Test on one Windows PC with a shared folder

For a test on one PC before central deployment, Word for Windows can load the add-in from a trusted shared-folder catalog:

Put manifest.xml in a folder and share it (right-click → Properties → Sharing).
In Word, choose File → Options → Trust Center → Trust Center Settings → Trusted Add-in Catalogs.
Paste the network path, such as \\server\folder, choose Add catalog and tick Show in Menu.
Restart Word, then choose Insert → My Add-ins → Shared Folder.

Support your users

The button is missing: check the assignment in Integrated apps, and ask the user to quit Word completely and open it again.
The connection is refused after sign-in: the user chose the wrong organisation, or has no access to Redact. Check Tool access in the hub.
The task pane is blank: the network blocks one of the addresses above.
Ending a connection: each Word connection is a personal API key that expires after 24 hours. The user ends it with Disconnect, or revokes it under API keys (/api-access) in the hub.