Access to other spaces and even apps

[David Allaway]

I have just shared a JPD space with an external user as a test.  They setup there Atlassian login using https://id.atlassian.com/ which was all good.  I then added them as a contributor via the Share option.  They got the email and then could see the space.  

However, they can also see all other spaces that we have setup in Jira and they even have access to app like our timesheet app and can see the developers timesheets.

Why is this happening and what I can do to prevent it.  I just want the external user to be a contributor on the single space.

[Patryk Grzegorz · Accepted solution]

In Jira Product Discovery, access to other spaces (or apps) works through project roles and permissions, not global admin rights.

To see or work in another space:

• The space admin needs to add you to one of the roles there (usually "Member" or "Contributor").
• Go to the space settings > Access > Invite people, or use the share button if it's public-ish.
• If it's cross-product (e.g. linking to Jira Software), you need separate permissions in that product too—JPD doesn't inherit them automatically.

If you're not seeing the "Switch space" option at all, check your Atlassian account has licenses for both products enabled. Sometimes it's just a matter of the space owner granting you explicit access.

Once added, you should see it in the space switcher top-left. If still blocked, ask the space admin to confirm your role and license status. That usually clears it up fast.

[David Allaway]

Hi Patryk

Thanks for your answer.

However I think you have misunderstood my issue.

The new user can see other spaces and apps and I don't want them to.  I only want them to see the JPD space that I have shared with them.

I want to know why this is happening and how I can prevent it?

Thanks

David

[Kamila Czubaj]

Hey David,

What are the space permissions?

[David Allaway]

Hi Kamila

It looks like this

[Kamila Czubaj]

Hey, when you have a limited access to the space, when you add a contributor they have access to everything that is not private to view. In this case every space that is open or limited. 

Do they have access to the Jira space too (where the delivery lives)?

If you do not want them to have access werehere, you can remove them as contributors and give them access to the publish view, where they have read-only access. Learn how to publish your views in this article.

Here isa detailed guide of the contributors role: The different types of users creators contributors 

Manage your team 

[Jens Schumacher - Released_so]

My guess is that the user was added to the jira-software-users group and gained access to the other spaces via that group. Check the groups for the user and ensure they are not a member of any groups. 

Another reasons could be that the other spaces are accessible to every user on the instance, in which case you'd have to restrict those spaces. 

[Leon Oud]

I had the same issue when we added an external user for the first time.

The default permission in the permission scheme of projects (now spaces) used to be or still is "Any logged in user" for Jira projects, so you'll have to set the "Browse project" in your permission scheme to another group that does not include your external user. This permission regulates the visibility of the project. Same goes for your filters and dashboard, that have a "Your company" sharing permission, also use a different group for that.

Would like to see some kind of permission overview per user tool, but that is probably in the Guard add on.