A small but growing portion of members belong to not just one, but multiple Circle communities (if you're reading this, you're one of them!)

Starting tomorrow β€” Sunday July 12, 2020 β€” we're introducing a community switcher to give these members an easy way to navigate between their multiple Circle communities in the same browser session.

The switcher won't be visible to a member unless and until they're already a member of multiple Circle communities.

What if I don't want my members to be exposed to this community switcher?

We've got you covered! As a Circle admin, you'll have the option to turn off this community switcher for your members in Settings β†’ General.

Before you decide to turn it off, it's worth considering a few of its benefits:
  • The switch helps members re-engage with your community β€” for example, if a member has unread notifications, we'll add an unread notification count next to your community icon.
  • Our communities have tens of thousands of members and growing. By leaving this on, you can make onboarding easier and reduce friction/confusion for anyone who is already a member of a Circle community.
  • If you decide to split up your own community into multiple in the future, your members will be able to easily share the same account and navigate across them.
  • If you choose to turn off the feature for your members, your community icon will not show up in a switcher on any other community.

My community has Single Sign-On (SSO) enabled. How will this work?

If you have SSO enabled, the switcher will not be visible unless and until someone has logged in on both your community (with their SSO account), and another Circle community (with their Circle account) in the same browser session.

My community does not have SSO enabled and I notice that my authentication pages are now on login.circle.so. Is that intentional?

To make this feature possible, we had to move the login, signup, and password reset pages for communities with Circle accounts to login.circle.so. (Note: this change does not apply to communities with SSO enabled as the only sign-in option.)

The authentication pages should look no different from before, and they're still completely white-labeled with your community branding. We don't plan to introduce any Circle branding to these pages, or to the community switcher.

The reason behind the login.circle.so change is purely technical: as with authentication providers like Facebook and Twitter, or cross-tenant platforms like Slack, Discord, Substack, and Teachable, we rely on storing a shared session token. This token lives on a shared domain, and lets a member switch across communities regardless of whether it's hosted on a circle.so subdomain or a custom domain (e.g. community.mycompany.com.)

If you prefer to host your community authentication pages on a domain you control, we suggest setting up Single Sign-On (SSO) with a custom OAuth provider of your choice.

Are you planning on becoming less white-labeled going forward?

Absolutely not. We intend to remain a completely white-labeled community platform, and in no instance will we ever promote other communities to your members, or vice-versa.

Our intention behind the switcher is to simplify user experience and confusion. The idea comes directly from feedback we've received from members, particularly community creators who themselves belong to other communities and find the current experience frustrating.


If you have any feedback, let us know at support@circle.so. We're all ears. 😊 ✌️
Yasssssssss. This is a big deal. πŸ’―
Nice! If this requires the auth page to go back to the circle.so domain, does this mean that communities with custom domains but no SSO will be able to allow social auth now too?
Yep, good observation! That’s now technically possible - we’re planning to turn it on soon for custom domains w/ a toggle to disable.
Sid Yadav Love that. Technical follow up...if someone auths in socially through Twitter or some other platform, does that still give Circle access to the email address on that social platform (and then by extension send that to my new member Zaps....haha).

It's been a while since I messed around with what was gained through social auth. Back in the day when I was playing around Facebook was still pretty liberal.
Jay Clouse yes, it does. Both Twitter and FB gives us their email (w/ permission of course), which lets us connect that social login to an actual account with that email (or create one). And then once they're in, the member can go into the Authentication tab and do a few things there - they can set a password, they can add other social login methods, they can remove social login methods, etc

TL;DR: every Circle member on the platform is associated w/ an email, no matter how they authenticate into us.
I used my business email address when I sign up for Circle, but when I joined another community (The Lightbulb Moment), I used my personal email address. I tried up update my address on the authentication page, and it said a confirmation email would be sent, but nothing came (not even in the junk folder). Now when I try to access that community, it says I don't have access. Then I log in with the other email address and I lose access to this community and the one that I am building. Help!
HiΒ Coach Becker! I just got in touch directly from support@circle.so to help get this resolved for you. We can merge the two accounts on our end!
Sid Yadav -Β 
In the original post above, the β€œsetting up Single Sign-On (SSO)” link no longer works.

Here is a possible replacement destination -

I noticed that when turning-off the 'Community Switcher' option,Β 
that despite being the Admin (that just turned it off) I, too,Β 
can no longer easily navigate between the Circle.so Community and my own Community. I need to log IN/OUT of each Community.

Possible (in a future update) to allow
Circle Admins to "have their cake and eat it too?"
(i.e. not be affected when turning-off the 'Community Switcher' option)

Post a comment

Log in