Restrict project access

[Guy.Baxter]

Hi all,

I have a couple of requirements I am struggling to meet and wondered if you can help. I have atlassian access and have integrated with Azure AD to bring across JSM users, JSM Admins, Confluence users, Confluence admins - this works fine. Here are the queries:

1. JSM Agents should only have access to their allocated project not all projects - how can this be achieved?

2. Portal customers - I will eventually have multiple projects and have 2 user groups. Some projects will be accessible to both, some to only one. User volumes are 1,000 and 15,000 in the other group so manual is not an option. I can see that assigning default groups to projects is a central setting - how can I manage this per project?

Thanks in advance.

[Joseph Chung Yin]

@Guy.Baxter -

Here are what you can do -

1)For each of your JSM projects, change the Customer permissions option to "Customer who are added to the project"

2) For both your agents, grant the needed agents by adding them into the project's "Users and Roles" to the ServiceDesk Team role.  So, if Joe Smith should only access project A and not project B, then he will not be in the project B.

3) For customer, you should associate them into different internal user groups.  Then use the internal user groups to be included in each project's "Users and Roles" section to the ServiceDesk Custoimer role.  You may need to build some automation to get customer added/removed to the internal groups to avoid manual operation.

Hope this helps,

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Guy.Baxter]

@Joseph Chung Yin  thanks for the reply.

Can you share any more information on how to approach the automation for customers?

Thanks.