← Back to home

Organization

Updated on 2026-10-13

For:Musher guide

Team life in six blocks: Members, Tasks, Messages, Protocols, Notes and the phone (Manage › Organization); a Viewer does not see “Tasks” and cannot post messages. Illustration.

Six tabs, one place

Organization brings the kennel's collective life into six tabs; the page stays open to every role.

The row of six Organization tabs (circled); “Tasks” (1) disappears for a Viewer role.

  • The six: “Members”, “Tasks”, “Messages”, “Protocols”, “Notes” and “Club”.
  • In “Members”, anyone — Vet, Guide or Viewer included — sets their own absences. Only “Tasks” disappears from the row for a Viewer.
  • To invite someone or change their role: Inviting your team, which describes the five roles (Owner, Handler, Vet, Viewer, Guide).

Members: who's here, who's out

The roster, your notifications, and the absence grid week by week.

The Members tab: “Stop notifying me for this kennel” (1), the “Availability” grid (2), “+ absence” (3) and “Next” (4).

  • Roster: the owner also finds “Invite a teammate” and “Pending invitations”; every other role sees the roster alone.
  • “My notifications”: “Stop notifying me for this kennel” turns off, for you only, the care reminders by e-mail — vaccinations, vet follow-ups, end of treatments, heats, whelping, pregnancy checks, equipment servicing —; teammates keep theirs, and nothing changes inside the app. There is no chore reminder by e-mail. The day's reminders go out at 07:10: ticking the box between 07:00 and 07:10 still lets the morning mail through. Nobody else sees this setting.
  • “Availability”: a weekly grid, twelve weeks at a time (“Previous” / “Next”), green for available, red for out.
  • Absence: reason (Vacation, Sick, Unavailable, Other), start and end dates, optional note. Each member sets their own; the owner can set or edit anyone's.

Tasks: templates, 7-day tracking, catching up

Chore templates, and a table showing who did what over 7 days.

The Tasks tab: the last 7 days tracking (1), its key (2), “New task” (3) and “Previous week” (4).

  • Templates: recurring or one-off chores — feed, walk, clean, or a custom type with its own label —, frequency (every day, certain days, once on a date), optional times, the dog (or the whole kennel), assigned teammates. Only the owner creates, edits, deactivates or deletes them; others read them, and a Viewer doesn't see the tab.
  • Checking off: today's due chores are checked off on the dashboard, not here; a checked chore disappears from that list.
  • Tracking (everyone except Viewer): one row per chore and time of day, one column per day. A cell shows the initials of who did it (key under the table), “to do” for today, ✕ when nobody checked it on a past day, “–” when it wasn't scheduled. “Previous week” / “Next week” go back in time.
  • Catching up: within the last 7 days, clicking a ✕ or “to do” cell checks it, after a confirmation. The owner picks who did it; others check in their own name. A check is undone the same way, by the person it's credited to or by the owner. Beyond 7 days, read-only.
  • Limits: the tracking shows who checked, never what time (offline, the check only arrives once the connection is back: the time would be the sending time). And a chore is never ✕ for a day before its last edit: MushMate only keeps its current definition.

Messages: instructions, priorities, urgent notices

The team's board; an “Urgent” message demands a confirmation.

The Messages tab: the form (1), the priority (2), the recipient (3) and an “Urgent” message with its “Got it” button (4).

  • Posting (everyone except Viewer): optional title, body, priority (Normal, Important, Urgent), recipient (“All members” or one teammate, excluding Viewers).
  • A message pinned by the owner stays on top. The author edits or deletes their message; the owner, any. Editing a message changes its title, its body and its priority (Normal, Important, Urgent) — not its recipient.
  • Urgent: red border. The targeted recipient — or, for the whole team, whoever reacts first — sees “Got it”; until someone confirms: “Awaiting confirmation”.

Protocols: the kennel's procedures, document import

The kennel's written procedures, by category: everyone reads them, two roles write them.

The Protocols tab: “Import a document” (1), “New protocol” (2) and a category of protocols (3).

  • Categories: Feeding, Cleaning, Care, Other.
  • Writing: the owner and the Vet role. Everyone else sees, in place of “New protocol”, “Only the owner and the vet can create or edit protocols.”
  • Importing (those two roles): a PDF or photos of paper sheets, up to 25 MB. MushMate suggests the protocols found, to uncheck before saving. A Word file isn't read directly: save it as a PDF first.

Notes: the team's scratchpad

A word, photos if needed; nothing to sort or search, no editing afterward.

The Notes tab: the entry field (1), “Add photos” (2) and “Save” (3).

  • Any member — Viewer included — writes; the author or the owner deletes.
  • A note can't be made of photos alone: a minimum of text is required.

On the phone: Manage › Organization

On the phone, reading is open to all, writing follows the roles, and “Members” can be written by the owner.

The Organization page of Manage on the phone and what each entry allows. Illustration.

  • Messages, Notes: every role, same rules as the web (a Viewer reads without posting). Posting or editing a message needs the network; Notes works offline and goes out when the connection is back. “Edit” on a message — yours, or any for the owner — also changes its priority; the priority is only sent if you changed it.
  • Offline, the last copy: Messages, today's chore list and the task templates can be read from their last copy, dated (“Offline · copy from Oct 11 18:02”) — if they have already been opened online on this phone; otherwise the screen says “Offline” and offers “Retry”. Pulling the screen down re-reads.
  • Protocols: read-only, and readable without a network — the phone keeps a copy, refreshed at every sync, and the screen says “Last read: …”. After seven days without a read, or when the date is unknown (a copy that came from a backup), a banner says so, with “Retry”; a phone that has never synced says so too, instead of showing “No protocols”. Every role reads them. Adding or editing is done on the web.
  • Tasks: today's list is on “Today”; creating or editing a template (“Manage chores”) stays owner-only and needs the network. The template there takes, as on the web, several times a day (“Add a time”: one checkbox per time, kept earliest to latest, none for a one-off chore) and assigned people (among those who can tick a chore; advisory only, anyone can tick, assigned or not). A member with no name entered reads “Member”, their role underneath; a person who has left the kennel stays assigned until you untick them.
  • “Task tracking”: the same tracking as the web, day by day; network required, absent for a Viewer. “Mark as done” and “Undo” there do what the web clicks do.
  • “Members”: the owner invites, revokes an invitation, changes a role, sets or clears an access end date and removes a member (Inviting your team); the other roles read the list. Under the list, “My notifications” (every role) turns off your care reminders by e-mail, as on the web; it needs the network, and without one the phone says it doesn't know where the setting stands instead of showing a switch that reads “off”. Below, “Availability” shows the same 12-week grid, grey for unavailable; “I'll be unavailable” declares an absence, and a tapped cell moves or removes it (yours, or anyone's for the owner). The phone neither shows nor writes the reason: it says “Unavailable”, even for an absence set on the web with a reason.
  • Invitee's side: “My invitations” (Manage › Organization) accepts an invitation you received, while one is waiting for your account's email address; the “Create your kennel” screen offers it before its form.

Going further