How to Add a User in Jira: A Step-by-Step Admin Guide 2026
Need to add a user in Jira without access issues? This admin guide covers invites, product access, and project permissions. Read now.
To add a user in Jira, invite them through your Atlassian organization or create an account in Jira Data Center, then grant product access and project permissions. The exact steps depend on your Jira edition and your admin role.
It’s easy to miss a permission along the way. Someone may accept an invitation but still be unable to open a project, or you may assign paid product access when they only need limited access. But here’s the truth: adding an account and giving someone useful, appropriate access are separate tasks.
This guide walks you through both. You’ll learn how to invite people in Jira Cloud, create accounts in Data Center, set project access, and troubleshoot common problems without granting more access than a person needs.
How to add a user in Jira
Start by identifying your Jira edition and checking that you have the right administrative permission. Then create or invite the account, assign the necessary product access, and confirm the person’s project permissions.
Jira Cloud: Invite a user
Sign in to your Atlassian organization administration area. You may need an organization admin or user access admin role to manage accounts.
Open Directory, then select Users. Choose the option to invite users. Labels and navigation can vary slightly as Atlassian updates its interface.
Enter the person’s work email address. If you’re inviting several people, follow the invitation screen’s instructions for adding multiple email addresses.
Select the products the person needs, such as Jira. Check the product access carefully because granting access can use a paid seat on your plan.
Choose any appropriate groups offered during setup, then send the invitation. Group access can affect which products and permissions the person receives.
Ask the person to open the invitation and finish signing in. Afterward, check that they can reach the right Jira site and project.
Here’s why the last check matters: accepting an invitation does not necessarily grant access to every project. You may still need to add the person to a project role or a group that has the relevant project permissions.
Jira Data Center: Create an account
Sign in with an account that has the required Jira administrator permissions.
Open the administration area and go to User management. The exact path depends on your Jira Data Center version and configuration.
Select the option to create a user. Enter the account details requested by your Jira setup, such as a username, email address, and display name.
Set or send initial sign-in details using your organization’s security process. If Jira connects to an external identity provider, account creation may be managed there instead.
Assign the user to the appropriate groups. Review each group’s product access and permissions before saving.
Confirm the person can sign in, open Jira, and access the intended project. Adjust project roles or permissions if needed.
Let me explain: Data Center installations can use different identity and directory configurations. If the account creation controls are unavailable, check with the administrator who manages your organization’s identity setup.
Give the user access to a project
Once the account has Jira product access, check how the project controls membership. Depending on the project type, you might add the person directly to a project role, add them to a group already assigned to that role, or update the project’s access settings.
For example, a new developer may need the project’s developer role to view issues and contribute to sprints. A contractor who only needs to follow progress may need a more limited role. Choose the smallest permission set that lets each person do their work.
If a user can sign in but cannot see a project, review the project’s access settings and permission scheme. Also check whether the person has the required group membership or project role.
Before you send an invitation
A quick access check can prevent both delays and unnecessary permissions. Before inviting someone, confirm who owns account administration, which Jira product they need, and what work they must do.
Confirm the Jira edition: Cloud invitations and Data Center account creation follow different administration paths.
Check your admin role: You may be able to manage a project without being allowed to invite organization-wide users.
Choose product access deliberately: The person may need Jira access, but not every Atlassian product available to your organization.
Plan project permissions: Decide whether a project role or group should control the person’s access.
Review seat impact: Product access can affect billing, depending on your plan and product.
The best part? A short checklist makes repeat invitations much easier. For example, a team lead can specify the project, role, and product access before an administrator sends an invitation.
Understand accounts, product access, and project permissions
These three access layers are related, but they do different jobs. Knowing which layer is missing makes troubleshooting faster.
Account: Lets a person sign in to the relevant Atlassian organization or Jira instance.
Product access: Lets the person use Jira or another product on the site. It can affect the organization’s subscription.
Project permissions: Determine what the person can see and do inside a particular project, such as viewing issues or managing settings.
Consider a new designer invited to Jira Cloud. Their account may be active, and Jira product access may be granted, yet the project can remain invisible until an administrator adds them to an authorized project role or group.
Keep those layers separate when investigating access. If the user cannot sign in, check the account and invitation. If they can sign in but cannot open Jira, check product access. If Jira opens but a project is missing, inspect project permissions.
How to manage access safely as your team grows
Access decisions become harder when several teams share projects. A clear process helps you avoid one-off permissions that are difficult to review later.
Use groups for repeatable access
If five engineers need the same access, assigning them through an established group can be easier to maintain than handling each permission separately. Check what that group can access before adding anyone, since group membership may grant more than project access.
Give people only the access they need
A person responsible for reporting may not need the same permissions as a project administrator. Start with the role that fits their tasks, then expand access only when a specific work requirement calls for it.
Review access when responsibilities change
People move between teams, finish contracts, or take on different responsibilities. Review group membership and project roles during those changes, and remove access that is no longer needed.
Document your internal handoff
Keep a clear internal record of who approves access, who sends invitations, and who checks project membership. That way, a team lead can request the right permissions without guessing which administrator to contact.
A related project management option: ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.
If you’re reviewing how project teams manage work and access, ONES Project may be worth evaluating alongside your existing setup. It offers Cloud, On-Premise, Private Cloud, and Air-gapped deployment options, with feature parity between its cloud and self-hosted versions. The free plan supports up to 30 seats.
Core capabilities
Pain: Teams need to bring Jira-style ways of working with them. ONES capability: Jira-compatible workflows. Result: Teams can preserve familiar processes during evaluation or transition.
Pain: Different teams need different approval paths. ONES capability: Custom workflows. Result: Work can follow steps suited to each team’s process.
Pain: Standard fields do not capture a team’s needs. ONES capability: Custom fields. Result: Teams can track the details relevant to their work.
Pain: Agile teams need sprint planning and tracking. ONES capability: Sprint management. Result: Teams can plan and follow sprint work in the project management product.
Pain: Repetitive actions consume time. ONES capability: Automation. Result: Teams can reduce manual steps in recurring workflows.
Pain: Project leads need to monitor progress. ONES capability: Built-in reporting. Result: Teams can review project activity without relying on extra reporting plugins.
Pain: Organizations need deployment flexibility. ONES capability: Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can choose an environment that fits their operational requirements.
Pain: Self-hosted teams want capabilities comparable to cloud teams. ONES capability: Full feature parity between cloud and self-hosted versions. Result: Deployment choice does not require giving up feature availability.
Application scenarios
A project team reducing plugin dependence: A team that relies on multiple plugins for workflows and reporting can evaluate ONES Project’s built-in workflows, custom fields, automation, and reporting as part of a broader tool review.
An organization with restricted network requirements: A team that cannot use a public cloud environment can assess the Air-gapped or other self-hosted deployment options while reviewing how project work should be managed.
Common challenges when adding Jira users
The invitation never arrives
Problem: The person cannot find the invitation email. Solution: Confirm the email address is correct, ask them to check spam or quarantine folders, and review the user’s invitation status in administration. Resend the invitation if the interface allows it.
The user can sign in but cannot open Jira
Problem: The account exists, but the person lacks product access. Solution: Review their product access and confirm that the correct Jira site or instance is selected. Check whether the organization requires an additional approval step.
The user has Jira but cannot see a project
Problem: Product access is present, but the project is missing or its issues are inaccessible. Solution: Check project roles, group membership, project access settings, and the relevant permission scheme.
You cannot invite or create an account
Problem: The invitation or account creation control is missing. Solution: Ask an organization or Jira administrator to confirm your role. In Data Center, check whether account management is handled through an external identity provider.
You are unsure whether access will add a seat
Problem: You do not know how a new product assignment affects your plan. Solution: Review the subscription and product access details before confirming the assignment. If billing is managed centrally, check with the subscription administrator first.
FAQs
Can I add someone to a Jira project without giving them Jira access?
Generally, a person needs access to the Jira product or instance before they can use a Jira project. Project membership controls what they can do after they can reach Jira; it does not usually replace product access. Check your organization’s product settings and the project’s access configuration, especially if your plan or deployment includes special access rules.
What permissions do I need to add a user in Jira?
Your permissions depend on the Jira edition and the organization’s administration setup. In Cloud, inviting users may require an organization admin or user access admin role. In Data Center, creating accounts typically requires Jira administration permissions unless an external identity provider manages accounts. If you cannot see user management controls, ask your administrator to confirm your role.
Why can a newly invited user sign in but not see a project?
Signing in confirms that the account works, but it does not guarantee project membership. The user may still need Jira product access, a project role, or membership in a group that grants project permissions. Check the project’s access settings and permission scheme, then confirm the user has the role needed for their tasks.
Does inviting a user to Jira always increase the bill?
Not necessarily. The effect depends on your product, plan, subscription, and whether the new account receives paid product access. Before assigning access, review your current subscription details and seat usage. Some forms of limited access may have different billing treatment, so avoid assuming every invitation has the same cost.
Can I add several people at once?
Jira Cloud’s invitation flow may allow you to invite multiple people, depending on the interface and your permissions. For Data Center, options can vary by version and identity configuration. When adding a group, confirm that everyone needs the same product and project access before applying shared permissions.
Conclusion
Adding a Jira user involves more than sending an invitation. You need to create or activate the account, grant the right product access, and confirm the person can reach the correct project.
When access gets tangled, identify which layer is missing before changing permissions. That simple check can save time and help prevent over-permissioning. If your team is reassessing project workflows as well, compare your current setup with options such as ONES Project and choose an approach that fits your deployment and team needs.