Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-868

Include Domain Level Restrictions for Service Desk Public Signup

XMLWordPrintable

    • 1,669
    • 76

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      Update as of 24 May 2022

      Hello all,

      I am excited to announce this feature has started to rollout today.

      For more information checkout the release blog.

      https://community.atlassian.com/t5/Jira-Service-Management-articles/Use-email-domains-to-restrict-external-customer-sign-up-for-your/ba-p/2036372#M1710

      Eager to hear your feedback.

      Cheers, 

      Ben.

      Problem Definition

      Currently when users configure public signup for Service Desk there is no current feature that allows admins to restrict the public signup for specific email domains. While this feature exists for the JIRA public signup option there is no such option for Service Desk public signup. This lack of functionality results in security implications to companies who - for multiple reasons - need to restrict customer public signup for Service Desk only to a specific set of external customers/domains.

      Suggested Solution

      Allow restriction to particular domains and verification process for valid e-mails to avoid spam account creation.

      Workaround

      It is possible to automatically remove tickets created from undesired domains by following the steps of the article below:
      https://community.atlassian.com/t5/Jira-Service-Desk-articles/Restrict-the-creation-of-tickets-of-your-Jira-Service-desk-Cloud/ba-p/1351965

            7ad1551c39c0 Benjamin Paton
            maguiar Marlon Aguiar
            Votes:
            691 Vote for this issue
            Watchers:
            434 Start watching this issue

              Created:
              Updated:
              Resolved: