Notifications for Inherited Permissions | Community
Skip to main content
O
OliviaMi
Level 4
February 20, 2023
Solved

Notifications for Inherited Permissions

  • February 20, 2023
  • 1 reply
  • 1048 views

Hello - when we launch a project from a template or switch the status from Planning to Current, or Current to Complete - do people with "Inherited Permissions" (because we have shared our portfolio with them) get those email notifications as well? Thanks! 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by William--

No, having inherited access to a project does not trigger any notifications about that project.

If someone with Portfolio access receives a project-related notification, it's because they are also on the project through some other method, like a task assignment, or because they own the Portfolio or Program to which the project was added.

1 reply

William--
Community Advisor
William--Community AdvisorAccepted solution
Community Advisor
February 21, 2023

No, having inherited access to a project does not trigger any notifications about that project.

If someone with Portfolio access receives a project-related notification, it's because they are also on the project through some other method, like a task assignment, or because they own the Portfolio or Program to which the project was added.

If you like my content, please take a moment to view and vote on my Idea Requests: https://tinyurl.com/4rbpr7hf
C
CR17506599
Level 4
March 15, 2023

We've also been trying to track down similar notifications issues in our Workfront instance.  We thought it could be 'inherited permissions', but after a little more digging it seems like it's the 'People' section of our main request queue project.  Anytime one of our staff is assigned to a request, they are added back to the 'People' section of the request queue project.  They then start getting notifications about that request queue (example, someone submits a new request and adds a document, they get a notification that a document has been uploaded). 

Does this sound correct?  Is there a way to prevent these types of notifications specifically?

William--
Community Advisor
William--Community Advisor
Community Advisor
March 15, 2023

That is correct. 

It sounds like your request queue is not configured to take full advantage of routing rules. Using routing rules is always advised. This allows you to make a queue broadly accessible to many/all users and depending upon the queue topic they select to submit their request, it is routed to a separate project that is privately managed by the working team. 

For example, I publish a queue called "Software Support Requests" and create three queue topics: Microsoft, Adobe, and Zoom. I can create a routing rule for each of those queue topics that specify any inbound request is immediately routed to a separate project. If the user selected the Microsoft queue topic, their request gets routed to the separate project called "Microsoft Support Requests." With this setup, a user assigned to a request in Microsoft Support Requests will get added to that project's project team, but not be added to the project teams for Adobe Support Requests or Zoom Support Requests - those teams no longer need to work out of the same project or get notifications about one another's work.


If you like my content, please take a moment to view and vote on my Idea Requests: https://tinyurl.com/4rbpr7hf
Terms & ConditionsAccessibility statement

Loading footer...