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

Allow email domain restrictions for public signup

XMLWordPrintable

    • 16
    • 44
    • 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 from Atlassian Product team

      Thank you all for your votes and feedback on this issue. This is the smaller of two issues about the same topic, and has been closed to direct the discussion to https://jira.atlassian.com/browse/JSDCLOUD-868

      That issue in currently Under Consideration and being evaluated for prioritisation. We would love to hear from you over there.

      Problem Definition

      In certain cases, Service Desks need to be restricted to a set of customers belonging to one and the same organisation.
      Public signup does not provide a proper means to prevent incorrect customer accounts not belonging to that organisation from being created.

      The only alternative available right now, is to disable public signup, which has as a result that the Service Desk administrator can get presented with significant amounts of work solely for account creation.

      Suggested Solution

      As such, being able to define an email domain as requirement for public signup, can provide a small degree of safety, while at the same time prevent a lot of overhead for the administrators.

      For instance, if a Service Desk has public signup enabled, and an email domain has been defined, the Service Desk will only allow account creation if the source address conforms to the defined domain.

            7ad1551c39c0 Benjamin Paton
            mnassette MJ (Inactive)
            Votes:
            104 Vote for this issue
            Watchers:
            73 Start watching this issue

              Created:
              Updated:
              Resolved: