Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1654

Allow Service Desk to Use Confluence as Knowledge Base w/o Anonymous

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Knowledge Base
    • None
    • We collect Jira Service Desk 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 JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Without the ability to allow our customers access to the knowledge base w/o allowing anonymous access, this severely limit its usage when it comes to sensitive information such as password or other information that could potentially be seen by browsing internet user – when it comes to Atlassian Cloud.

      Please figure out a way to limit KB access to only registered SD customers. I haven't use it before, but I see in Confluence that you can allow JIRA to handle user management? Is that a viable workaround? I know I can see SD Customer roles in JIRA but they don't exist in Confluence.

            [JSDSERVER-1654] Allow Service Desk to Use Confluence as Knowledge Base w/o Anonymous

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011876 ] New: JAC Suggestion Workflow 3 [ 3649477 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665349 ] New: JAC Suggestion Workflow [ 3011876 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2325889 ] New: Confluence Workflow - Public Facing v4 [ 2665349 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2053835 ] New: JSD Suggestion Workflow - TEMP [ 2325889 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049065 ] New: JSD Suggestion Workflow [ 2053835 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1280583 ] New: JSD Suggestion Workflow - TEMP [ 2049065 ]
            jonah (Inactive) made changes -
            Description Original: Without the ability to allow our customers access to the knowledge base w/o allowing anonymous access, this severely limit its usage when it comes to sensitive information such as password or other information that could potentially be seen by browsing internet user -- when it comes to Atlassian Cloud.

            Please figure out a way to limit KB access to only registered SD customers. I haven't use it before, but I see in Confluence that you can allow JIRA to handle user management? Is that a viable workaround? I know I can see SD Customer roles in JIRA but they don't exist in Confluence.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-1654].
              {panel}

            Without the ability to allow our customers access to the knowledge base w/o allowing anonymous access, this severely limit its usage when it comes to sensitive information such as password or other information that could potentially be seen by browsing internet user -- when it comes to Atlassian Cloud.

            Please figure out a way to limit KB access to only registered SD customers. I haven't use it before, but I see in Confluence that you can allow JIRA to handle user management? Is that a viable workaround? I know I can see SD Customer roles in JIRA but they don't exist in Confluence.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-1654 [ JSDCLOUD-1654 ]
            Owen made changes -
            Workflow Original: TTT: Simple Issue Tracking Workflow [ 841586 ] New: JSD Suggestion Workflow [ 1280583 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            shihab made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: To Do [ 10071 ] New: Done [ 10044 ]

              Unassigned Unassigned
              0137353a32ef Anthony Scudese
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: