Portal suddenly requiring registration

Question

Backstory: I have a second site admin that, due to issues of kneejerk reactions and not documenting changes, I've recently restricted from making backend changes to our spaces.

Up until this morning, if a new person went to our portal, they could still put in a ticket but the first field required them to enter an email address. Now, it's requiring registration before actually getting to the different service desk portals. I know there used to be an "allow anonymous" setting, but for the life of me I cannot find it in this new version!

Below is the log section where I see the change, but I cannot find this setting!

GlobalCustomerAccessSettings{globalCustomerAccessPermission=PUBLIC, anonymousAccessEnabled=true, recaptchaForAnonymousDisabled=false}GlobalCustomerAccessSettings{globalCustomerAccessPermission=PUBLIC, anonymousAccessEnabled=false, recaptchaForAnonymousDisabled=false}

Trudy P Claspill · Answer

It is true that Atlassian has changed their terminology. There was an announcement some time back that they were changing from the term "products" to "apps".

So you have to select Jira Apps instead of Products.

Then, as you found, you can select Customer Access.

And then, as stated in the instructions, you will find the option to Allow customers to create accounts

In your image notice this:

If you check the box farther up in the form for External accounts

...then the final checkbox referenced in step 3 appears.

Chad Henderson_qpe911 · Answer

The issue with the documentation is that it is not layed out for the new cloud version. There is no longer a "products" section and the anonymous switch is no longer in the Customer Access section.

Trudy P Claspill · Answer

Hello @Chad Henderson

Referring to this documentation:

https://support.atlassian.com/jira-service-management-cloud/docs/set-up-and-manage-portal-access/

To allow anonymous access to customer portals the Site Admin needs to allow anonymous access to Help Centers for the site. The details are in that document.