Adding End Users to an organization | Community
Skip to main content

Adding End Users to an organization

  • November 16, 2022
  • 3 replies
  • 0 views

Forrest11

Background - I have inherited a small Zendesk setup as a new admin. We have an open Zendesk Support instance as we use it to support end users of two different free mobile applications. We break up the support flows by having a separate brand and support center setup for each. With a third app coming out in the next year we will have a third brand added into the mix. Users submit tickets either via support form or chatbot.

We currently do not use Organizations in anyway. It seems best practice to me to add end users for each app into an organization as this will open up some functionality and help segregate/organize things even further down the road as we grow.

Am I wrong or does the only way to have users automatically added to an organization seem to be based on their email domain? The end users of our apps could have any email domain under the sun so this doesn't work. I don't see a way to do this with triggers either unless I am over looking something.

Is my only option some kind of custom code/web trigger to add new users to an organization when they create their first ticket?

3 replies

Heather13
  • November 16, 2022

yes the only baked in way to auto add users to an Org is via their email address which is awful for your use case.

But I am not convinced you need to use Orgs for your use case since you already have the brand. Instead I would use Orgs in your case for VIP types or Orgs for Users vs others like Partners.


Forrest11
  • Author
  • November 16, 2022

Hi Heather! Thanks for the super quick response and confirming things for me. Appreciate your suggestion on not using Orgs at all in my use case too. I think I agree with you it's not necessary as and probably better suited for corralling other. Picking up a long to-do/look-into list from my predecessor and learning Zendesk as I go.


Heather13
  • November 16, 2022

Any time! BTW I'm also curious as to why you need separate brands -- that means you have 2 separate KBs to keep up. I wonder if you'd consider 1 brand and using different forms which means customers can identify which form to use when filing a ticket if they happen to be using the widget or the portal.

Just food for thought :D