Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-10719

Recently Updated List has users that aren't in current group

    • 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.

      When a user updates info, this shows up in EVERY user's Recently Updated list; we want to use Confluence as a customer information portal. If this is the case, Customer1 will have users that can see updates for Customer2 users. This seriously impedes our ability to use this product.

      If User1 is in the group Customer1, and User2 is in the group Customer2, and they're not in any shared groups, why can they see each other in Recently Updated or in the People Directory? Some ability to control this would greatly increase the utility of this implementation.

      Thanks!

            [CONFSERVER-10719] Recently Updated List has users that aren't in current group

            Tim,

            On further, further reflection This issue seems to be a duplicate of CONF-1134 which has been linked to this issue, I suggest voting for that issue instead.

            Adnan Chowdhury [Atlassian] added a comment - Tim, On further, further reflection This issue seems to be a duplicate of CONF-1134 which has been linked to this issue, I suggest voting for that issue instead.

            Timothy,

            Thinking about this issue again, the recently updated list will not show any updates that the logged in user does not have the permission to see. I take it that you already have the customer information set up in different spaces with different permissions so that users of each space cannot see work or updates in the other space?

            Adnan Chowdhury [Atlassian] added a comment - Timothy, Thinking about this issue again, the recently updated list will not show any updates that the logged in user does not have the permission to see. I take it that you already have the customer information set up in different spaces with different permissions so that users of each space cannot see work or updates in the other space?

            Timothy, thanks for the suggestion.

            Unfortunately the use case that you describe is not one that we want to do strategically with the product. It will result in a complex set of permissions supporting a use which isn't the core purpose of Confluence, which is to provide an internal collaborative environment for teams.

            Adnan Chowdhury [Atlassian] added a comment - Timothy, thanks for the suggestion. Unfortunately the use case that you describe is not one that we want to do strategically with the product. It will result in a complex set of permissions supporting a use which isn't the core purpose of Confluence, which is to provide an internal collaborative environment for teams.

              Unassigned Unassigned
              9f5c31b7f02b Timothy James
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: