Allow for granular control of "Who can raise requests" in a service project.

XMLWordPrintable

    • 2

      Currently when setting a project so that "Anyone can raise a request on the customer portal or by email" it causes the project to be visible to anyone in the portal and anyone can email the email channel configured for the project.

      This request is to split these permissions into two separate permissions allowing administrators to choose if they want anyone to be able to raise requests via email and through the portal independently.

      • Who can raise requests via email
      • Who can raise requests via the customer portal

      A use case for such a configuration would be in an instance where the JSM instance is public-facing and is intended so that anyone can raise requests via email. However, it is not always helpful to have all projects listed in the portal since this could allow for requests to be raised in error or in the wrong project/request type.

      Having such granular control should allow for new customers to raise requests via email, which will add them as a customer in that specific project, and then they would be able to see the request types for the project in the customer portal after login.

            Assignee:
            Unassigned
            Reporter:
            David McCoy
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: