Overview

How notification templates are read is mostly how Kazoo always allows sub accounts to override their parent accounts, with some twists :))

In simpler term, KAZOO performs something called walking up the account hierarchy, or we like to call it The Walk. We start from sub account to read the notification template and if not found we walk up the account hierarchy (going to parent account/accounts) stopping in each parent account to see if the document exists in that parent account and if not continuing the walk UNTIL we reach to the first parent account that is the reseller of the original account that we started our walk. In that case if the reseller doesn’t have that document then we abandon our walk and fall back to read system_config notification template.

If during our walk any parent account has the document we stop the walk and return that document.

We also repeat the same process for template attachments. So a child account can only customize just only JSON part of document and not customizing the HTML/Text template, doing so will that account to inherit its parent template attachments.

Monster UI branding app and even Kazoo is totally showing its age and the UI part is somewhat confusing.

Some visual notes:

1. On side bar when a a template name is in grey or has a red circle next to it it means that template is disable which means the account has the document (so if you see that in brandingtest account that means brandingtest is overriding its parents and reseller. Also it means when one of the child accounts (like brandingtest2here) doesn’t have the document, it would inherit it from brandingtest and not reseller, other ancestors or system.
   1. So in summary disable means this account has document and the walk is always stops in this account level
2. A Green cog means the notification is enabled and the account is overrides the notification. That means the account has the document and the walk stops in this level
3. When changing enable/disable the effect of red circle is not visible away you need to change view (go to other apps or tabs) and come back
4. There is another cog next to Template name in title of the page when you go to that template that allows you to remove the customization in that account so it would inherit the template from its ancestors. Also there is an option to force write the template from system config itself. that means it override its parents settings and the walk with stop in this level for its
5. If in doubt you can always check the payload from API when loading the template, look for something account_ovverridden or account_defined field set to true. Kazoo is never wrong :))