Implied Permissions as an End User, troubleshooting SR permissions
- End User in question is both an analyst/end user, so they have queue scope to Queue A
- Building an SR that is for a different department, it will belong dynamically to Queue B on submission
- The aforementioned end user/analyst can submit the SR, but can't see it in My Requests or looking it up in the console
Something about this just doesn't sound right - if they are an affected user, shouldn't they have implied permissions enabling them to view the request they submitted to a Support Group outside of their queue scope? Or does in fact a new queue have to be created allowing the end user/analyst in question the ability to view their own request?
It feels redundant and if anything problematic, as you can't create a Queue based on the Affected User = me. In which case, you might end up creating a Queue based on the Work Item Support Group and other qualifiers so they can view it. The inherit problem is by doing this, it means any user with access to this request could view someone else's request if they knew the Work Item ID.
Am I overthinking this?