Jira Guests: Secure External Collaboration Without Extra Licences

Collaborating with customers, suppliers, contractors, and external partners is a common part of modern project delivery. However, giving external users access to Jira has often meant balancing collaboration with security, governance, and licensing costs.

With Jira Guests, Atlassian introduces a simpler way to collaborate securely with people outside your organisation. Instead of providing full user access, administrators can invite external users as Guests, allowing them to work only within the specific Jira Spaces and work items they need - without exposing the rest of the instance.

In this guide, we'll explore what Jira Guests are, how they work, when to use them, and the key considerations for administrators planning their rollout.

---

What are Jira Guests?

Jira Guests allow you to give external users, such as customers, partners, contractors, or suppliers, access to specific Jira Spaces without granting them the same level of access as full licensed users. Guests can collaborate where needed while remaining restricted to only the spaces and work items they have been invited to access.

Guests are included at no additional cost on paid plans (up to 5 guests per paid user, subject to your Atlassian plan)

When should you use Guest Roles?

Guest roles are ideal when you need to collaborate securely with people outside your organisation. This might mean working alongside customers on shared spaces, coordinating with vendors or suppliers, giving contractors temporary access to delivery work, or allowing partners to participate in support activities.

What can Guests do?

Guests can only access one Jira Space per site.

The permissions available to guests depend on the space's permission scheme, but typically they can:

• View work items they have permission to access

• Create and edit work items

• Transition and resolve work items (change statuses, including to Done)

• Comment on work items, and edit or delete their own comments

• Upload attachments, and delete their own attachments

• Be assigned to work items and assign them to others

• Link work items within the same space

• Log work and manage their own worklogs

• View combined and summarised project data, development information, and read-only workflows

• View watchers (and manage watchers in company-managed spaces)

• Participate in boards, backlogs, and views within the space

• Receive notifications and participate in discussions

  
  

Jira administrators remain in control of exactly what guests can and cannot do.

What Guests cannot do

Guests have a fixed set of permissions that cannot be expanded through permission schemes or space roles. This means they cannot:

• Access more than one Jira space per site

• See work or data outside their assigned space

• Access site-level experiences (Home, Dashboards, Goals, or Plans)

• Use any global permissions (e.g. administer Jira, bulk changes, browse users)

• Administer spaces, edit workflows, or manage work item layouts

• Manage sprints

• Archive, restore, or delete work items

• Move work items to other spaces

• Set work item security or modify reporters

• Set fix versions (the "Resolve work items" permission)

• Delete or edit other users' comments, attachments, or worklogs

• Link work items to other spaces

Benefits of Guest Roles

Guest roles give you a way to collaborate with external users securely and efficiently. You share only the spaces they need, reducing the risk of exposing sensitive information elsewhere in your instance. From an administration perspective, there's no need to create full internal accounts for people who only need limited, space-scoped access. This also brings governance benefits — your internal work stays protected — and can reduce licensing costs, since guest users don't require the same licensing model as full Jira users (subject to your Atlassian plan).

How to Implement Guest Roles

Guest access is granted in two steps:

1. A site admin invites the guest to the Jira site (this controls who can sign in as a guest).

2. A space admin adds the guest to a specific space (this controls where they can collaborate).

Before inviting guests, review the following:

• Review the permission scheme for the target space to ensure guests can only perform the actions you intend.

• Check the Browse spaces permission in company-managed permission schemes to ensure guests cannot see a list of other spaces on your site.

• Set team-managed spaces to Private if they contain sensitive work — this prevents them from appearing in the space directory. (Note: "Limited" access still allows all logged-in users to view the space.)

• Review Jira Product Discovery space access to ensure guests have not been granted Contributor or Creator roles.

---

Final Thoughts

Jira Guests represent an important step forward in secure external collaboration. By allowing customers, partners, contractors, and suppliers to access only the projects they need, organisations can improve collaboration while maintaining strong governance and reducing unnecessary licensing costs.

As with any new capability, the real value comes from implementing it with the right governance model, ensuring that access remains secure, scalable, and easy to manage as your organisation grows.

Ready to get the most from Jira Guests?

Whether you're planning to introduce Jira Guests, reviewing your current permission model, or looking to optimise your Atlassian environment, Sourcesense International can help.

As an Atlassian Platinum Solution Partner, we work with organisations to design secure, scalable collaboration environments that maximise the value of Atlassian Cloud.

Get in touch with our team to discuss how Jira Guests can support your organisation's collaboration and governance strategy.