Authorisation in a project

[Jens Prokoph]

Hello,
I am facing the challenge of creating a new project and the user authorisations for this are very strict.
Is it possible that all tickets end up with an employee, he then assigns them to employees and they can only and exclusively see these tickets? The second editors should not be allowed to see all tickets in the project.

Is there a variant for this?

[Wojciech Miecznikowski]

Hello Jens,
What you're looking for is called Issue Security (or Work Item Security) in Jira. This functionality allows you to control visibility on a per-issue basis within a project.
To achieve what you described, you'll need to:

1. Configure an Issue Security Scheme and associate it with your project.
2. Within the scheme, you can define one or more security levels.
3. Assign permissions to each level using fields like Assignee, Reporter, or even custom user fields.
4. Only users included in the specified fields (e.g., the Assignee) will be able to view the corresponding issue (if restriction, so this lock, applied to a work item).
This way, tickets can initially go to one person, and as they reassign them, visibility will be restricted to the assigned user only — as required.

You can find detailed documentation here:
- For Cloud: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/
- For DC: https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117

[Jens Prokoph]

Hi,
thanks for the help. I have now been able to configure many of them the way I want. Unfortunately there is now a central point where I don't know how to proceed. I would now like to assign this schema to a project.
Unfortunately, the specified option is not available in my project settings.

"Associate a permission scheme with a company-managed project
Once you have your project permission grants figured out, you can put the scheme into effect by associating it with the projects its meant to govern.

To associate a permission scheme with a company-managed project:

Choose Settings (), then select Projects.

Search for and select the project you want to change permissions for.

Next to your project's name in the sidebar, select More actions (---), then Project settings.

Select Permissions from the sidebar. This displays the current permissions scheme.

Click the Actions dropdown menu and choose Use a different scheme."

Here is a screenshot of my page;
Can you tell me how to assign this?

[Wojciech Miecznikowski]

Hello Jens,

It looks like Team-managed project, then situation is different. In Team-managed project you don't have schemes - configurations are seperated from each other and projects are simplified.

Unfortunately, in Team-managed (Service Management) project you don't have this optional configuration (because team-managed are simplified version). In this case I would recommend you to use Company-managed project (you have to craete new one).

[Jens Prokoph]

that means I can't simply change this project to an company-managed project?

[Wojciech Miecznikowski]

You are right - we don't have switch button to just change it, it is not such simple as it looks like. You have to create new project and if you want you can move work items work one project to another.