Temporary links for controlling page access

Kevin Kott September 11, 2024

Hello,

this is a bit of a niche problem, but I was wondering if there is a way to generate a temporary link to a document or directory. The reason behind this is we are trying to control the route that a page/directory is accessed. For instance, we want a directory to be hidden from the main tree (completed) and it only being accessible through another document/page. This forces the user to read the first document before they can access the second document. What we are trying to avoid is the user skipping the first document entirely and just going to the second document. If there was a way to generate a temporary link, or have a hyperlink that randomizes a temporary link on the page, then the user wouldn't be able to save the link for future use

1 answer

0 votes
Shawn Doyle - ReleaseTEAM
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 11, 2024

No, there isn't anything like this in Confluence.  I was thinking of some workarounds that could achieve your goal, while I came up with a couple, they would all be more annoying to maintain so I won't suggest any of them.

I would suggest, revisiting why you feel you need to restrict/trick the user in this way, look at how you present the information to your users to be sure they read the important parts.

 

Kevin Kott September 12, 2024

Essentially the "second document" is a shared document with a bunch of "first documents". This is to eliminate repeat information within a whole bunch of "first documents". A "first document" might have multiple "second documents" that they would need to choose from depending on the scenario. Since these "second documents" are shared among a bunch of "first documents" it makes more sense to have the "seconds documents" separate from the "first documents". A solution would be to combine the documents, but then the "first documents" get extremely long and we're trying to keep them short and concise. I might table this issue until it actually materializes.

Thinking about this issue further I might be able to include some HTML code that detects the URL a user is coming from in the second document. The URL will remain the same for all users, so <IF NOT URL:First Document|THEN send user to First Document>. I will have to meditate on this some more.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events