How to Create a Group in Jira: Step-by-Step Guide (2026)
Need to manage Jira access? Learn the jira create group steps, add members, and set permissions correctly. Read now to avoid common mistakes.
Creating a Jira group helps you assign product access and permissions to people with similar responsibilities. You can create one in Atlassian Administration for Jira Cloud or in Jira’s user management settings for Data Center.
But here's the truth: creating the group is only the first step. If you skip access settings or project permissions, members may still be unable to reach the work they need—or may receive broader access than intended.
Here’s how to create a group, add people, and connect it to the right Jira permissions. I’ll also explain the common setup mistakes that can cause confusion later, so you can build a group that is useful, secure, and easy to manage.
How to Create a Group in Jira
Start by choosing the instructions for your Jira deployment. Jira Cloud group management takes place in Atlassian Administration; Jira Data Center group management is handled through Jira’s user management area.

Jira Cloud: Create a Group in Atlassian Administration
Sign in to admin.atlassian.com with an account that has organization or user management permissions.
Select your organization, then open Directory and choose Groups. The exact labels may vary slightly as Atlassian updates its interface.
Select Create group, enter a clear group name, and add a short description if the option is available.
Choose Create to save the group. Search for the group afterward to confirm that it appears in the directory.
Open the group and add the intended members. You can often add people by searching their names or email addresses.
Review the group’s product access and project permissions. Creating a group alone does not automatically grant access to every Jira project.
For example, you might create marketing-jira-contributors for campaign coordinators. Add only the people who need that access, then grant the group the relevant Jira product and project permissions.
Jira Data Center: Create a Group in User Management
Sign in to Jira with an administrator account.
Open Jira administration, then navigate to User management and Groups.
Select Add group, enter the group name, and confirm the creation.
Find the new group in the group list and add the required users.
Assign the group to the appropriate global permissions, project roles, or permission scheme entries.
On a Data Center installation, menu names can differ by Jira version and configuration. If you cannot see user management controls, ask a Jira administrator to check your account permissions.
What a Jira Group Can—and Cannot—Do
A Jira group is a named collection of accounts. Administrators use groups to manage access and permissions for several people together rather than configuring each person separately.
Here’s why: groups make recurring changes easier. If a new team member joins a project, adding them to the right group can be simpler than granting several permissions one by one.
However, a group is not the same thing as a project role. A group can be assigned to a project role or permission scheme, but creating the group does not automatically give its members access to a project.
Think of the Group as a Membership List
Imagine a project role called Developers and a group called platform-engineers. An administrator can add that group to the Developers role, then grant the role permission to browse the project.
That setup has two parts: people belong to the group, and the group receives access through a project role or permission scheme. If either connection is missing, members may not see the project or perform the expected actions.
Plan the Group Before You Add Members
A little planning prevents an untidy directory. Before creating a group, decide who belongs in it, what access they need, and who will maintain its membership.
Choose a clear name. Use a team, function, or access purpose, such as finance-project-viewers.
Keep membership focused. Avoid combining people with different access needs just because they work in the same department.
Use a consistent naming pattern. A shared convention helps administrators distinguish groups for product access, project roles, and general team membership.
Identify an owner. Decide who approves membership changes and checks that access remains appropriate.
For instance, a company might separate product-planning-editors from product-planning-viewers. That distinction is easier to understand than a broad group that includes everyone in product.
Grant the Right Jira Access
After creating the group, connect it to the access the members actually need. In Jira Cloud, check both product access and project-level permissions; in Data Center, review the relevant global and project permissions.
Let me explain: product access determines whether someone can use Jira, while project permissions control what they can do within a particular project. A person may have a Jira account but still lack permission to browse a specific project.
Check Product Access and Project Permissions
Confirm the group’s members can access the Jira product when required.
Review the project’s permission scheme or role assignments.
Check whether the group has only the permissions needed for its work.
Test access with a representative account, especially when the project contains restricted work.
For example, a group of external reviewers may need permission to view issues but not to edit them. Assigning a broad contributor role could give them more access than the review task requires.
Verify the Group and Maintain It
Once you add members and assign permissions, verify the result instead of assuming the setup worked. Ask a group member to sign in and confirm that the expected project and actions are available.
The best part? A short review can catch both access gaps and accidental over-permissioning. If someone cannot see the project, check product access, group membership, role assignment, and the project’s permission scheme in that order.
Make Group Reviews Routine
Review group membership when teams change, projects close, or responsibilities shift. Remove people who no longer need access and update permissions when the group’s purpose changes.
A simple quarterly check works well for many teams. For a group with access to sensitive projects, review membership more frequently and record who is responsible for approving changes.
ONES.com Solution for Teams Organizing Project Work
Value proposition: ONES.com brings project management and knowledge management together, while ONES Project provides project workflows for teams looking for a Jira alternative. ONES Project and ONES Wiki are sold separately.

