How to Add Someone to a Jira Project: 5 Simple Steps (2026)
Need to add someone to a Jira project? Follow the jira add person to project steps, assign the right role, and verify access. Read now.
Adding a teammate to a Jira project should take only a few minutes. Yet a missing permission, wrong project role, or lack of Jira access can leave someone unable to contribute.
That delay can hold up a review or sprint task while you troubleshoot settings. Here’s how to add someone to a Jira project in five steps, choose an appropriate role, and check that access works afterward. The instructions focus on Jira Cloud, where project menus can differ slightly between company-managed and team-managed projects.
Add Someone to a Jira Project in 5 Steps
In Jira Cloud, open the project, find its people or access settings, add the person, assign a role, and confirm they can open the project. You’ll usually need project administration permission, and the person may also need Jira product access.
Open the right project. Sign in to Jira and select the project where you want to add a teammate. Check the project name before changing access, especially if similar projects appear in the menu.
Open the project’s people or access settings. In many company-managed projects, select Project settings, then People. In team-managed projects, look for Project settings and an access, people, or members option.
Choose the add-person control. Select Add people, Add members, or a similarly named control. If you can’t find it, your project type or permission level may affect the menu.
Enter the person and select a role. Search for their Jira account by name or email address. Choose a role that fits their work, such as a project administrator, contributor, or viewer, if those options are available.
Save the change and check access. Confirm the addition, then ask the person to open the project. Have them try a relevant task, such as viewing an issue or adding a comment, to check their access.
But here’s the truth: adding someone to a project and granting access to Jira are related, but they aren’t always the same step. If Jira says the person lacks product access, an administrator may need to update that separately.

Check Access Before You Add a Teammate
Before inviting someone, confirm their Jira account and the access they need. A person who needs to review a board may not need permission to edit issues or manage project settings.
For example, a client reviewing a launch plan might need view access, while a developer working on sprint tasks needs permission to update issues. Granting the broadest role by default can expose settings or actions the person doesn’t need.
Confirm Your Permissions
If you don’t see a way to manage project members, ask a project administrator or Jira administrator for help. Your account may not have permission to change project access.
In company-managed projects, access can depend on project roles and permission settings. Team-managed projects often provide their own member controls, so the route may look different.
Choose a Project Role That Fits the Work
Pick a role based on the tasks the person will perform. The available role names and permissions depend on your project setup, so check what each role allows before assigning it.
A contributor who updates issues may need editing access. A stakeholder who only checks progress can often use a view-focused role, if one is available. Reserve project administration for people responsible for project settings.
Use a Simple Role Check
Reviewing progress: Choose a role with viewing permissions, when your project offers one.
Working on tasks: Select a role that permits the person to update relevant issues and participate in project work.
Managing project settings: Grant administration permissions only when the person needs to maintain project configuration.
Here’s why: a role that is too limited can block everyday work, while excessive access creates avoidable risk. Matching permissions to responsibilities makes access easier to review later.
Verify the Person Can Work in the Project
After you add the person, ask them to open the project using their own Jira account. Check that they can see the project and complete a task that matches their assigned role.
For instance, ask a new contributor to open an issue and add a comment. If they can view the project but can’t edit an issue, review their project role and the issue’s permission settings.
What to Check if Access Fails
Confirm that you added the correct account, selected the intended project, and chose a role with the required permissions. If Jira reports that product access is missing, contact an administrator who manages Jira access.
Some changes may take a short time to appear. If the person still can’t access the project, ask them to sign out and back in before investigating more complex permission settings.
Account for Company-Managed and Team-Managed Projects
Jira project menus vary by project type. Company-managed projects commonly use project roles and permission schemes, while team-managed projects handle more access choices within project settings.
That difference matters when a teammate can’t find the same People option shown in a guide. Check the project type and look for a member or access control in its settings rather than assuming the option is missing.
You might be wondering: what if the person is already part of your Jira site? They may still need access to this specific project, and project membership alone may not resolve a separate product-access restriction.
ONES.com Solution: Project and Knowledge Management
Value proposition: ONES.com brings project management and knowledge management together on one platform. Its products are sold separately, so you can choose ONES Project for project work and ONES Wiki for knowledge management.

