I'm having this error message when adding someone to a space

[Javier Vázquez Gurrola]

I'm having "No one can be added at the moment Hash 1R8H57G
Trace 6bdc0bbf9ece41fa842751316754ff81" when trying to add someone to Jira space

[James Gamble]

Hi Javier,

The first thing I’d check is whether your account has the Browse users and groups global permission. Jira requires that permission to search for and add existing users to a space, and Atlassian has documented this exact type of hash error when someone tries to add people without it. A Jira admin can check under Settings > System > Global permissions.

I’d also ask a site admin to check the organization’s user invitation settings. The same error can appear when invitations are disabled or require admin approval, even though the Add people window still lets you enter an email address. If the person already has site access, try searching for their display name instead of their email address and make sure you select their Atlassian account, not a contact result imported from Google, Slack, or Microsoft.

If another Jira administrator can add the same person successfully, that points more toward your permissions. If nobody can add them, the site invitation settings, the user’s account status, or a backend issue are more likely.

If those checks don’t resolve it, I agree with @Gor Greyan that you’ll need to contact Atlassian Support and include the full hash, trace ID, approximate time of the attempt, your site URL, and the affected space. Those trace values are mainly useful to Atlassian because they can match them to the server-side logs.

Thanks,

James

[Gor Greyan]

Hi @Javier Vázquez Gurrola

A few things I'd recommend checking first:

• Confirm that the user you're trying to add already has an Atlassian account and has accepted any pending invitation.
• Try adding a different user to the same space. If that succeeds, the issue may be specific to the original user.
• Try adding the user from an incognito/private browser window or a different browser to rule out a browser-related issue.

If the issue persists and you're consistently seeing the same, I'd recommend opening a support ticket with Atlassian and including those values. They can use the trace identifier to investigate the server-side logs:

https://support.atlassian.com/contact/