Currently, when a project or portfolio as a child item is added to a portfolio, the portfolio owner is automatically granted editor access to that project. This behavior was implemented to ensure that portfolio owners could always view and manage their child items, regardless of privacy settings.
As part of a new update, portfolio administrators will now be notified if there are items within their portfolio that are restricted due to privacy rules, with the option to request access. To align with this new functionality, the automatic addition of portfolio owners as editors will be removed.
This change will give administrators and developers more control over access to portfolio child items, both in the Asana web app UI as well as the API.
You can opt-in to this change with the no_adding_owner_to_portfolio_items flag.
Who is affected
This change affects users who manage portfolio contents via the add a portfolio item endpoint.
Timeline
This feature will be live in the API and available for opt-in on December 18th, 2024
The feature will become opt-out around April 2025
Use the no_adding_owner_to_portfolio_items flag to opt-in or out of the feature
Usage
Though there is no change in the request or response, there is a side effect that will no longer happen under the new behavior: we will no longer attempt to add the portfolio owner as a member of the work item added to the parent portfolio.
This update is a great step forward for improving privacy and giving portfolio administrators more control over access to child items. The notification and access request feature will make managing restricted items more transparent and efficient. Opting in early with the no_adding_owner_to_portfolio_items flag ensures you’re prepared for the change ahead of its default rollout in April 2025!