Users restricted to a space, can they access Smart Linked content?

Question

OK, I'm pretty sure I know the answer, but I have to ask.  I have a communal space, and I have a contractor group who only have access to that space.  My question is this: if I post a smart link to a document in another space, will my contractors be able to access that document?  I'm guessing no.

I'm trying to limit their access to only the one space, but there are some documents in other spaces which the contractors need to access.  I wound up copying one document over to their space so they can have access to what they need, but I need to provide some other documents as well, and I hate, hate, hate making copies of the documents.

What is the best solution here?  I'm guessing the smart links won't be available to my contractors... any advice would be greatly appreciated.

Nicolas Grossi · Accepted Answer

@Randy O'Neal You might take a look at this thread: https://community.atlassian.com/t5/Confluence-questions/Smart-Links-Not-Appearing-for-Other-Users/qaq-p/1748228

HTH

Nicolas

Kristian Klima_gtcuat · Accepted Answer

Hi @Randy O'Neal

Permissions will be a blocker. HOWEVER, there is a workaround, actually TWO workarounds, that do not require manual copy paste of content. And you will not need smart links for COnfluence Content.

Workaround 1

Using Space Sync for Confluence allows you to sync content from multiple spaces into another space. So you can have one target space to which you push content from your source spaces. The app has per-space permission levels, so you can ensure that the sync is one-directional.

Workaround 2

Providing the contractors only consume the content, you can use Scroll Documents and Scroll Viewport apps to do the following.

* Use Scroll Documents to create Documents - think of them as virtual documents = any section of a space that you define. So you would have a section/entire space A as Document 1, a section of space B as Document 2.
* Then, using Scroll Viewport, you built a doc center/website where Document 1 and Document 2 would be your content sources.
* You restrict access to of the Viewport site to your contractors (via your company's SSO or via token - both features come standard with Viewport).
* SSO ensures that your contractors will be able to access linked/embedded content that they have access to via SSO.
* Every time you update the content in your spaces A and B, you simply rebuild the Viewport site.

Viewport site is completely independent from Confluence (permission wise), so you can have your cake and eat it (depending on the specifics of your use case) - your contractors will not need a seat on Confluence. Again - they can only read content.