Altus For Word
Simplify Project Documentation with Altus
Introducing Altus for Word, the quick and easy way to produce Microsoft Word documents that contain Altus Project data.
Collaborative Document Creation and Management
- Synchronise Altus Project Data into Microsoft Word: Add and update Altus Project data directly into Word documents without needing to manually enter information. Project Details are imported as fields while Project registers are imported as customisable and formattable tables.
- Use Templates generated by other Altus users: Pick up and synchronise your Altus Project data effortlessly into templates created by any Altus user.
- Brand and Style Documents: Documents and templates retain the rich formatting you give them using Word.
- Work Together: Collaborate on documents with both Altus and non-Altus users.
Project Lifecycle Document Templating Made Easy
- Create Project Templates with Ease: Use Altus project data to effortlessly create Word documents and document templates.
- Share Templates: Distributed templates can be used by all Altus users for consistent documentation within your Portfolio or organisation.
This guide provides all necessary information to download, install, and use the Altus For Word Add-In across your organisation.
Installation
This process need only be performed once per organisation by an Administrator.
Download Manifest
Please download the manifest file from the following link:
Deployment via 365 Admin Center
To deploy the Altus For Word Add-In via the Admin Center for your organization:
Log in to the Microsoft 365 Admin Center:
- Visit https://admin.microsoft.com and sign in with your admin credentials.
Navigate to Integrated Apps:
- In the left-hand navigation pane, select Settings and then choose Integrated apps.
Add a new Add-In:
- Click on Add-ins.
- Select Deploy Add-In at the top of the page.
- Click on Next to proceed past the introductory information.
Upload the Add-In Manifest:
- Choose the option to Upload custom apps.
- Click on Upload your add-in and select the manifest file from your computer.
- Follow the prompts to upload the manifest file.
Users
- Assign users or groups who will have access to the Add-In.
Review and Set Permissions:
- Review the permissions requested by the Add-In.
- If acceptable, provide consent on behalf of your organization by selecting the appropriate option.
Deploy the Add-In:
- Complete the deployment process by following the on-screen instructions.
Granting Consent
Altus for Word will require consent to make the connections on behalf of the user to the Altus installation in the Microsoft Dataverse. If the M365 EntraID is configured not to allow users to provide consent themselves, then an Administrative pre-consent will be required. It is recommended that an M365 use the following link to pre-consent on behalf of users to ensure that they are nt prompted during their initial usage of the product:
A screen similar to the following will be presented:
Supported Word Versions
The following versions of Microsoft Word are supported:
- Browser-based version of Word (recommended)
- Desktop version support will be provided on a best effort basis as there are many different versions of Microsoft Word. We will update the table below as information becomes available.
Word version | Support Status | Lifecycle End Date |
---|---|---|
Word Online | Supported * | ♾️ |
Word M365 | Supported | ♾️ |
Word M365 for Mac | Possible | ♾️ |
Word for IOS | Possible | ♾️ |
Word for Android | Unsupported | ♾️ |
Word 2021 | Possible | Oct 13, 2026 |
Word 2021 for Mac | Possible | Oct 13, 2026 |
Word LTSC 2021 | Possible | Oct 13, 2026 |
Word LTSC 2021 for Mac | Possible | Oct 13, 2026 |
Word 2019 | Possible | Oct 14, 2025 |
Word 2019 for Mac | Unsupported | Oct 10, 2023 |
Word 2016 | Possible | Oct 14, 2025 |
Word 2016 for Mac | Unsupported | Oct 13, 2020 |
Word 2013 | Unsupported | Apr 11, 2023 |
Word 2008 for Mac | Unsupported | Apr 9, 2013 |
(* Solution impacted by Microsoft Word Online formatting limitations)
Warning
If the support status is "Possible" then Altus for Word is untested and may have issues or not work at all.
Architecture
Altus for Word utilises the Office add-in extensibility model to provide automation and templating facilities in Microsoft Word. It runs in the web browser or webview control on the end-user's computer, and is supplied by Altus, but does not send any customer data via Altus run infrastructure. All customer data is sent only to and from the end-user's computer and the Power Platform environment. All data is encrypted in transit and secured using OAUTH connections to Entra ID.
Known Limitations
Placeholder Text
When a document has an inserted field that is yet to be updated by Altus For Word, such as when first opening a templated document, placeholder text will appear in the field control, representing the field name to be fetched.
A current limitation of Word in Office for the Web is that this placeholder text will not appear. These fields will appear blank until updated by Altus For Word
Word in Read-Only Mode
Microsoft currently does not expose a method for Add-Ins to detect what mode a document is in (Editing, Reviewing, Viewing). Functionality in these modes therefore may not perform as expected, for example if attempting to insert or update data.
Unsupported Fields
The following fields cannot be added to a document:
- createdonbehalfby
- exchangerate
- importsequencenumber
- modifiedonbehalfby
- overriddencreatedon
- owningteam
- timezoneruleversionnumber
- utcconversiontimezonecode
- versionnumber
Unsupported Field Types
The following field types are currently not supported:
- Number : Language Code - The numeric value on its own has no obvious meaning.
- Number : Duration - The numeric value on its own has no obvious meaning.
- Number : Time zone - The numeric value on its own has no obvious meaning.
- Currency - Primary currency field is allowed, but the _base value is suppressed.
- File : File - Both the field and the _name value are suppressed.
- File : Image - The field and the _url,_timestamp, and _timestamp@...FormattedValue fields are suppressed.