Create one organization for each group of people who share team meals. Everyone in an organization — Admins, Orderers, and Staff — can join the group orders on its meal calendar, so a group that shouldn’t see those meals needs its own organization.
If you have an NYC office, everyone in the NYC organization on CaterCow should be able to join a team-wide meal. If there’s also an SF office, that should be a separate organization, with its own meal calendar. SF teammates can’t see NYC’s meal calendar unless they join the NYC organization too.
If you’re an Admin for both the NYC and SF organizations, you can manage both from one account and switch between them in the Organization menu. You’ll still send each office’s Staff that organization’s own meal calendar link.
A couple of rules of thumb:
- Same group of people, multiple addresses? Keep one organization and use separate saved addresses instead. An organization’s group orders share a meal limit — by default, 1 meal per person for group orders at the same time — so one person can’t get a company-paid meal at both addresses for the same mealtime.
- Different groups of people with little or no overlap? Separate organizations make more sense — for example, an SF organization and an NYC organization, or a Sales organization and a Product organization. Each organization has its own members, settings, and meal calendar.
When you signed up, we created your first organization for you, named after you (for example, “Jane Smith’s Team”). To add another, see How do I create an organization? If your company has a company-wide account with CaterCow, read the note for larger companies there first: organizations you add from your dashboard aren’t connected to that account automatically.
If you’re not sure which setup fits your situation, email us at support@catercow.com and we’re happy to help you figure out the best structure.