INTEGRATIONS
Bring identity, spreadsheets, external references and channel alerts into your PMO workflow. Organisation and workspace policies determine what can be used.
Configured Microsoft sign-in, with administrator-controlled account provisioning. Requires an Entra application registration and workspace configuration.
No SCIM or directory synchronisation is promised.
Google sign-in for invited or existing people. Separately consent to picked Sheets imports, supported Drive links and exports to a new Google Sheet.
Sign-in alone does not grant access to Drive. Data operations require connection, consent and policy allowance.
Import risks, issues and new draft projects through source selection, column mapping, row checks and a queued commit. Export supported reports with their filters.
Known source IDs are skipped on spreadsheet re-import; this is not an update-sync engine. Task and WBS migration are outside this import scope.
Attach supported external file links to project documents. Microsoft links are pasted; Google Drive picking uses the person’s permitted connection.
Links do not satisfy required gate evidence. Microsoft links do not imply Graph file lookup or file-content synchronisation.
Route configured events to a Teams Workflow webhook or Google Chat space. The message points people back to the authorised AEVU record.
Alerts contain a short message and secure link, without project names, financial figures or AI content.
Read a configured SuiteTalk SOAP saved search to create or update project records and associated clients. Preserve AEVU-owned governance decisions when matching existing projects.
This is not ERP transaction write-back, invoice synchronisation or financial reconciliation. Configure credentials and confirm rollout scope.
CONTROL THE CONNECTION
The organisation controls which capabilities its workspaces may use. Plan and platform availability also apply.
Connect the required account or service and configure the permitted operations. A saved connection is not the same as a successful run.
Supported queued operations expose status and failure information. The NetSuite connection retains its own import flow.
A CLOSER LOOK
No. Integration availability depends on plan entitlements, organisation and workspace policy, user permission and provider configuration. Confirm the capabilities required for your rollout.
No. A link to a file in another service does not satisfy a required document or stage-gate condition.
Production readiness requires the appropriate provider credentials, consent configuration and end-to-end checks. A connection screen or capability label alone is not evidence of a successful production integration.
BRING THE WHOLE PICTURE INTO FOCUS
Explore AEVU around a real workflow your team needs to improve.