If you’re comparing ways to organize project work, ONES Project is a Jira alternative with Jira-compatible workflows. It can suit teams looking to manage work with fewer add-ons or requiring a self-hosted deployment.
Core Capabilities
When teams need familiar project workflows, ONES Project supports Jira-compatible workflows. Teams can carry familiar ways of organizing work into the platform.
When reporting relies on extra plugins, built-in reporting provides project visibility within ONES Project. Teams can review progress without assembling reports through separate add-ons.
When standard processes don’t fit, custom workflows and fields let teams adapt project tracking. That can help capture details specific to a team’s work.
When teams plan work in iterations, sprint management supports sprint-based project activity. Teams can organize and follow work through their sprint process.
When routine actions take repeated effort, automation can handle selected workflow tasks. Teams can reduce manual steps in recurring project processes.
When project and knowledge work need different spaces, ONES Wiki provides a knowledge management product alongside ONES Project. Since they’re sold separately, teams can choose the product that suits their needs.
When deployment requirements vary, ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. The self-hosted version has full feature parity with the cloud version.
When a team wants to try the platform, the free plan supports 30 seats. A team can assess its project needs before deciding whether the platform fits its work.
Application Scenarios
A team moving from Jira can evaluate ONES Project against its existing workflow needs, including sprint planning, custom fields, and reporting. Jira compatibility can help the team assess whether its established process fits.
A company with strict hosting requirements can compare Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Full feature parity across cloud and self-hosted versions gives the team deployment flexibility without a stated feature split.
A team looking to keep project work and knowledge management within the same platform can consider ONES Project and ONES Wiki. Because the products are sold separately, it can select one or both based on its requirements.
Common Challenges When Adding a Jira Project Member
The Add-People Option Isn’t Visible
Problem: You open project settings but can’t find a control for adding people. Solution: Check whether the project is company-managed or team-managed, then ask a project administrator if your account can manage membership.
The Person Can’t Open Jira
Problem: You added someone to the project, but Jira still reports an access issue. Solution: Ask a Jira administrator to check whether the person has Jira product access, which may be managed separately from project membership.
The Person Can View but Not Edit
Problem: The teammate sees the project but can’t update issues. Solution: Review their role and the relevant project or issue permissions. Make sure the role supports the specific action they need.
The Wrong Person or Project Was Selected
Problem: A name or project looks similar to another one. Solution: Verify the account details and project name before saving. If you made a mistake, remove the incorrect access and add the intended person.
FAQs About Adding People to Jira Projects
Do I need administrator access to add someone to a Jira project?
You need permission to manage people or access for that project. The exact permission depends on your Jira configuration and project type. If you can’t find an add-person control, ask a project administrator or Jira administrator to check your permissions. Avoid sharing someone else’s account to work around access restrictions.
Why can someone access Jira but not my project?
Jira product access doesn’t necessarily grant access to every project. The person may need to be added to the specific project or assigned a project role with appropriate permissions. Check both their project membership and the role’s permissions. If access still fails, ask an administrator to review the project’s access settings.
Can I add someone using their email address?
In many Jira Cloud setups, you can search for a person by name or email when adding project members. The account must be available to your Jira site, and your permissions must allow you to add them. If the search returns no match, check the address or ask an administrator about account access.
What role should I give a new project member?
Choose a role based on the person’s responsibilities. Someone reviewing project progress may only need view permissions, while a teammate updating issues needs suitable editing access. Project administrators should be limited to people who manage settings. Role names and capabilities can differ, so check the options in your project before assigning one.
Conclusion
To add someone to a Jira project, open its member or access settings, select the person, assign an appropriate role, and verify that they can do their work. If access remains blocked, check project permissions and Jira product access separately.
That quick review can prevent delays and avoid giving someone more access than they need. Start with the project and task, then choose the right level of access for the teammate.