Jira Access: A Step-by-Step Guide to User Role Permissions
Unsure how to grant Jira access safely? Learn to check product access, groups, roles, and permissions—read now to assign the right access.
You need to give someone Jira access, but the right setting may depend on more than their project role. They might lack product access, belong to the wrong group, or need a specific permission before a project appears.
Granting broad access can expose sensitive work or let someone change settings they should not control. And if you adjust the wrong permission scheme, the fix may affect several projects at once.
But here's the truth: Jira access becomes easier to manage when you check it in layers. Start with the person’s account and product access, then review project roles, permissions, and any issue-level restrictions. This guide walks you through each step, explains what common roles can do, and shows how to troubleshoot access without granting more than someone needs.
How to grant Jira access and assign the right role
Use this sequence whenever you add someone to Jira or investigate a missing project. The order matters: project permissions cannot help someone who cannot access the Jira product at all.

1. Confirm the person has an account and Jira product access
Check that the person can sign in to your Atlassian site and has access to the relevant Jira product. An account alone may not include a Jira license or product entitlement.
For Jira Cloud, an organization or site administrator can review account and product access through the Atlassian administration area. Exact menu labels may vary. In a self-managed Jira environment, check the equivalent user and product access settings with your administrator.
For example, a colleague may have an Atlassian account but no Jira Software access. Adding them to a project role will not resolve that separate product-access gap.

2. Identify the project and access level they need
Ask what the person needs to do, not simply whether they need “access.” Someone who only needs to view and comment on issues usually requires fewer permissions than someone who manages a backlog or project settings.
Confirm the project name and whether it is company-managed or team-managed. Jira organizes roles and permissions differently across project types, so the right setting depends on that detail.
A developer may need to view issues, comment, and transition work. A project lead may also need to manage versions or edit project settings. Keep the requested tasks specific.
3. Add the person to the appropriate project role
Open the project’s settings and find its people, access, or project-role controls. Add the person directly or add a group that contains them, depending on your organization’s access practices.
Choose a role that matches their responsibilities. Common roles include administrator, developer, and viewer, although names and available roles can vary. A project role is a convenient way to group people; it does not automatically grant every permission by itself.
For instance, adding a contractor to a developer role can give them the project access associated with that role’s permission scheme. Avoid using an administrator role just to make a missing button appear.
4. Check the project’s permission scheme
Review which permissions the project role receives. A permission scheme connects actions, such as browsing projects or editing issues, with users, groups, or project roles.
Look for the exact action the person needs. If they can open an issue but cannot edit it, check the edit permission and the groups or roles assigned to it. If you change a scheme shared by multiple projects, consider the impact on every project using it.
Here's why: changing a role assignment may be safer than changing a shared permission scheme. A scheme change can alter access for many people across several projects.
5. Review issue-level security and special restrictions
A person may have permission to browse a project while still being unable to see particular issues. Jira issue security levels can restrict visibility within a project, even when the general project permissions look correct.
Check whether the missing issue uses a security level and whether the person, their group, or their project role is included. Also consider whether a board filter, workflow condition, or other project rule is affecting what they see or can do.
6. Ask the person to test the specific task
Have the person sign in and try the action they requested. Ask them to open a relevant issue, edit a field, add a comment, or transition an issue, depending on their role.
Testing the real task catches gaps that a role name alone cannot reveal. If access still fails, note the project, issue, and action involved. Then check product access, role membership, permissions, and issue security in that order.
Understand the layers behind Jira permissions
Jira access usually involves several connected layers: account access, product access, project roles, permission schemes, and sometimes issue security. A person needs the relevant access at each layer to complete a task.
Think of it like entering an office building. Product access gets someone through the front door, a project role gives them access to a work area, and issue security can restrict a specific room. A missing permission at any point can block the task.
For example, an employee may be able to sign in and open Jira but still lack access to a particular project. Another person may browse that project but be blocked from a confidential issue. Checking one layer at a time makes the cause easier to find.
Choose roles by responsibility, not job title
Role names can make permissions seem simple, but the permission scheme determines what each role can actually do. Review the actions attached to a role before assigning it, especially when projects contain sensitive work.
A developer role might allow someone to browse issues, add comments, and update work. A viewer role may suit a stakeholder who needs to follow progress without changing issues. An administrator role can permit project configuration, so reserve it for people who need that responsibility.
You might be wondering: should you add a person directly or use a group? Direct assignment can work for a small, temporary need. Groups are often easier to maintain when several people share the same access requirements or when team membership changes regularly.
Troubleshoot a missing project or blocked action
Start by asking what the person can and cannot do. “I can’t access Jira” is less useful than “I can open Jira, but the project does not appear” or “I can see the issue, but I cannot edit it.”
If the project is missing, verify product access, project membership, and the permission to browse that project. If only one issue is missing, investigate its security level. If a button or action is unavailable, inspect the matching permission and any workflow conditions.
For example, someone who can view a backlog but cannot move an issue may have browsing permission without the required transition permission. Checking that specific action is more effective than making them a project administrator.
Keep access useful and secure over time
Access decisions should reflect current responsibilities. When a person changes teams or finishes a contract, review their project membership and remove access they no longer need.
Set a routine for checking project roles, group membership, and administrator assignments. A short review after a team change can prevent old permissions from lingering. For sensitive projects, agree on who approves access and how long temporary access should last.
The best part? You do not need to redesign every permission scheme to improve access. Clear role definitions, careful group membership, and a simple review habit can resolve many recurring problems.
Jira Access Management Solution: ONES.com

