Table of Contents

Deployment

Altus for Project deployment has the following steps:

Altus for Project requires a one time permission to make the connections from your computer to the Altus installation in the Microsoft Dataverse and Microsoft Graph. Consent is required before this connection can be made. Due to many administrators disabling user consent, administrative pre-consent is recommended.

>>Admin consent to Altus for Project in your organisation<<

The following dialog will be displayed:

Why do we need these permissions?

Altus for Project needs the permissions to perform the following tasks:

  • Have access to use files
    • Altus for Project needs to access the MPP file directly to send a copy to the Altus service for analysis and publishing. This can be on the user's computer or on a OneDrive/SharePoint folder they have access to.
  • Sign in and read user profile
    • Altus for project needs to sign in the current user to Entra ID. This is the most basic permission available.
  • Read all users' basic profiles
    • When assigning users to tasks, Altus for Project needs to collect information about the assignees names, profile pictures etc.
  • Access Common Data Service as organization users
    • Altus for Project needs to communicate to the target Altus installation which resides in the organisation's Common Data Service (also called Dataverse).

With these permissions, all processing happens either on the user's computer or in the Altus instance in your M365 tenancy. No project data is sent to 3rd party services.

Deploy to PCs

There are two ways Altus for Project can be deployed:

  1. Self-serve: Download and install Altus for Project on each computer. See Self Serve.
  2. Corporate Deployment: When deploying to multiple PCs in a corporate environment it may be necessary to use a package manager product to automate the deployment. A possible example of how this can be done with Microsoft Intune is provided, but for other 3rd party deployment packing tools, please see the your vendor's documentation.

Self-serve deployment

To deploy Altus for Project onto a PC you will need:

  1. A computer that meets the minimum requirements.
  2. A user account that has permission to install software on your computer. (Local Administrator)
  3. Microsoft Project is already installed.

Download and install the MSI installer for Altus for Project:

Release Description Version Download Link
General Availability Recommended for most people Download

Once installed, Altus for Project will keep itself automatically updated to the latest version in the selected ring so you can get the latest updates and fixes.

Note

Downloading and installing Altus for Project requires local administrative permissions on the target Windows PC. If this is not achievable then please consult your administrator regarding a Corporate Deployment option

Microsoft Office Add-in Activation

For the Altus toolbar to be visible to users they also need to be able to have the Altus Project Add-in, activated within Microsoft Project. This will happen automatically unless the environment has limitations added to what Add-ins can be used.

If you cannot see the Altus Project Add-in after the app has been installed, check the Add-ins settings within your Microsoft Project Options.

This screen displays the Add-ins Options page in Microsoft Project

Edit this page