Confluence
  1. Confluence
  2. CONF-12842

Disabling the People Directory section from the Browse menu

    Details

    • Last commented by user?:
      true

      Description

      Updated Description

      Some company policies want to restrict the viewing of a list of users. Thus they would like to disable the people directory and any way to access it.

      Workaround

      Is detailed in this documentation: http://confluence.atlassian.com/display/DOC/Hiding+the+People+Directory

      However if you navigate to the profile of a user, and then click on the "People" in the breadcrumb link (Dashboard >> People >> FullName >> Profile) or you go to the URL directly <CONFLUENCE_INSTALL>/browsepeople.action, you will be able to access the people directory.

      To workaround this, set up Apache webserver in front of confluence and redirect requests to this URL.

      Original Description

      It would be good to have an option to disable the People Directory section in the Browse menu of the Dashboard page.

        Issue Links

          Activity

          Hide
          Ming Giet Chong [Atlassian] added a comment -

          Ideally, you might want to try the manual workaround below to remove the text from the "Browse" menu:

          1. Shutdown Confluence
          2. Look for global-browse-sections.xml.
          3. Comment/Remove the web-item below:
            <web-item key="global-people" name="People Directory" section="system.browse/global" weight="10">
                    <label key="people.directory.title" />
                    <link linkId="people-directory-link">/peopledirectory.action</link>
                    <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.NotSharedModeCondition"/>
            </web-item>
            
          4. Restart Confluence

          For Confluence standalone version, the global-browse-sections.xml is located in the WEB-INF\lib\confluence-2.9.jar. After making the changes to the file, you can simply place the file into the WEB-INF\classes\plugins folder. You need to create the plugins folder manually.

          Show
          Ming Giet Chong [Atlassian] added a comment - Ideally, you might want to try the manual workaround below to remove the text from the "Browse" menu: Shutdown Confluence Look for global-browse-sections.xml. Comment/Remove the web-item below: <web-item key="global-people" name="People Directory" section="system.browse/global" weight="10"> <label key="people.directory.title" /> <link linkId="people-directory-link">/peopledirectory.action</link> <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.NotSharedModeCondition"/> </web-item> Restart Confluence For Confluence standalone version, the global-browse-sections.xml is located in the WEB-INF\lib\confluence-2.9.jar . After making the changes to the file, you can simply place the file into the WEB-INF\classes\plugins folder. You need to create the plugins folder manually.
          Show
          Jeremy Largman [Atlassian] added a comment - The doc is now updated: http://confluence.atlassian.com/display/DOC/Hiding+the+People+Directory
          Hide
          Matt Ryall [Atlassian] added a comment -

          Why do people want to disable the people directory? Is this actually a duplicate of CONF-7837?

          Show
          Matt Ryall [Atlassian] added a comment - Why do people want to disable the people directory? Is this actually a duplicate of CONF-7837 ?
          Hide
          Masashi Ueno added a comment -

          Perhaps our situation is unique, but we use Enterprise Hosted Confluence with anonymous access enabled, and we don't want (or need) users to see the individuals who manage the site.

          Show
          Masashi Ueno added a comment - Perhaps our situation is unique, but we use Enterprise Hosted Confluence with anonymous access enabled, and we don't want (or need) users to see the individuals who manage the site.
          Hide
          Ben Wright added a comment -

          It would be great if we had not merely an option to disable the link on the dashboard, but disallow anonymous access to the directory entirely. Currently with the manual work-around the actual directory is still searchable/viewable. Hiding the information is much more important to us than the link (though that would be nice too). We want to keep the wiki open to anonymous users so that they can get a sense of what it is before they sign up.

          Show
          Ben Wright added a comment - It would be great if we had not merely an option to disable the link on the dashboard, but disallow anonymous access to the directory entirely. Currently with the manual work-around the actual directory is still searchable/viewable. Hiding the information is much more important to us than the link (though that would be nice too). We want to keep the wiki open to anonymous users so that they can get a sense of what it is before they sign up.
          Hide
          Tim Moore [Atlassian] added a comment -
          Show
          Tim Moore [Atlassian] added a comment - Related JIRA Studio issue: https://studio.atlassian.com/browse/JST-5176
          Hide
          John Masson [Atlassian] added a comment -

          I think the story described here could be achieved by CONF-7837 if it were implemented by removing access to the people directory for all groups.

          As such I'm going to close this issue as a duplicate. For those not already watching it or having voted on CONF-7837 you might like to do so.

          Show
          John Masson [Atlassian] added a comment - I think the story described here could be achieved by CONF-7837 if it were implemented by removing access to the people directory for all groups. As such I'm going to close this issue as a duplicate. For those not already watching it or having voted on CONF-7837 you might like to do so.

            People

            • Votes:
              20 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Last commented:
                1 year, 22 weeks ago