nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

cancel access given through outgoing links

frederic_vu_040v1h

I see on some documents, "outgoing links", mainly mailto, including external users.

We have not enabled public links, but on the document shared in "everyone can view", I checked with some of those external users (suppliers), and they confirm being able to access it.

For some of them, we have stopped working with them, and I would like to remove the access they have on those pages.

As IT manager, I would like to have a complete view of those existing direct links to any document in our Confluence, and possibly cancel them. Where is it possible to do this ?

Accepted answers

Nic Brough -Adaptavist-

How are these external users getting permission to see the pages?

You've ruled out public links, so there's either:

They are logging into Confluence as a normal user
The stuff they can see is in a Service Desk Knowledge Base and they are customers
You are allowing them in via "anonymous" access, which means no-one has to log in to see the content

Do you know which it is? (Check the space permissions to see who is allowed in, it should be able to show you all three of those)

All comments

Nic Brough -Adaptavist-

How are these external users getting permission to see the pages?

You've ruled out public links, so there's either:

They are logging into Confluence as a normal user
The stuff they can see is in a Service Desk Knowledge Base and they are customers
You are allowing them in via "anonymous" access, which means no-one has to log in to see the content

Do you know which it is? (Check the space permissions to see who is allowed in, it should be able to show you all three of those)

frederic_vu_040v1h

I've seen the users to whom the documents we shared, arrive in the list of our users, with "has site access".

One of them (let's name him BOB) also appeared in the "Access Request" list and is still pending approval (so was not approved). But if I choose to "Reject" this access request, Confluence tells me "You're about to deny access to BOB. They won't be able to request access again and we'll let them know they were denied access."

So I don't want to do that as we may work with BOB in the future again. Unless you tell me he would be able to come back later if we share a new document with us?

So I think we are in the case 1 of your list, but I'm not sure how/when they get access to our site in the process as BOB was listed among our users with "has site access" and his "Access Request" is still pending approval.

Nic Brough -Adaptavist-

Ok, so Bob is a standard Confluence user, so, yes, you can just lock them out of the system, by removing them from the "has site access" or disabling the account, or even deleting it (not recommended, stick to "disable")

The "reject" is a bit more complex, but I think you've already answered it yourself - yes, you can reject Bob, but that rejection only applies to what Bob was invited to. If rejected, Bob won't get added to the space/page, and they can't be invited to that again, but you can invite Bob to another page, or even add Bob to the space and/or page without the invite.

frederic_vu_040v1h

thank your very much for this clear and precise answer ! :-)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud