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

Notify admins they cannot edit the directory they're logged in through

XMLWordPrintable

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

      The UI for the User Directories configuration in Confluence's admin has an operations column.

      When you are logged in using a user registered for a directory, this user don't have the privilege to modified the directory it belong to. As stated here:

      You cannot edit, disable or remove the directory your user belongs to. This precaution is designed to prevent administrators from locking themselves out of the application by changing the directory configuration in a way that prevents them logging in or removes their administration permissions.

      However, there is nothing in the UI that indicates why a directory cannot be edited.

      Possible Resolution

      I suggest we keep the "Edit" button but grayed it out. When a user hover over the grayed out button add a simple message like "you are logged in via this directory, hence it is not possible to modify it" in the operations column when that is the reason the directory cannot be edited.

        1. Screen shot 2012-01-04 at 3.56.37 PM.png
          Screen shot 2012-01-04 at 3.56.37 PM.png
          194 kB

            [CONFSERVER-24312] Notify admins they cannot edit the directory they're logged in through

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3568525 ] New: JAC Suggestion Workflow 3 [ 4332976 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3180759 ] New: JAC Suggestion Workflow 4 [ 3568525 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3037077 ] New: JAC Suggestion Workflow 2 [ 3180759 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2529959 ] New: JAC Suggestion Workflow [ 3037077 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2259519 ] New: Confluence Workflow - Public Facing v4 [ 2529959 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2196061 ] New: Confluence Workflow - Public Facing v3 [ 2259519 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1927848 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2196061 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1755556 ] New: Confluence Workflow - Public Facing v3 [ 1927848 ]
            jonah (Inactive) made changes -
            Description Original: The UI for the User Directories configuration in Confluence's admin has an operations column.

            When you are logged in using a user registered for a directory, this user don't have the privilege to modified the directory it belong to. As stated [here|http://confluence.atlassian.com/display/JIRA/Configuring+User+Directories#ConfiguringUserDirectories-UpdatingDirectories]:

            {quote}You cannot edit, disable or remove the directory your user belongs to. This precaution is designed to prevent administrators from locking themselves out of the application by changing the directory configuration in a way that prevents them logging in or removes their administration permissions.{quote}

            However, there is nothing in the UI that indicates why a directory cannot be edited.

            *Possible Resolution*

            I suggest we keep the "Edit" button but grayed it out. When a user hover over the grayed out button add a simple message like "you are logged in via this directory, hence it is not possible to modify it" in the operations column when that is the reason the directory cannot be edited.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-24312].
              {panel}

            The UI for the User Directories configuration in Confluence's admin has an operations column.

            When you are logged in using a user registered for a directory, this user don't have the privilege to modified the directory it belong to. As stated [here|http://confluence.atlassian.com/display/JIRA/Configuring+User+Directories#ConfiguringUserDirectories-UpdatingDirectories]:

            {quote}You cannot edit, disable or remove the directory your user belongs to. This precaution is designed to prevent administrators from locking themselves out of the application by changing the directory configuration in a way that prevents them logging in or removes their administration permissions.{quote}

            However, there is nothing in the UI that indicates why a directory cannot be edited.

            *Possible Resolution*

            I suggest we keep the "Edit" button but grayed it out. When a user hover over the grayed out button add a simple message like "you are logged in via this directory, hence it is not possible to modify it" in the operations column when that is the reason the directory cannot be edited.
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-24312 [ CONFCLOUD-24312 ]

              Unassigned Unassigned
              cdarroch Daz
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: