Restricting access to all tickets within an organisation to designated users
Asked by Alex:

We're currently evaluating JSM for our service desk solution, but we have a very specific use case and I cannot work out whether what we need is achievable.

What we would like is the following.

* Our product is installed on multiple client sites. We want to set up an organisation which will represent each client site, and allow any users in those organisations to raise requests.
* Each user should be able to view the status of their own requests
* For each organisation, there will be one or more "superusers" which can view all requests for that organisation, regardless of who made the report.
* Users from one organisation (ie, one client site) will not be able to see requests from another organisation.

Our preferred workflow is that a user will submit a report via email. When this comes in, if that user is not a member of an organisation yet, we will add them to the appropriate one.

From that point on, the workflow should behave as above.

Is this possible with JSM? I can see a way to allow all members of an organisation to see all requests within the organisation, but I cannot find a way to restrict users to only see their own requests, while still allowing a more privileged user to see all requests within the organisation.

Many thanks


Answers:
author: Jovin
body: Hi [@Alex](/t5/user/viewprofilepage/user-id/5239945)

This is standard operation for when you work with Organizations within JSM! Here are some configuration notes:

* [Everything on Organizations](https://support.atlassian.com/jira-service-management-cloud/docs/group-customers-into-organizations/)
  * [Adding Users Manually](https://support.atlassian.com/jira-service-management-cloud/docs/add-a-customer-to-an-organization/)
  * [Adding users based on their email domain](https://community.atlassian.com/t5/Jira-Service-Management-articles/Managing-customers-and-organizations-on-Jira-Service-Management/ba-p/2677857#M4206)
    * [Original idea request](https://jira.atlassian.com/browse/JSDCLOUD-4519)
* [Issue sharing settings for customers](https://support.atlassian.com/jira-service-management-cloud/docs/change-project-customer-permissions/)

Note that you cannot restrict your Agents from sharing tickets to other organizations intentionally, without developing some automations to validate the organization added :)


author: Alex
body: Hi [@Rilwan Ahmed](/t5/user/viewprofilepage/user-id/716861)

Thank you, that looks perfect!

I'll add that to my reading list, and hopefully this should be enough to get everything set up as we need it.

Many thanks


author: Rilwan Ahmed
body: Hi [@Alex](/t5/user/viewprofilepage/user-id/5239945) ,

Make use of **[Issue Security scheme](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/)**. You can add reporter, single user and other roles/groups as required. This will add restrictions to other users from viewing the ticket.


author: Alex
body: Hi [@Jovin](/t5/user/viewprofilepage/user-id/5104734)

Thank you for getting back to me so quickly.

I'm reading those links you provided now, and it looks like exactly what we need.

When you mention agents sharing tickets to other organisations, I presume this is purely applicable to agents within our company? If so, we can manage this with working procedures.

Our main concern is making sure that if we have an organisation (say, Client Site A) that requests made by members of Client Site A can only be seen by the user who made the request, or by an admin user (a customer with additional permissions) associated with Client Site A.

The intention is that a senior staff member for each client site can view and manage requests made by their staff, but with the restriction that they cannot see any requests made from other client sites. I'm assuming that organisations are the most sensible way to achieve this, however I'm still researching.

comments: author: Jovin
body: Hey [@Alex](/t5/user/viewprofilepage/user-id/5239945)

Correct, by default in JSM customers can ONLY see their own requests. They can share to others (based on your sharing settings), as an example, you can make it so they can only share to users that have a profile (e.g. their peers that have logged in as well), and they can only share to organizations they are a member to.

By agents I mean your licensed users - they can add any organization to any ticket, which you can reverse/validate through automation rules.

[@Rilwan Ahmed](/t5/user/viewprofilepage/user-id/716861) 's comment is also very useful, but is a different mechanism that can also extend to the Agent view. e.g. if Agent A should only be able to see Client A tickets, you can do that.


Tags: cloud

jira-service-management

jira-service-management-cloud