Delete a project record

Project records can be permanently deleted from Altus where the user has the appropriate permissions.

Important:
Deleting a Project is permanent and cannot be undone. Project deletion also affects related Project data. Always confirm the deletion through your organisation's approved governance and retention process before proceeding.

For administrators managing several obsolete or unwanted Projects, bulk Project clean-up can also be performed using Microsoft-native capabilities, rather than deleting Projects individually through Altus.


Delete an Individual Project

To delete a single Project from Altus:

  1. Open the required Project record.
  2. From the command bar, select Delete.

If You Do Not Have Permission

If you do not have permission to delete the Project:

  • A message will indicate that you have insufficient privileges.

Contact your Altus administrator or PMO for assistance.

If You Have Permission

A confirmation screen appears.

  1. Enter the Project Name exactly as requested.
  2. Select Delete to confirm.

Important:
Project deletion is permanent and cannot be reversed. Always check the Project carefully before confirming deletion.


Bulk Delete Projects Using Power Apps

Where multiple Project records need to be removed, an authorised administrator can perform the clean-up directly using Microsoft Power Apps rather than opening and deleting each Project individually in Altus.


This approach is intended for administrative clean-up scenarios such as removing multiple Projects that:

  • Were created in error
  • Are obsolete
  • Are no longer required
  • Have been confirmed for permanent removal through the organisation's governance process

Altus introduced support for bulk Project clean-up using Microsoft's native capabilities in the March 2026 release.

Important:
Bulk deletion should be performed only by an authorised administrator with the appropriate Power Apps and Dataverse permissions.

Because multiple Projects can be affected at once, confirm the records selected for deletion before performing the action.

Before Bulk Deletion

Before deleting multiple Projects, the administrator should confirm that:

  • Each Project has been approved for permanent deletion
  • The selected Projects are no longer required for reporting or audit purposes
  • The Projects should be deleted rather than Closed or Completed
  • Any linked external schedules have been considered
  • Any associated Microsoft 365 Groups or external collaboration assets have been considered
  • Organisational data-retention requirements have been satisfied

Best Practice:
Use bulk deletion as an administrative clean-up mechanism, not as the normal end-of-life process for completed Projects. Where Project history must be retained, use an appropriate Closed or Completed status instead.


Governance and Permissions

Deletion of significant parent records such as:

  • Projects
  • Programs
  • Portfolios
  • Bookable Resources

is typically restricted through centrally managed security permissions.

Important:
The ability to delete an individual Project from Altus and the ability to perform bulk administrative deletion through Power Apps depend on the user's assigned permissions.


Parent vs Child Records

Deletion protection applied to a parent Project record should not be assumed to prevent authorised users from managing every related child record independently.

Project-related records may include:

  • Risks
  • Issues
  • Tasks
  • Financial records
  • Deliverables
  • Decisions
  • Changes
  • Lessons
  • Other related records

Access to delete or modify these records depends on the user's permissions and the configuration of the relevant record type.


Cascade Deletion for Projects

When a Project is permanently deleted, related Project information may also be removed according to the relationships and deletion behaviour configured in Altus and Dataverse.

Important:
Consider the complete Project data footprint before deleting the Project, particularly when performing bulk clean-up.

External Components

Some components associated with a Project exist outside the Project record itself and may require separate administration.

For example:

  • An externally managed schedule should be reviewed separately.
  • An associated Microsoft 365 Group may require separate administrative management.

Do not assume that deleting the Altus Project automatically removes every related Microsoft 365 or external asset.


Portfolio and Program Considerations

Treat deletion of Portfolios and Programs separately from Project deletion.

Before deleting a Portfolio or Program, review its related records and organisational relationships to determine whether additional clean-up is required.

Where related records remain without their previous parent relationship, review those records against your organisation's retention and governance requirements.


Manage Orphan Records

Where a parent record has been removed and related records remain, authorised users can review the relevant central registers.

For example:

  1. Navigate to the appropriate register under Work, such as Risks or Issues.
  2. Select an appropriate central list view.
  3. Filter for records without the expected:
    • Project
    • Program
    • Portfolio
  4. Review the resulting records.
  5. Update, archive, reassign, or delete the records according to your organisation's governance requirements.


Close vs Delete a Project

Close or Complete the Project

Use this approach when the Project has finished but its history should remain available.

This supports continued:

  • Reporting
  • Historical analysis
  • Audit
  • Governance
  • Record keeping

Delete the Project

Use deletion when the record should be permanently removed, for example where an unnecessary or erroneous Project has been approved for deletion.

Tip:
In most cases, use the appropriate Closed or Completed Project Status for completed work rather than deleting the Project.


Key Considerations

  • Project deletion is irreversible.
  • Deletion should follow organisational governance and retention requirements.
  • Use Closed or Completed status where Project history should be retained.
  • Bulk Project clean-up is available to authorised administrators through Microsoft-native capabilities.
  • Bulk deletion should be treated as an administrative activity rather than routine Project management.
  • Review all selected Projects carefully before a bulk deletion.
  • Related Project information may be affected by deletion.
  • External schedules and Microsoft 365 components may require separate administration.
  • Deleting Portfolios or Programs may require additional review of their related records.
  • Access to deletion functionality is governed by security permissions.


Tips

  • Confirm with stakeholders before permanently deleting a Project.
  • Use Project closure instead of deletion for completed work that must remain available historically.
  • Review downstream reporting, Financials, audit, and governance impacts before deletion.
  • Use bulk deletion only where multiple Projects have been explicitly approved for clean-up.
  • Verify the selected Project records carefully before an administrator performs bulk deletion in Power Apps.
  • Consider associated Microsoft 365 Groups, SharePoint content, and external schedules separately.
  • Review related records after parent-record clean-up where additional remediation may be required.


Last updated: 10/27/26, 3:31 AM

Altus Help Centre