When a customer registers on a Guide / Help Center login page, it sends an email to them to finish setting up their account by setting up their password. As soon as they do this, they're brought into the Help Center and can see all content. Is there a way for us to not have them be fully in control of getting into the Help Center, and instead we monitor registrations and ensure we want to provide them with access? This seems like it would be a big security concern if with this setup, anyone can register and get in.
Is there a way to review/approve Guide/Help Center registrations
User segments sounds promising for limiting article content, but I'm still unsure of whether I can set this up the way I'd like for access to support tickets. Today, we have some products where we have the need for end users to email into Support to have a ticket created and will likely never log into our help center (just based on their persona and job, they are not the type to take the help center click path) - my understanding is having "Anybody can submit tickets" disabled would take away this ability for that user set.
One workaround for this approval scenario I'd like to have, is it possible for me to create an easy report showing end users and when they were created and what their name/email is? This would allow us to weekly/monthly review users and ensure we don't have anyone that isn't from our clients registered.
@ahmed11 - Is there a way to search more granularly? I'd like to not only specify creation timeframe, but I'm more concerned with finding users recently created who are fully registered and can access our Help Center.
Luckily we don't use messaging or social logins. We have an SSO setup from our product to our help center and then the normal help center login page with registration. I'm just trying to figure out an easy approach to monitoring that latter scenario so that we don't have people who aren't clients registering and interacting in our help center. Is your approach still what you would recommend for that need?
Historically, we only allowed SSO as we always had Redirect to SSO enabled. However, we have a use case now where we need clients for another of our products to be able to access our help center (that product doesn't have a link or SSO to our help center set up). Because of this, I switched us to the "Let them choose" setting below, which now allows folks to go to our help center login page and self-register. My concern is the general public can now register and get into our help center, which isn't ideal, and we want an easy way to monitor end users to ensure we limit this to just our actual clients.
Hey Ahmed,
I'm not familiar with that sync process you refer to, how would I do that?
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.