Global customer permissions determine whether projects can let customers:
- create their own accounts in customer portals
- view portals without logging in
Regardless of which global permission you set, projects will always have the option to require customers to log in. This lets you have projects with different permission settings.
To view or change global customer permissions for your site:
- .
- Under , select Configuration.
- Look for the subsection titled Customer permissions.
Can customers create their own accounts?
- Yes. Project admins have the option to let customers create their own accounts.
- No. Customers can never create their own accounts. They can't send requests unless agents add them to the project.
Can customers access and send requests from the help center without logging in?
- Yes. Project admins can let customers view portals without logging in. Customers still log in to view their requests.
- No. If you picked No above, this one's already a No.
How global permissions affect project permissions
The following table shows how the global customer permissions affect what's available in project customer permissions:
Global settings | Available project settings | |
Can customers create their own accounts? | Can customers access the help center without logging in? | Who can access the portal and send requests to the project? |
---|---|---|
No (default) | No (default) |
|
Yes | No |
|
Yes | Yes |
|
Learn more about project-level customer permissions in .
Customer licenses
Customers aren't assigned a
license, which means it's free for them to send you requests, and free for you to receive them.CAPTCHA
The customer portal uses an invisible honeypot field to stop bots from creating spam accounts on the portal. Portals that don't require customers to log in use RECAPTCHA to stop spam requests.