Value proposition
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. If your team is reviewing how it manages project work beyond Jira, ONES Project is a Jira alternative with Jira-compatible workflows and deployment options that include self-hosting.
Core capabilities
- Pain: Teams want to keep familiar Jira-style processes. ONES capability: ONES Project supports Jira-compatible workflows. Result: Teams can evaluate a transition without rebuilding every process from scratch.
- Pain: Projects need different fields and stages. ONES capability: Custom workflows and fields let teams shape how work is tracked. Result: Project details can reflect the team’s actual process.
- Pain: Teams need to plan and track sprints. ONES capability: Sprint management supports agile project work. Result: Teams can organize planned work and monitor progress in the same project environment.
- Pain: Repeated manual actions take time. ONES capability: Automation supports routine project operations. Result: Teams can reduce repetitive steps in their workflows.
- Pain: Project leads need visibility into work progress. ONES capability: Built-in reporting gives teams reporting options within the platform. Result: Leads can review project activity without relying on a separate reporting add-on for every need.
- Pain: Teams want project work and knowledge management under one platform. ONES capability: ONES.com brings together project management and knowledge management. Result: Teams can consider a connected platform approach. ONES Project and ONES Wiki are sold separately.
- Pain: Some organizations cannot use a cloud-only deployment. ONES capability: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can assess an environment that fits their hosting and network requirements.
- Pain: Self-hosted teams worry that deployment choice will limit functionality. ONES capability: The cloud and self-hosted versions have full feature parity. Result: Teams can assess self-hosting without planning around a reduced feature set.
- Pain: Teams want to test a platform before expanding access. ONES capability: The free plan supports up to 30 seats. Result: A smaller team can evaluate its fit before considering a broader rollout.
Application scenarios
A regulated team reviewing hosting options: A team with strict network requirements can assess ONES.com’s On-Premise, Private Cloud, or Air-gapped deployment. The team can also compare its Jira-compatible workflows with existing project practices.
A growing product group reducing add-on dependence: A team using several plugins for common project needs can evaluate ONES Project’s built-in reporting, custom workflows and fields, sprint management, and automation. This can help the team assess whether fewer plugins meet its requirements.
A team connecting project work with internal knowledge: A group that wants project management and knowledge management within one platform can review ONES.com. It should account for ONES Project and ONES Wiki being sold separately when planning its setup.
Common challenges when managing project access
- Problem: Someone has an account but cannot open Jira. Check whether the person has product access, not just an account. Then verify that they can sign in to the correct site or environment.
- Problem: A project disappears for one person. Check project membership, the browse-project permission, and any relevant group assignments. Confirm that the person is looking at the correct Jira site.
- Problem: A person can see issues but cannot edit them. Review the edit permission and the role or group connected to it. Check workflow conditions if the restriction applies only to a particular status.
- Problem: One issue remains hidden. Inspect its issue security level and confirm whether the person’s role or group is included. Project access does not necessarily grant visibility into every issue.
- Problem: A permission change affects other teams. Find out whether the project shares its permission scheme with other projects. Prefer a targeted role or group adjustment when it meets the need without changing access elsewhere.
Frequently asked questions
What is the difference between Jira product access and project access?
Product access allows someone to use a Jira product on your site. Project access determines what they can see or do within a particular project. A person may have an account and Jira access but still lack permission to browse a project. Check both layers before changing a project role, because a role cannot replace missing product access.
Does adding someone to a Jira project role give them every project permission?
No. A project role groups people for permission management, but the project’s permission scheme determines which actions that role receives. Review the scheme to see whether it grants browsing, editing, commenting, or other permissions. Also check for issue security or workflow rules that may restrict access to particular issues or actions.
Why can someone see a project but not a specific issue?
Issue security may restrict visibility for selected issues, even when someone can browse the project. Check the issue’s security level and whether the person, their group, or their project role is allowed to see it. If the issue is visible but a particular action is unavailable, investigate the relevant permission and workflow conditions instead.
Should I assign Jira access to individuals or groups?
Use the approach that fits your team’s maintenance needs. Individual assignments can suit one-off or short-term access. Groups can be easier to manage when several people need the same permissions or team membership changes regularly. Whichever approach you choose, check the resulting permissions and remove access when it is no longer needed.
What should I check first when Jira access is not working?
Clarify the exact problem first: can the person sign in, open Jira, find the project, view an issue, or perform a specific action? Then check product access, project membership, the permission scheme, issue security, and workflow restrictions in that order. Testing the requested task after each change helps identify the setting that actually resolves the issue.
Conclusion
Effective Jira access starts with the task someone needs to complete. Confirm their account and product access, assign a suitable project role, review the permission scheme, and check issue-level restrictions when visibility differs.
When access problems persist, narrow them down by asking what the person can do and where the block occurs. That simple approach can help you fix the actual permission gap while avoiding unnecessary access.
But here's the truth: a clear access routine protects project work and makes day-to-day collaboration smoother. Review roles as responsibilities change, keep administrator access limited, and test important permission changes with the person who requested them.