How are bigger organizations getting around the one email per group limitation?

So we are considering trying out hipchat in our organization which consists of a few thousand people, and a good 200+ people would be using hipchat.

We would have dozens of different teams, you usually would be a member of lets say at least 3-4 teams concurrently.

How are other organizations working around the limitation that you have to use a different email adress to sign up for different hipchat groups? 

Surely just using a single group would be a nightmare in terms of administration (eventhough we would be using LDAP directory since we'd host hipchat server by ourselves).

The only other workaround I can imagine is having to write a little webapp that lets you choose from the list of known hipchat groups and then creating and registering an alias email adress at our exchange server.

Still a stupid workaround for an extremly bad architecture decision.

Any bigger user groups out there that dare to share their experiences/workarounds?



Log in or Sign up to comment
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Craig Castle-Mead
Published Mar 26, 2018 in Hipchat Data Center

Migration of Hipchat server to Data Center - a retrospective to use the clients After a bunch of testing (rooms, memberships, check for private message history, and most importantly - the custom emoticons!) nearly everything was looking as we needed, however...

386 views 2 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you