Hi!
The Communities feature is not compatible or supported in Domain Separation as described here:
Domain separation and Communities • Australia Customer Service Management • Docs | ServiceNow
Is there any way to bypass this or have a workaround for making a Community to work in global domain instead separated domains? The idea would be that community is not domain separated information, while the rest is.
We tried to setup an example community on global domain with all necessary configurations there, which allowed the test user to see some content posted by my admin account, but they were not able to ask a question on a forum themselves. The widgets on the homepage were not visible and the "ask a question" link found in the header directed to a "404 not found" page. This occured evven after granting the user "Full access" permissions and the sn_communities.admin role.
So do we conclude that the communites on the domain separated instance simply is a dead end, or is there some way to make it work?
BR Ändi
