Restricted portal users can see the links to JIRA and BitBucket links in the Confluence main menu

Colette Moran October 27, 2016

I've got a Service Desk project (cloud) that some external restricted portal users have access to.
I'm hooking up a Confluence space to it so that they can use the knowledge base search features within the portal.

When a user searches and clicks on the search result it displays nicely inside the portal.
But if that page contains a link to another page in the space, then when they click on that they'll be taken to the space on Confluence proper.

They can then see the links back to our main JIRA site (cloud), which just redirects them to the portal if they click on it, but the name on the link is just our company name so it's not obvious this is what will happen.

They can also see the "Bitbucket - Company Name" link which takes them to our team profile page on Bitbucket. There's nothing for them to see there so having the link in the menu is just adding potentially confusing options for users.

Finally they can see the "Company Name Confluence" link. This goes to a page with the breadcrumbs "Administration/Users" and the message "Not permitted. You are not permitted to perform this operation".
At this point they can hit back to get back to the original space but there's no link on this page to take them there.

So the questions are:

  1. is there a setting that I can use to remove Bitbucket from the menu options?
  2. Is there a setting I can use so that the Confluence link in the menu will divert them back to the only space they have access to rather than showing them an unhelpful error message?
  3. And failing both of those, is there a way I can exclude the top level parent page for the space showing up in the search so they never get the opportunity to get out to the main Confluence site?

1 answer

0 votes
Colette Moran October 27, 2016

I managed to remove the Bitbucket link via the Confluence > General Configuration> Application Navigator settings, where I set the Bitbucket entry to be restricted to full JIRA users.

And I can live with the link back to the main JIRA because it's useful for them to be able to get back to the portal, even if the link name isn't obvious.

So the only real problem is the fact that clicking on the Confluence link in the menu or the logo/home button in the header beside the menu takes them to the error page.

The exact same problem is described in detail and with screenshots here https://jira.atlassian.com/browse/CONF-36417.

Suggest an answer

Log in or Sign up to answer