Creating a Jira group is one way to organize access, but teams also need clear workflows, dependable reporting, and shared project knowledge. ONES.com offers an alternative approach for teams that want project management capabilities with deployment choices that can fit different operating environments.
Core Capabilities
Scattered project tracking → ONES Project’s project management workspace → teams can manage tasks and project activity in one structured environment.
Different teams need different processes → Custom workflows and fields → teams can shape issue details and workflow stages around their work.
Unclear sprint progress → Sprint management and built-in reporting → teams can review sprint activity and project progress without assembling separate reporting processes.
Repeated manual handoffs → Automation → teams can reduce routine steps and make common workflow transitions more consistent.
Existing Jira habits → Jira-compatible workflows → teams can use familiar workflow concepts while evaluating a Jira alternative.
Too many separate add-ons → Native project management capabilities → teams may be able to reduce reliance on plugins for common needs.
Restrictions on hosting → Cloud, On-Premise, Private Cloud, or Air-gapped deployments → organizations can choose an environment that fits their operational requirements.
Concerns about self-hosted capability gaps → Full feature parity between cloud and self-hosted versions → teams can consider deployment needs without giving up feature availability.
Project work disconnected from team knowledge → ONES.com’s project and knowledge management offerings → teams can choose ONES Project and ONES Wiki for their respective needs, with each product sold separately.
Application Scenarios
Growing product team: A product group can use ONES Project to manage backlogs, sprints, custom fields, and reporting. That gives project leads a defined workflow without relying on a collection of separate plugins for routine project needs.
Restricted deployment environment: An organization with strict hosting requirements can evaluate On-Premise, Private Cloud, or Air-gapped deployment. Its team can assess the deployment fit while retaining feature parity with the cloud version.
Team combining project work and knowledge management: A company can use ONES Project for project management and select ONES Wiki separately for knowledge management. This can help teams keep project coordination and shared team knowledge within the ONES.com offering.
Common Challenges When Setting Up Jira Groups
Members cannot access the intended project. Check product access, group membership, project role assignments, and the permission scheme. A group’s existence alone does not provide project access.
Members receive too much access. Review the group’s roles and permissions. Split a broad group into focused groups, such as viewers and editors, when responsibilities differ.
Administrators cannot find group controls. Confirm that the account has the required organization or Jira administration permissions. Cloud and Data Center expose group management in different places.
Group names become confusing. Adopt a naming convention and use a short description when available. For example, a prefix such as project- can help distinguish project-specific groups.
Membership becomes outdated. Assign an owner and review the group on a regular schedule. Remove people when their responsibilities change or they no longer need access.
Frequently Asked Questions
Who can create a group in Jira?
In Jira Cloud, you generally need suitable organization or user management permissions to create and manage groups through Atlassian Administration. In Jira Data Center, you need Jira administration permissions that include user management. If the group controls access to a sensitive project, follow your organization’s approval process before adding members or changing permissions.
Does creating a Jira group automatically give members access to a project?
No. Creating the group provides a place to manage membership, but you still need to connect it to the relevant product access and project permissions. Depending on your setup, that may mean assigning the group to a project role or permission scheme. Check access with a representative member after configuring those settings.
Can I add an existing Jira user to a group?
Yes. Open the group in the relevant administration area and add the person to its membership. In Jira Cloud, group management is generally handled in Atlassian Administration. In Data Center, use Jira’s user management settings. The person may still need product access or project permissions before they can work in a particular project.
What is the difference between a Jira group and a project role?
A group is a collection of accounts that administrators can manage together. A project role is a project-level way to define responsibilities, such as Developers or Administrators. You can assign a group to a project role, then use the project’s permission scheme to determine what that role can do. They work together, but they serve different purposes.
Can I create groups for different levels of project access?
Yes. You can create separate groups for different responsibilities, such as viewers, contributors, and project administrators. Assign each group only the permissions its members need. For example, reviewers may need to browse issues, while contributors may need permission to edit them. Clear separation makes access reviews easier and can reduce accidental over-permissioning.
Conclusion
To create a Jira group, use Atlassian Administration for Jira Cloud or Jira’s user management settings for Data Center. Add the intended people, then assign the group the product access and project permissions they need.
But here's the truth: a group that is never connected to the right permissions may not solve the access problem. Choose a clear purpose, test the setup, and review membership as responsibilities change.
When your team is also evaluating how it manages project workflows, reporting, and shared knowledge, ONES.com offers another path to consider. Start with the access needs you have today, then choose a setup your team can maintain over time.