Table of Contents

Integrating External Idea Registers with Altus

Many organisations capture ideas outside of Altus, often in Microsoft 365 tools such as SharePoint. This is common in larger enterprises where licensing models, governance requirements, or submission scale influence how idea intake is structured.

Altus supports this model through a flexible, Microsoft-native integration approach.

Where ideas are managed externally, we recommend implementing an organisation-specific Power Automate workflow.

How it works

  • A flow is triggered on create, update, or delete events in a SharePoint list or similar Microsoft 365 source.
  • The workflow applies required organisational logic, including validation, mapping, transformation, and filtering.
  • The flow inserts or updates the corresponding record in the Altus Ideas table using a Microsoft Dataverse connection.

Why This Approach

  • Keeps idea capture outside Altus where appropriate.
  • Avoids unnecessary licensing uplift for submit-only users.
  • Leverages standard Microsoft 365 capabilities.
  • Supports organisation-specific structures without constraining design.

Because external idea registers vary significantly across organisations, this pattern is delivered as part of solution design rather than as a fixed out-of-the-box setting. It ensures flexibility while maintaining alignment with the Microsoft ecosystem.

This configuration can be delivered by an Altus implementation partner. Organisations with internal Power Automate expertise can also implement the integration directly using the same Microsoft-native architecture.

Edit this page