Why can't my client open the Jira link I sent them?
· Andrey Guenov
ClientLens for Jira
A Jira link only works for someone with an Atlassian account, access to your site, and browse permission on that project. External people have none of those by default, so they hit a login wall or a 'you don't have permission' error. The options are to license them, use guest access on a paid plan, or send the information rather than the link.
You pasted a Jira link into an email to your client. They clicked it and got a login screen, or worse, a blunt message telling them they don't have permission.
A Jira link is not a public URL. Opening one requires three things at once: an Atlassian account, access to your Jira site, and browse permission on that specific project. Your client almost certainly has none of them.
Which error means what
The symptom tells you where they got stuck.
A login or sign-up screen means they have no Atlassian account, or aren't signed in to one with access to your site. They're stopped at the front door.
"You don't have permission to view this issue" means they got further — they have an account and reached your site — but lack browse permission on that project. Your permission scheme doesn't include them. (If the opposite is happening and people can see more than you intended, that's the same setting from the other side: see why everyone in your company can see your Jira project.)
The issue exists but looks empty or partial usually points to issue-level security: they can see the project but the specific item is restricted.
What actually works
License them. The direct answer. Buy a seat, add them to a role with browse permission. Correct when the client genuinely needs to work in the project — comment, review, file things. Expensive and heavy when they'll log in once and never return; the client seat cost calculator puts a number on that if you're weighing it.
Guest access, on a paid plan. Jira's guest access lets an external person work inside a single space without a full license. It's available on Standard, Premium, and Enterprise — not Free. It's a real, well-scoped feature, and it's the right answer when your client needs to collaborate. Note it's still an invite-and-account flow: a site admin invites them, a space admin adds them, and they sign in with an Atlassian account. What guest access can and can't do in 2026 covers the limits in detail.
Send the information instead of the link. Often the honest answer. If the client just wants to know how things are going, a written update, a scheduled automation email, or an exported report gets them the answer without an account. Jira's automation rules can email any address, licensed or not. Sharing project status with an unlicensed client compares the routes.
Publish a view externally. There's a category of Marketplace apps that expose Jira content — a board, a filter, or a plain-language summary — to people without accounts. Different apps serve different needs, from full board access for collaborators to a simple status page for readers.
The question worth asking first
Before you solve the access problem, check whether it is an access problem.
A lot of the time, the client asking for "access to the project" doesn't want the board. They want to know whether the work is on track. Handing them a Jira interface answers a question they didn't ask, and the usual outcome is that they log in once, find it overwhelming, and email you for a summary anyway. What non-technical stakeholders actually want to know is the fuller version of that argument.
If they'll genuinely work in the project, get them in properly — license or guest access. If they only want to know the status, skip the access problem entirely and send them the status. It's cheaper, faster, and it's what they were actually after.
I'm Andrey. I build small, focused apps for Jira at Guenov Labs, and I write about keeping non-technical people informed about technical work.
FAQ
- Why can't my client open a Jira link I sent them?
- Because a Jira link isn't a public URL. Opening it requires an Atlassian account, access to your Jira site, and browse permission on that specific project. An external person typically has none of these, so they see a login screen or a permission error rather than the issue.
- Can I send a Jira link to someone without an account?
- Not with a normal Jira URL. They would need an account and access. The alternatives are licensing them as a user, adding them as a guest to one space if you're on a paid plan, exporting the information and sending that instead, or using an app that publishes a view externally.
- Why does my client see a 'you don't have permission' error?
- They have an Atlassian account and reached your site, but lack browse permission for that project — or the specific issue is protected by issue-level security. Adding them to a project role with browse permission fixes the first case; the second requires adjusting the issue's security level.