Org, client, site: the three levels

The three-level model SendTidings uses: your agency on top, your clients in the middle, their sites at the bottom. It matters more than it sounds.

The three levels

SendTidings has three nested levels, and getting them straight upfront saves a lot of confusion later:

  • Org: your agency. The account you log into. Has team members, billing, and integrations.
  • Client: one of your customers. Lives inside your org. Has a name, a logo, and (optionally) some tags.
  • Site: a website that belongs to a client. The thing that actually gets a monthly report.

So: one org has many clients, one client has many sites, one site sends one monthly report.

Diagram of the three levels in SendTidings: one organisation (your agency) at the top branches to several clients (your customers); each client branches to one or more sites (their websites); a note states each site sends one monthly report on the 1st.
One organisation holds many clients; each client holds one or more sites; each site sends one monthly report.

Why this trips agencies up

If you’re an agency, your clients probably call their own company “the org.” That’s reasonable in their world. In SendTidings, org always means your agency — the account paying the bill. Your client’s company is a client, even if their letterhead says “Acme Organisation.”

It’s worth getting this right because almost every screen, setting, and permission attaches to one of these three levels. When something feels in the wrong place, it’s usually because you’re thinking at the wrong level.

What lives where

A rough guide to what attaches to each level:

  • Org-level: team members, billing, sender domain, and most integrations (Plausible, Matomo, Google connections). Connect once here, reuse across every client and site.
  • Client-level: the client’s name, logo, brand colour, and tags. Things that should look consistent across all of that client’s reports.
  • Site-level: the actual website URL, recipients, send day, primary analytics provider, and the report itself.

The pattern: the higher up something lives, the less often you touch it. Set the org sender domain once. Add a client when you win one. Tweak a site when something changes for that specific property.

See also

See also: Primary provider explained