Creating Groups in Jira: A Step-by-Step Admin Guide [2026]
Need safer Jira access? Learn creating groups in Jira for Cloud and Data Center, verify permissions, and manage members confidently. Read now.
Creating a Jira group can make access easier to manage, but one careless membership change may expose projects or interrupt someone’s work. The confusing part is that Jira Cloud and Jira Data Center handle group administration differently, and a Jira admin may not have the organization permissions needed to create groups.
Here’s the truth: a group does not automatically grant every permission. Its access depends on the product access settings and project permissions connected to it. Follow the steps for your Jira environment, check what the group can reach, and add members only after you understand the impact. This guide walks you through the process, explains common access issues, and shows how to keep group membership manageable.
How to Create a Group in Jira
First, identify whether you use Jira Cloud or Jira Data Center. Then create the group in the appropriate administration area, confirm its permissions, and add members.

Step 1: Confirm Your Jira Environment and Admin Access
In Jira Cloud, group management is generally handled through Atlassian organization administration. You may need organization administrator privileges to create or manage groups. A Jira administrator role by itself may not be enough.
In Jira Data Center, group management is usually available through Jira administration. If your organization connects Jira to an external directory, such as LDAP, group creation and membership may need to happen in that directory instead.
Step 2: Open Group Management
For Jira Cloud, sign in to your Atlassian organization administration area and open the user management or directory section. Select Groups to view existing groups and group controls. The exact labels can vary as Atlassian updates its interface.
For Jira Data Center, open Jira administration, then go to User management and select Groups. If you cannot see the group controls, ask an administrator to check your role and directory configuration.
Step 3: Create the Group
Select the option to create a group. Choose a clear, specific name, such as project-orion-readers or support-team-agents. A name that describes the team or access purpose is easier to understand than a broad label like team1.
Before confirming, check for an existing group with a similar name. Duplicate or ambiguous names can lead to mistakes when administrators assign access later.
Step 4: Review Product and Project Access
Creating a group does not necessarily give its members access to Jira or any particular project. In Cloud, check whether the group is connected to product access. In either environment, review project permissions and any global permissions that refer to the group.
For example, adding a group to a project’s browse permission may let its members view that project. Adding it to a broader administrative permission could give members much more access than intended.
Step 5: Add Members and Test Access
Add the intended people to the group, then verify their access with a test account or a carefully chosen member. Check both what the person can do and what they should not be able to do.
But here’s the truth: group access can overlap. Someone may get permission through another group, so removing them from one group might not remove their project access. Test the full permission path before treating a change as complete.
- Confirm the Jira environment and your admin role.
- Open the correct group management page.
- Create a clearly named group.
- Review product access, global permissions, and project permissions.
- Add members and verify the resulting access.
How Jira Groups Affect Access
A Jira group is a named collection of accounts that administrators can use to manage access. Instead of granting the same permission to each person individually, an administrator can connect a group to product access or a permission setting.
Here’s why that matters: when a team changes, you can update group membership rather than editing many project settings. However, group membership only has an effect where Jira or its connected services use that group.
Groups, Product Access, and Project Permissions
Think of a group as a key ring. The group itself does not open a door; the permissions connected to it determine which doors its members can open. Product access, global permissions, and project permissions may each use groups in different ways.
For example, a person may be in a group that grants Jira access and another group that grants permission to browse a specific project. If you remove the person from the project group but leave the broader permission in place, they may still retain access.
Common Group Uses
Organizations often use groups for project roles, department access, or recurring responsibilities. Examples include a group for product managers who need to edit project settings and another for stakeholders who only need to view work.
Keep group membership aligned with actual job duties. A tightly scoped group is easier to review than one that mixes administrators, contractors, and occasional viewers.
Cloud and Data Center: Important Differences
Jira Cloud group administration sits within Atlassian’s organization and user management experience. Depending on your setup, organization administrators may control group creation, while Jira administrators manage project-level configuration.
In Jira Data Center, the Jira administration interface may provide group controls, but an external directory can change who is allowed to manage groups. If a group comes from an external directory, attempting to change it in Jira may not work as expected.
Check Where the Group Is Managed
If a group appears in Jira but its membership controls are unavailable, check whether it is synchronized from an external directory. Ask the directory administrator where the group should be maintained before creating a second group with a similar name.
For example, a company may manage employee groups centrally and synchronize them to Jira Data Center. Creating a local Jira group for the same team could split membership between two places.
Verify the Current Interface
Administration menus can change between product versions and organization configurations. If a step does not match your screen, search the administration area for group management and confirm your role before changing permissions.
Let me explain: the key task is not finding one exact menu label. It is confirming that you are editing the intended group in the system that controls its membership.
Plan Group Names and Membership Beforehand
A useful naming pattern tells administrators who belongs in a group and what the group enables. Names such as finance-project-viewers or mobile-release-managers are easier to assess than labels that reveal little about their purpose.
Keep membership focused. If five people need to manage a project and twenty people only need to view it, separate those responsibilities into distinct groups with different permissions.
Set an Owner and Review Schedule
Assign a responsible owner for groups that control sensitive or important access. The owner can confirm whether members still need access when teams or responsibilities change.
A quarterly review can catch stale memberships. For example, an administrator might compare each group’s purpose with its current members and remove people whose project role has ended.
Document the Access Purpose Clearly
Record what a group is for, who owns it, and which permissions refer to it. This helps another administrator understand why a group exists before changing or deleting it.
You might be wondering: does every group need a long description? No. A brief, specific purpose and a named owner are often enough to prevent confusion.
Manage Group Changes Safely
Group changes can affect many projects at once. Before adding or removing a group from a permission setting, identify the people affected and the access they will gain or lose.
The best part? A simple change process can reduce surprises. Test access with a small, representative group first when the change affects a sensitive project or a large team.
Use a Change Checklist
- Confirm the group name and its intended purpose.
- Check which product, global, and project permissions use the group.
- Identify overlapping access that may remain through other groups.
- Notify affected team members when the change could interrupt their work.
- Verify the result after making the change.
Be Careful When Removing or Renaming a Group
Removing a group or changing its name can affect every permission that refers to it. Before deleting a group, check whether it is still connected to project permissions, product access, or administrative settings.
If a group is no longer needed, remove its permission assignments first, confirm that no active work depends on it, and follow your organization’s access review process. Avoid deleting a group just because its original owner has left.
Creating and Managing Groups with ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project provides project management as a Jira alternative, while ONES Wiki provides a knowledge base as a Confluence alternative; they are sold separately.

