Ability to mark a Portal item as a Favourite

[Drew_Sutton]

Within ArcGIS Pro add the ability to right-click on an item within the Catalog > Portal pane and mark an item as a favourite. These items could then be easily found within the Portal > My Favourites area.

This functionality is possible within the Catalog > Project pane OR if you favourite an ArcGIS Online or Living Atlas item via a browser.

Having the ability to favourite an item within ArcGIS Pro would make finding frequently used Portal, ArcGIS Online and Living Atlas items much easier and remove the need to go to a browser if you want to favourite and item.

[LindsayRaabe_FPCWA]

Was just about to post this idea myself - glad to see it's under consideration already. 

[PrabaniNaidoo1]

It would also be useful to mark a portal group as a favourite item both in Portal and ArcGIS Pro.

[PrabaniNaidoo1]

this would help with quicker access to portal groups with lots of data.

[PrabaniNaidoo1]

especially when you are part of many groups.

[HannahTam]

Our GIS team is currently teaching non-GIS staff members how to utilize streaming layers from ArcGIS Online in ArcGIS Pro. We have created an Open Data Portal to catalog our authoritative data, and we are working on developing the best method for bringing these streaming layers into, and storing them in Pro.

The "Data From Path" workflow has been our method thus far, but this option does not provide the longevity that adding a layer to favorites does. It would be extremely helpful for our workflow to have a button within the ArcGIS Pro interface that allows users to add AGOL hosted layers to their favorites. Currently, to add a layer to favorites you can only do so through the layer overview page in AGOL.

Adding a "Favorite to AGOL" button will simplify our instructions for locating/utilizing streaming layers, it will allow our staff to more easily access layers that are specific to their workflow, and it will create a more consistent overall workflow that doesn't require accessing AGOL from the web (our non-GIS staff members do not have publishing permissions, so we don't want them exploring the organization level site).