Please vote for this QUICK WIN that addresses CURRENT GAP and SECURITY RISK:
QUICK WIN: We need a function for CurrentUserInContactGroup similar to CurrentUserInTeam()
Why? For elevated access, SECURITY reasons, and overall improved UI, user experience, and to satisfy business requirements and business processes.
When? For situations where Contact Group members require elevated access.
Elevated Access such as Quick Actions, Command Buttons, Field visibility, Field Required Rules.
For example CAB Members for Change, Knowledge Advisory Group for Knowledge, and Approval Contact Groups for Approvals and Service Requests.
User Stories:
- As a Contact Approval Group member for example I need to have access to override Approvals.
- As a CAB Approval Group member for example I need to have access to edit certain fields on a change request, such as Scheduled Start/End Date, etc.
- As a Knowledge Advisory Group member I should have the ability to Publish Knowledge Articles. The list goes on.
Current GAP, RISK, and Opportunity:
– Switching between Change Manager, Knowledge Manager, SDM, etc) is very cumbersome, limiting, and poses a SECURITY RISK.
For example a CAB Member should not have full Change Manager Access. Same applies to Approval Contact Group Members, Knowledge Advisory Board Members and so on.
Especially Approval Contact Group members have very specific members (Department Heads for example) that should have some additional functionality and security rights but as an Analyst or Self Service User.
ITSM/ITAM/ESM Blog 
You must be logged in to post a comment.