For teams reviewing how they organize project work and access, ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Its self-hosted versions have feature parity with the cloud version, which can help teams that need deployment choice alongside consistent capabilities.
Core Capabilities
- Disconnected project and knowledge work: Teams may keep project tracking and team knowledge in separate systems. ONES.com brings project management and knowledge management into a unified platform, while ONES Project and ONES Wiki remain separately sold products.
- Migration concerns for Jira workflows: Rebuilding familiar processes can slow adoption. ONES Project supports Jira-compatible workflows, helping teams preserve familiar ways of managing work.
- Limited visibility into progress: Teams may need to assemble status updates across projects. Built-in reporting gives teams a way to review progress within their project management environment.
- Rigid process requirements: A standard workflow may not match every team’s approval path. Custom workflows and fields let teams represent project-specific steps and information.
- Sprint planning needs: Agile teams need to plan and track sprint work. ONES Project includes sprint management for organizing that work.
- Repeated manual tasks: Administrators and project teams may spend time on recurring process steps. Automation can handle configured actions and reduce repetitive work.
- Deployment constraints: Some organizations need a self-hosted or restricted-network deployment. ONES.com offers On-Premise, Private Cloud, and Air-gapped options alongside Cloud.
- Seat limits during evaluation: A team may want to try project management before committing to a larger rollout. The free plan supports up to 30 seats.
Application Scenarios
A software team moving Jira workflows can assess ONES Project’s Jira-compatible workflows, custom fields, sprint management, and reporting. It can map a small project first, then compare the resulting workflow with the team’s current process.
An organization with restricted network requirements can evaluate the Air-gapped or On-Premise deployment options. This gives administrators a way to assess project management within the deployment conditions their organization requires.
A team that also needs shared knowledge can consider ONES Wiki separately from ONES Project. Keeping the product choice aligned with the team’s actual needs helps avoid adopting capabilities it does not plan to use.
Common Challenges When Creating Jira Groups
You Cannot Find the Group Management Controls
Problem: Your Jira role may not include organization-level group administration, or your Data Center groups may be managed externally.
Solution: Confirm your environment and ask the appropriate organization or directory administrator to check your permissions.
The Group Exists, but Members Cannot Open a Project
Problem: The group may not be connected to product access or the project’s relevant permissions.
Solution: Review product access and project permissions separately. Then test with a member account to confirm the expected access.
Removing a Member Does Not Remove Their Access
Problem: Another group or direct permission may still grant access to the same project.
Solution: Review all applicable permission paths before concluding that membership changes have failed.
Group Names Are Hard to Interpret
Problem: Short or generic names make it difficult to tell which people belong or what a group allows.
Solution: Use a consistent naming pattern that describes the team, project, or access purpose. Add an owner and a short explanation where available.
FAQs About Jira Groups
Can a Jira administrator create groups?
It depends on the Jira environment and your assigned permissions. In Jira Cloud, group administration may require organization administrator access. In Jira Data Center, a Jira administrator may have group controls, but externally managed groups can require changes in the connected directory. If you cannot create a group, check your role and ask which system controls group membership.
Does creating a group automatically give members Jira access?
No. Creating the group alone does not necessarily provide product access or project permissions. Administrators may need to connect the group to Jira product access, a global permission, or a project permission. Check the relevant settings and test with a member account so you know what the group actually enables.
Can I use a Jira group to control access to one project?
Yes, if the project’s permission settings allow the group to be assigned the relevant permission. For example, a group can be used for a project permission that lets members browse that project. Review other permissions too, since members might have access through another group or a separate assignment.
Why can’t I edit a group in Jira Data Center?
The group may be managed by an external directory rather than directly in Jira. In that setup, membership changes usually need to be made where the group is maintained, then synchronized with Jira. Check the directory configuration or contact its administrator before making a replacement group, which could create split membership.
Conclusion
Creating a Jira group is straightforward once you know where group management lives and which permissions your role includes. Choose a clear name, connect the group only to the access it needs, and test the result before considering the change complete.
Group changes can become confusing when product access, project permissions, and overlapping memberships are involved. A focused group structure, a named owner, and regular reviews help keep access understandable as teams change. If your team is also evaluating project management options, compare the workflow and deployment requirements carefully before choosing a platform.