Limit access to Issues report and Project Requests

David,

Product Management has reached back to me on this and asked that I have you submit an enhancement ticket on this where you can describe, in detail, the changes you are looking to have performed so they can better review this situation.

For the parts that you are looking for clarification on, just include that info too in the ticket so they can be sure to best identify exactly what you need clarified vs what behaviors you'd like to be changed.

Let me know if you have any questions.

Sincerely,
Mark Sayers

Hi David,

I have forwarded this question to Product Management and asked them for a response. I'll let you know, or they will post a reply here, when they have reviewed this further.

Sincerely,
Mark Sayers
TD Support

Mark, should I make a ticket somewhere for the Product Management group, or will you be checking with them on the exposure of the Issues module?

Okay, so those look like just the standard desktop modules in Project/Workspaces. I am not sure why the Issues module exposes other projects' Issues when Analysis is present, yet the other modules do not show other projects' plans/tasks.

The Product Management group perhaps could shed more light on the level of exposure for each of these modules/reports.

Mark, attached is a screenshot showing the reports I'm referring to for Issues and Tasks in the Desktop/Workspaces Desktop.  Let me know if that doesn't give enough info -

David

projectworkspaces_desktop.png

Hello David,

You're only going to see your own Projects/Workspaces when looking at the Projects/Workspaces application. I am wondering which report you are viewing where you report seeing only your own/assigned tasks?

It would appear the access to Portfolio Planning is enough to allow someone to approve pending requests. The Security Role permissions do not indicate that anything is able to be restricted so a user cannot approve a request. The roles do permit restrictions from staffing by default, yes.

Let me know on the question about the tasks report so I can confirm whether it is supposed to show only your assigned tasks or those on all projects if Anaysis is present.

Sincerely,
Mark Sayers
TD Support

Thanks, Mark.  So it seems that with "Analysis" on one's account and using different canned searches in Projects/Desktops, that you can see all Issues but only one's own Projects/Workspaces or one's own Tasks.  If that's correct, is there a particular rationale for having Issues be more exposed like that?

As far as Project Requests, it looks like simply having the "Portfolio Planning" app is enough to allow one to not only see, but to Approve (but not necessarily Staff) any Project Request.  Is that correct, or is there anything to prevent someone from approving any project request they can view in Portfolio Planning?

Sorry, I aim to stop after these questions!

David,

It is the expectation that if you have access to the Analysis application that Issues desktop module will allow you to see Issues from any project even if you aren't a member on them.

It does a check on the back end to verify for Analysis access of the user who's desktop it's on so it knows whether or not they should be able to see that info.

Sincerely,
Mark Sayers
TD Support

Hi Mark,

Looking more, specifically it's only when the user has Analysis that they can see Issues in that search from Projects on which they are not a member.  Attached is a doc showing that "MISTER TECH", who has Analysis, can see an Issue for a project on which he is not a Resource (nor sponsor nor manager).

Not sure if that's expected in Analysis, but it seems MISTER TECH can't see other Projects on some searches I looked at in Analysis, so I wouldn't expect him to see those project Issues either.  I can provide more shots if needed.

Issues_Visibility.docx

The Issues canned report should actually already be restricted such that only Issues on projects which you are a member of will appear in the desktop. Are you seeing specific instances where this is not the case? If so please provide some screen shots which show said issues and also demonstrate that you are *not* in fact a resource on that Issue's project at the time of seeing it in the module.

Hello David,

There are not currently any permissions or controls around that canned report which would facilitate restricting access to viewing Issues there, nor is the canned desktop module able to be deactivated at this time.

The Types for projects can be restricted so only certain groups can access them when Creating new projects/requests or associating services to a certain Project Type, but nothing specifically controls whether or not a user can view every Project Request that currently is pending in the system, no.

These might be good enhancement candidates to allow for greater restriction capabilities in these areas of the tool.

Let me know if you have any additional questions or concerns about these.

Sincerely,
Mark Sayers
TD Support