I've looked at the Chat FAQ and I'm still not sure what the point of having a "parent user" of the chat account is.

Why can't a Chat account be associated with multiple other Stack Exchange accounts in the normal way?


2 Answers 2


To be honest, much of the "parent user" idea is still a leftover of the original plan to let each Stack Exchange site have its own chat site. You can see this in http://chat.meta.stackexchange.com and https://chat.stackoverflow.com/ – having a "parent user" here obviously makes sense.

At some point, we decided that not every single SE site needs its own chat site; it's much nicer for the community to gather on https://chat.stackexchange.com. This was also in the very early days of expanding the Stack Exchange network via the Area 51 process. The very first SE 2.0 site (Web Applications) was launched around the same time as chat.

Our handling of cross-site accounts back then was quite limited, as you see from the amount of issue reports regarding account association from that time. To explain it in simple terms, back in those days the master "unit" was a user account on a specific site; from there on, you could follow the trails to accounts on other sites that were associated with it.

This handling makes sense considering how the network evolved from one to three or four sites, but once we began having dozens of sites, that didn't really scale anymore. Lots of work in the second half of last year was spent on a project (codenamed "Costanza Wallet") to correct this, and turn the philosophy around: now, the master "unit" is a network account, and it can have one to many site accounts.

Chat is still very much in the old mode, in which having a single site account to be the master user was pretty much the only way. We have made gradual improvements in this area, but it's still far from done. I don't know if we're ever going to totally get rid of the idea of a user's "main site", since most people have such a site that they consider to be the most important (if not only) site they're active on, but over time, this idea should disappear into the background more and more.

Long story short: On chat.so and chat.meta.se, the use of a "parent user" is clear; it's very much identical to the relationship between a main site user and the corresponding child meta user. On chat.se, the use of a "parent user" is, for the most part, a relic.

  • 2
    Great answer, thanks. The logical follow-up question is: what work (if any) is currently being done in this area? Will there be a way to set the network user as the parent user? Why isn't there a way to access the chat user from the network profile?
    – jtbandes
    Apr 3, 2012 at 17:38
  • 2
    You know, your “over 80 sites” figure, while not exactly false, still keeps falling further and further behind reality. :)
    – tchrist
    Jul 28, 2014 at 5:52
  • 3
    @tchrist What can I say, modesty is a virtue. If Mercedes advertised with "More than one car sold every year", that'd be awesome. ;)
    – balpha StaffMod
    Jul 28, 2014 at 5:55

The parent user in chat is the user that decide some of the privileges users have in chat; for example, it is the account that decides when a user on chat is a moderator.


I guess they use just an account because, differently, the code should verify if the user is a moderator in any of the sites where the user has an account.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .