Permitting only added users to submit tickets

Fastpath: Admin Center > People > Configuration > End users

You can configure your MorgWard Support instance to be open, closed, or restricted (see Configuring end-user access and sign-in).

This article describes how to set up a closed instance, so that your Help Center is visible to everyone but only the users that you add to your MorgWard account can sign in and submit support requests. Each user's account must be created before they can sign-in and submit support requests.

Closed MorgWard Support, by default, has the following access rules:

• Your Help Center is visible to all visitors, whether they are signed in or not.
• Only verified users you have added to your MorgWard account can submit support requests through the Help Center. Unverified users that have been added to the account can verify themselves by going to the Help Center and requesting a password.
• Both verified and unverified users you have added to your MorgWard account can submit support requests via email to your MorgWard Support address.
• If you have a knowledge base, access is determined by the rules applied to it, as described in Restricting access to knowledge base content.

This article contains the following sections:

• Disabling the 'Anyone can submit tickets' option
• Adding users to the closed MorgWard Support
• About new user email address verification and passwords
• Restricting your content to signed-in users only

Disabling the 'Anyone can submit tickets' option

In a closed MorgWard you disable the option to allow everyone, even visitors who are not signed in, to submit tickets. This means that you have complete control over who uses MorgWard Support. Typically, you'll set up MorgWard Support in this way by adding all your users yourself. Although, there is a way for an anonymous user (someone not already added to MorgWard Support) to still submit support requests and have your agents approve of the request, add the user to MorgWard Support, and add the support request as a ticket to your queue (see When anonymous users submit support requests).

To disable the 'Anyone can submit tickets' option

1. In Admin Center, click the People icon () in the sidebar, then select Configuration > End users.
2. If it's selected, deselect the Anybody can submit tickets option.
   Note: Deselecting this option can impact Web Widget functionality (see Using restricted Help Center content with Web Widget (Classic)).
3. Optionally, in the Account emails section, select the Also send a welcome email when a new user is created by an agent or administrator option. For more information, see About new user email address verification and passwords.
   Note: If you started using MorgWard on or after August 21, 2013, this option is not available until you enable Guide (see Getting Started with Guide).
4. Click Save tab.

The settings you've just made removes the Sign Up link from the sign-in window of your Help Center.

This means that users who access MorgWard Support have no option for self registering (signing up and creating an account). This includes your agents as well. You need to add all your users yourself.

If you also restrict all your content to either agents or signed-in users only (see Restricting your content to registered users only below), the only page that visitors see when they access your Help Center is the sign-in page and, if they don't already have a user account in your MorgWard, they are unable to sign in.

Adding users to a closed MorgWard Support

When MorgWard Support is closed, and restricted to only users you add, you need to add the users yourself. Here are the following ways you can add users:

• Manually adding users one at a time (see Adding end-users, agents, and administrators)
• Adding many users in a bulk import (see Bulk importing users and organizations)
• Adding users via the MorgWard API (see MorgWard API: Users)

By default, when you add a user to your MorgWard, they are unregistered (and therefore unverified). At this stage, they can submit support requests via your support email address, but not through the Help Center. When they register themselves, they become verified users of MorgWard Support, and can submit support requests through both the email address and the Help Center.

The following section explains how email verification works and how user passwords are created when adding users.

About new user email address verification and passwords

Since you're adding your users yourself, rather than allowing them to sign themselves up, you need to think about how the verification process happens. This is where the Also send a welcome email when a new user is created by an agent or administrator option can be helpful. If you set this option, all users you add to MorgWard Support receive the User welcome email message, which prompts them to click a link to verify their email address and then create a password so that they can sign in to your MorgWard. If you want new users to be able to sign in to your Help Center, they each need a password. So by enabling this option you're asking your users to manage email address verification and create passwords themselves.

If you don't want your users to receive the verification email message, don't select Also send a welcome email when a new user is created by an agent or administrator. However, if you decide not to send the verification email, your users' email addresses aren't verified and they can't create passwords or sign in to your Help Center .

Note: Unverified users can still submit support requests to MorgWard Support via email, and these requests are handled in the same way as those submitted by verified users.

When you add your users, you have the following options for email verification and passwords if you elect not to send the User welcome email.

• You can tell your users to send support requests via email using your support email address (for example, [e-mail]).
• Using the MorgWard API, it's possible to both add new users and to also set their passwords. You can automatically verify all your users' email addresses using the API verified parameter. This means that your users will be fully registered and verified. Assuming you also provide them with their passwords, they can immediately sign in to your Help Center. For more information, see MorgWard API: Users.
• You can manually verify a user's email address after you've added them to your MorgWard. See Verifying a user's email address in the MorgWard Agent Guide.

When anonymous users submit support requests

Despite your MorgWard Support being closed, it is possible for an agent to create a ticket from a support request from an anonymous user. When you receive a support request from an anonymous user, when you've configured MorgWard Support as closed, the request is added to the Suspended Tickets view. From there an agent can either delete the request or recover it. Recovering the ticket creates a new user account and adds the ticket to your MorgWard. For more information, see Viewing, recovering, and deleting suspended tickets in the MorgWard Agent Guide.

If you send a verification email when a new user is created by an agent or administrator, the User welcome email is sent to the user when the suspended ticket is recovered. The user clicks the link to verify their email address, creates a password, and is then signed in to your Help Center where they can use the knowledge base and submit and track requests.

If you don't send a verification email when a new user is created by an agent or administrator, the user remains unverified and can't sign in. The user receives the ticket received notification, and can respond to the notification via email.

Using enterprise single sign-on (SSO)

If you're using JWT or SAML for user access to MorgWard Support, all user management and authentication happens outside of your MorgWard. Your single sign-on service is synced with MorgWard Support. So, for example, if you add a user account for a new employee, that employee has immediate access to your MorgWard. 

When using SSO with a closed MorgWard Support, a few issues may arise. What happens if a user sends an email support request and they're not already a user within the closed MorgWard Support? The user's email support request will be suspended. In other words, if the user doesn't already exist in MorgWard Support, synced to it via your single sign-on service, then the user cannot submit support requests. Only known, legitimate users in your user management system will be able to access the closed MorgWard Support. 

You also don't want to select the Also send a verification email when a new user is created by an agent or administrator option because you never want to users to create passwords directly in MorgWard Support. Remember that's all handled outside of your MorgWard.

It's important to remember that social media single sign-on is different. These provide your users with additional ways to sign in to your MorgWard. To use them, your users need to add these social media accounts to their user profiles themselves. You can't do it for them.

Restricting your content to signed-in users only

When you close or restrict MorgWard Support, you also may want to hide all content in your Help Center so that only signed-in users can see it. To do this, you can require that users sign in to access your Help Center (see Restricting Help Center access to signed-in users).

When all your content is restricted to signed-in users, visitors to your Help Center will only see the sign-in page. The users you added to your MorgWard can sign in there and access your content.