How to Add a Person to a Jira Project: 5 Quick, Clear Steps
Need to add a teammate to Jira? This 5-step guide to jira add person to project helps you assign the right access. Read now.
Adding someone to a Jira project can take only a few clicks, but the wrong role can leave them unable to work—or give them more access than they need. That makes a simple invitation surprisingly easy to get wrong.
You might be wondering: why can a teammate see the project but not create an issue? Jira access can depend on project permissions, project roles, and whether the person has an account on your site. The steps also look a little different across Jira project types.
Here’s the quick route: open the project’s people or access settings, add the person, assign an appropriate role, and check that they can reach the work they need. I’ll walk you through each step, explain common access problems, and show you how to avoid granting unnecessary permissions.
How to Add a Person to a Jira Project in 5 Steps
Quick answer: Open the Jira project, go to its people or access settings, add the person, choose a suitable role, and confirm access. You may need site administrator permission to invite someone who does not have a Jira account yet.
- Open the project. Sign in to Jira and select the project you want the person to join. Check the project name before continuing, especially if you manage several projects with similar names.
- Find the people or access settings. Look for People in the project sidebar. If it is not there, open Project settings and look for People, Access, or a similar option. The menu can vary by Jira project type and site configuration.
- Choose the add-person option. Select the button or link for adding people. Enter the teammate’s name, username, or email address, depending on what Jira asks for.
- Assign a project role. Choose the role that matches the person’s responsibilities, such as viewer, contributor, or project administrator. Available role names and permissions depend on how your Jira site is set up.
- Confirm access. Submit the change, then ask the person to open the project. If they cannot see a board, issue, or project feature, check the project’s permissions and their assigned role.
But here’s the truth: adding a person to a project and giving them permission to perform every task are not always the same thing. Their role and your project’s permission settings determine what they can actually do.

Before You Invite Someone, Check These Details
First, confirm that the person has an account on your Jira site. If their name or email does not appear when you search, your site may require an administrator to invite them before you can add them to a project.
Next, check your own access. If you cannot see the project’s people or access controls, you may not have permission to manage membership. Ask a project administrator or Jira site administrator to make the change.
For example, a project lead may be able to assign existing Jira users to a project but may not be able to create new site accounts. An administrator can handle the invitation, after which the project lead can select the person and assign a role.
Choose a Role That Matches the Work
A project role determines which actions a person can take, subject to the project’s permission settings. A stakeholder who only needs progress updates may need less access than a developer who creates issues and updates sprints.
Here’s why: broad permissions can create avoidable risk, while limited permissions can slow down everyday work. Think through the tasks the person needs to complete, then select the least access that still lets them do those tasks.
- Viewer: Suitable when someone needs to follow progress or review project activity without making changes, if your site offers this role.
- Contributor or team member: Often suitable for people who need to work on issues, update tasks, or participate in project workflows.
- Project administrator: Usually reserved for people responsible for configuring project settings, managing access, or maintaining workflows.
Role labels are not universal. Check your Jira configuration before relying on a role name, and test the permissions with a suitable account if the project handles sensitive work.
What to Do When the Person Still Cannot Access the Project
If the person has been added but cannot open the project, confirm that they accepted any invitation and signed in to the correct Jira site. An account on a different site may not provide access to yours.
If they can open the project but cannot complete a task, check the relevant permission. For instance, someone may be able to view issues but lack permission to create them, transition them, or access a specific board.
Also check whether the project is company-managed or team-managed. Their access controls can differ, so an instruction that works in one project may not match the menus or permission model in another.
Let me explain: give the person one specific task to try, such as opening an issue or adding a comment. That makes it easier to identify whether the problem is project access, a missing permission, or a board-specific setting.
ONES.com Solution for Managing Project Access

Value Proposition
ONES.com brings project management and knowledge management together in one AI-powered platform, with ONES Project for project work and ONES Wiki for team knowledge. The two products are sold separately, so you can choose the capabilities that fit your team.
If your team is reviewing Jira alternatives, ONES Project supports structured project workflows while offering Jira-compatible workflows and deployment choices that include on-premise and air-gapped environments.
Core Capabilities
- Access is difficult to manage across project activity → ONES Project provides custom workflows and fields → teams can align project setup with their working practices.
- Teams rely on extra plugins for common project tasks → Built-in reporting supports project tracking → teams can reduce plugin dependence for routine reporting needs.
- Sprint work is hard to coordinate → Sprint management supports iterative planning → teams can organize and follow work within their project workflow.
- Repeated tasks consume team time → Automation can handle configured workflow actions → teams can reduce manual steps in recurring processes.
- Project work and team guidance are scattered → ONES Wiki provides a knowledge management option → teams can maintain guidance alongside their project management environment.
- Organizations have different hosting requirements → ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments → teams can select a deployment that suits their environment.
- Self-hosted teams worry about missing capabilities → The cloud and self-hosted versions have full feature parity → teams can choose deployment without giving up feature access.
- A team wants to try the platform before expanding → The free plan supports up to 30 seats → a small team can evaluate its project management needs.
Application Scenarios
Software team moving from Jira: A development team can evaluate ONES Project as a Jira alternative, configure workflows and fields, and use sprint management and built-in reporting. This can help the team map its existing project practices while reducing reliance on plugins for routine functions.
Organization with restricted hosting needs: A company that must keep project management within its own environment can consider On-Premise, Private Cloud, or Air-gapped deployment. The same feature parity across cloud and self-hosted versions helps teams assess hosting separately from feature availability.
Common Challenges When Adding Project Members
The Person Does Not Appear in Search
Problem: Jira cannot find the person’s name or email when you try to add them. Solution: Check that you have the right account details and ask a site administrator whether the person needs an invitation or account access first.
The Person Can View Work but Cannot Edit It
Problem: The teammate can open the project but cannot create or update issues. Solution: Review their project role and the permissions tied to the action they need. Ask an administrator to adjust access if you cannot change those settings.
The Project Menu Does Not Match the Instructions
Problem: You cannot find a People or Access option where you expect it. Solution: Check the project type and look under project settings. Menu names and locations can differ across Jira configurations.
The Person Can Open the Project but Not a Board
Problem: Project access works, but a board or particular issues remain unavailable. Solution: Check the board’s sharing and filter permissions, along with any issue security settings that limit visibility.
Frequently Asked Questions
Can I add someone to a Jira project without being an administrator?
Possibly. Some Jira project roles allow project members to add existing site users, while other sites reserve access changes for project or site administrators. If you cannot find the project’s People or Access controls, ask your project administrator to confirm your permissions. Inviting someone who does not yet have an account may require a site administrator even when you can add existing users.
Why can’t I find the person I want to add?
The person may not have an account on your Jira site, or you may be searching with an email address or name that does not match their account. Confirm their account details first. If they are new to the site, ask an administrator whether an invitation is required. Also check that you are using the correct Jira site if your organization has more than one.
What role should I give a new project member?
Choose a role according to the tasks the person needs to complete. A stakeholder who only follows progress may need viewing access, while a teammate updating issues may need a contributor role. Reserve project administration for people who manage project settings or membership. Jira role names and permissions can vary, so check the settings before assigning access.
Does adding someone to a Jira project give them access to every board?
Not necessarily. Project membership does not always grant access to every board, issue, or feature associated with that project. Board sharing, saved filter permissions, issue security, and project permissions can all affect what someone sees. If a teammate can open the project but cannot see a particular board, check those settings separately.
Conclusion
To add someone to a Jira project, open the project’s people or access settings, select the person, assign a suitable role, and verify that they can reach the work they need. If the person is missing or cannot complete a task, check account access, project permissions, and board settings.
A few careful checks can prevent both access delays and unnecessary permissions. Start with the teammate’s actual responsibilities, then adjust access only as needed. If your team is considering another project management setup, compare its workflow, deployment, and access controls with the way your projects operate.