All Collections
Recommendations in Aurelius
Cross-Project Recommendations
Cross-Project Recommendations
Zack Naylor avatar
Written by Zack Naylor
Updated over a week ago

Cross-Project Recommendations let you create recommendations with key insights from multiple projects.

What is a Cross-Project Recommendation?

A Cross-Project Insight is just like a Recommendation from any project you have in Aurelius. However, Cross-Project Recommendations allow you to capture recommendations, new ideas and suggestions using key insights from multiple projects. Think of them as "global recommendations".

Just like any Recommendation, Cross-Project Recommendations have six parts:

  1. Name

  2. Description

  3. Tags

  4. Supporting Key Insights

  5. Status

  6. Type

How to Create Cross-Project Recommendations

You can make Cross-Project Recommendations in several ways.

From the All Tags page

Select Key Insights > Create New Cross Project Recommendation > Add your name, title and details

Creating Cross Project Recommendations from the All Tags page in Aurelius

From the All Insights page

Select Key Insights > Create Cross Project Recommendation" > Add your name, title and details

Creating Cross Project Recommendations from the All Insights page in Aurelius

From Universal Search

Select Key Insights > Create New Cross Project Recommendation > Add your name, title and details

Creating Cross Project Recommendations from the Universal Search results page

Adding your name, description, tags, status and type for a cross-project recommendation

Creating a Cross Project Recommendation with details

Cross-Project Recommendations vs. Recommendations (on a project)

Simply put, Cross-Project Recommendations are Recommendations or ideas/suggestions/next steps made with key insights from multiple projects. Cross-Project Insights live on the All Recommendations page by default. They can also be added to Collections.

Recommendations are findings made within a single project and key insights from that project only. Recommendations live in the project they were created by default.

Did this answer your question?