User Groups

Published Date: August 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered:

Onboarding Jama Connect®

Summary

Plan user groups and permissions in Jama Connect® to provide users with the appropriate level of access while balancing organization-level and project-level administration. Define which permissions should be managed by Organization Administrators and which can be delegated to Project Administrators.

Consider aligning user groups with license types when appropriate to simplify access management.

Resolution

User groups help you manage where users can access content in Jama Connect. When planning groups and permissions, consider both the level of access users need and who should be responsible for managing that access.

Define Organization-Level Access

Determine which access should be managed centrally by your Organization Administrators.

Organization Administrators can create organization-level user groups and grant those groups appropriate access to Jama Connect projects.

When defining organization-level access, consider:

Which groups of users require access to specific projects.
Which permissions should be consistent across the organization.
Which access decisions require centralized management.
Which permissions can be delegated to Project Administrators.

Avoid managing permissions at a more granular level than necessary at the organization level.

Delegate Project-Level Permissions

Project Administrators can manage permissions within the projects they administer.

Consider using organization-level groups to provide access to the appropriate projects while allowing Project Administrators to manage more granular permissions within those projects, such as access to specific components and sets.

This approach can help balance centralized governance with the flexibility individual projects need.

Consider License Types When Creating Groups

User groups may align with the license types assigned to users.

Keep in mind that licenses and permissions serve different purposes:

A user's license determines the capabilities available to them in Jama Connect.
A user's group membership and permissions determine where they can exercise those capabilities.

For example, you might create a Read-Only organization-level group and grant that group Read access to the appropriate projects. Users with Stakeholder licenses can then be added to the group. Their license provides read capabilities, while the group's permissions determine where they have that access.

Plan Your User Group Structure

Before creating groups, identify the common access needs across your organization.

For each proposed group, consider:

Who should belong to the group.
Which license types those users are likely to have.
Which projects the group needs to access.
What level of access the group requires.
Whether more granular permissions should be managed by the Project Administrator.

Keep the group structure as simple as possible while meeting your organization's access and governance requirements.

What to Do Next

Define the organization-level user groups needed for your deployment and assign the appropriate project access.

Coordinate with Project Administrators to determine which permissions will be managed within individual projects. As users are added to Jama Connect, assign the appropriate license, group membership, and permissions based on their role and access needs.

Review your group and permission structure as your deployment expands to ensure it continues to support your organization's access and administration needs.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to