Sounds like you're using Federated ID alongside the private community feature? If so, that's why you're needing to approve users. The private community feature is for those who want the ultimate hands-on control of who gets to see and contribute to the community. However, for folks who are using Federated ID, it can turn into more of an inconvenience — especially those with a large already established userbase. We have a solution for just an occasion! We call it "secure embedding". This feature turns off "unauthorized" versions of your community, only allowing instances that are "signed". Signed embeds of Muut like ones that use Federated ID :) The muut.com version of your community would be disabled, but it would still be active on your site. Just head to your forum settings page, turn on [secure embedding](https://muut.com/settings/#___/secure-embedding), and then you can turn off the [private community](https://muut.com/settings/#___/private-community). Once done you'll be good to go. Oh, and don't worry, as the community owner you'll still be able to view the community on muut.com in case you need to manage content or anything else :)

You're right, it works now. Thanks! However, the community is publicly visible (at least the first page is) How do I have it so that it's not accessible publicly (including that page) until you log in to WP? Ideally, anon users see a nice "you should sign in first' type prompt. Authenticated users should seamlessly logged in and presented with the for um landing page (this part is working correctly)

You would want to restrict the Muut page behind a member's only page on WordPress. Since Muut is now only available on your website now, you can control access to the page with WP instead of worrying about Muut :)

Of course! That makes sense. Thank you Monika.

Monika, would this work with Brilliant Directory platform?