• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      If we take a look at the Permissions and Restrictions page, we can note the following statement:

      If someone doesn't have 'View' space permission, links to pages in that space won't be shown at all.

      However, in Confluence 5.8.x versions, this operation does not match with this statement. If you put a link to a page inside a space that you do not have the view permissions, it will be redirected to a "Page not Found" message. If the user does not have the permissions to view the space, the links will still be displayed and once you click, a page not found.

      This is a request to change the documentation or check if this is a bug that can be fixed in the system.

      However, this could be also a request to remove this function from the system, if it was supposed to be implemented. The reason would be that removing/hiding links could affect on the proposal of the page.

      For example, if the link is tied to a word in a text, if it would not be displayed for the user, it could affect on reading the text, once it would be missing some words. It could be kept only for direct links, in example, only pasting the page URL to a page without having it tied to a word.

            [CONFSERVER-39576] Links and Space Permissions

            Rachel Robins added a comment - - edited

            I have updated the documentation to reflect the current behaviour. Namely that if someone doesn't have 'View' space permission, links to pages in that space will be visible to them, but they'll get a "page not found" message. The space key is not revealed in the link URL. 

            This is slightly different to the behaviour when a page is restricted - where the user will get a "page restricted" message, and in some cases may be able to request access to the page. 

            Sorry for the oversight. 

            Rachel Robins added a comment - - edited I have updated the documentation to reflect the current behaviour. Namely that if someone doesn't have 'View' space permission, links to pages in that space will be visible to them, but they'll get a "page not found" message. The space key is not revealed in the link URL.  This is slightly different to the behaviour when a page is restricted - where the user will get a "page restricted" message, and in some cases may be able to request access to the page.  Sorry for the oversight. 

            Can you clarify what exactly there are no plans to implement please? Right now the documentation is different than the software behaviour. Will the software be updated to match the documentation? Will the documentation be updated to match the software?

            Documentation states - "If someone doesn't have 'View' space permission, links to pages in that space won't be shown at all." 

            Reality on 6.0.4 "If someone doesn't have 'View" space permission, links to pages in that space are shown, but lead to page not found error when clicked."

            Which is expected?

             

            keith.earley@eidosmontreal.com added a comment - Can you clarify what exactly there are no plans to implement please? Right now the documentation is different than the software behaviour. Will the software be updated to match the documentation? Will the documentation be updated to match the software? Documentation states - "If someone doesn't have 'View' space permission, links to pages in that space won't be shown at all."  Reality on 6.0.4 "If someone doesn't have 'View" space permission, links to pages in that space are shown, but lead to page not found error when clicked." Which is expected?  

            Atlassian update

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. Thanks again.
            Regards,
            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Atlassian update Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. Thanks again. Regards, Confluence Product Management

              Unassigned Unassigned
              gdecampos Giuliano C.
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: