Team Accounts

Chewse | 2018

Supporting organizations with complex team structures

Bigger enterprise companies can have complicated organization structures, and Team Accounts was an effort to provide more flexibility. Necessary features include enabling user permissions, updated billing views, and a new dashboard.


James Pulec
Engineering Lead

Justin Lee

Kelsey Preston
Account Manager


Currently, if parent company BigCo has child company SmallCo and TinyCo under its organization, they would have to exist as three separate accounts without any knowledge of the other.

Chewse treats every account as a straightforward grouping of meals with an associated admin. This structure works for clients within 15–100 members, but for more complex organizations, the existing structure becomes restrictive.

For instance, if billing for SmallCo and TinyCo are actually handled by BigCo, there are only workarounds to how to manage payments through the online product. Or, if an admin for SmallCo and TinyCo was out of office, there was no way for someone within BigCo to log in and handle requests.

We had to build the necessary feature set to properly accomodate larger clients with various organization structures.

Current model. Each team/organization has a dedicated account on Chewse and has to have a dedicated admin account.

Desired model. For enterprise-grade flexibility, different levels of permissions are needed. Also, this model would enable a growth model that would allow existing Team accounts to plug into Organization accounts.

Meal Calendar

Evolution of the client dashboard

The initial Meal Calendar prominently featured photography. While that was fine for smaller clients who ate at most once a day, the format started to break with more meals a day.

The next substantial iteration featured cards that were stacked in order of time.

However, to adequately support different meal schedules that belonged to distinct groupings in a master calendar, the list view was the most comprehensible method.

The initial pass at a Billings page was list of every order. The next iteration would involve consolidating these orders by logical groupings (i.e. schedule, team, time period).

The People section would enable Super Admin users to set permissions for other members of an Organization. Essentially, Teams can be any subset of an Organization. The three levels (Organization, Team, Member) added an entire degree of flexibility over the previous model (Organization, Admin).