Access level Controls

[Pavan Kumar Tatavarti]

I am handling three different vendors in my process and they don't want to disclose their data with other vendor. So they were requested that do we have any that kind of controls which we can provide them to mitigate these issues in production. 

I am investigating thoroughly on this access level controls and how to provide and what types of accesses need to give to others as a admin to run our operations smoothly without having this kind of issues in future.

We should get clarify that, whether do we have control point like should not view the request by other client which is not pertaining to them. Please refer the below examples of issues in access levels. Could you please check and advise on priority with solution. 

• Genpact can access all
• Business can access only those requests for their business
• Provider can access only those requests for their action
• Business user and approver should not have Jira admin access
• Auto routing for business approval and provider action

[Ste Wright]

Hi @Pavan Kumar Tatavarti 

Can I clarify...

• Is this in Jira Service Management, so 3 different vendors as Agents accessing one Jira instance?
• Do they have different JSM Projects?
• Can you specify the different levels, with examples?
• What access to Jira does each level get?

I think it's likely you're going to need a mix of...

• Project Permissions
• Issue Security Levels - as an example, these could be set automatically at creation using Automation - and Businesses/Providers could be given access in the Agent view, based on User Groups in the Security Levels

^ Let us know some more specifics, so we can try to detail a better example :)

Ste