Use Cases

People reach for calendar sync the moment they have more than one calendar that matters. A freelancer juggling two clients. A consultant on three overlapping engagements. An EA running calendars for two executives at different companies. A small team where some live in Google Workspace and others in Microsoft 365. The pattern is the same: events scattered across systems that don’t talk to each other, and a missed meeting waiting to happen.

The pages below walk through specific setups: what the problem looks like in practice, how to configure Hetk, and which privacy settings keep client information from leaking sideways when calendars belong to different people or organisations.

Find your situation

• Freelancers, for two or more clients who each invite you to their calendar, with no client able to see the others’ meetings.
• Consultants, for overlapping engagements where each client’s calendar should reflect your availability without exposing who else you work with.
• Lawyers and law firms, where court dates, client matters, and a shared firm calendar meet, and confidentiality is a professional obligation rather than a preference.
• Executives, for board commitments, a company calendar, and a personal one kept aligned so an assistant scheduling on your behalf never double-books.
• Executive assistants, who run calendars for more than one principal, often across different companies and providers.
• Recruiters, for interview loops booked across candidate, hiring-manager, and personal calendars without leaking who is interviewing where.
• Real estate agents, whose showings, closings, and brokerage calendar need to agree, often on the move between two phones.
• Remote teams, where some people live in Google Workspace and others in Microsoft 365, with shared availability that doesn’t require everyone to switch tools.
• Work and personal life, one calendar for the job and one for everything else, so a dentist appointment blocks work time without broadcasting the details.

What the setups have in common

Two patterns show up again and again. The first is a read-only mirror: a one-way sync that copies events from a source into another calendar so you see them everywhere, without letting edits flow back. The second is a private busy block: a sync with “Mark as Private” turned on, so a meeting reserves the time on a shared calendar while the title, description, location, and attendees stay behind. Most real configurations are a handful of these pointed in the right directions.

Privacy is the part people underestimate. A calendar shared with a colleague, a partner, or a client is a channel, and anything you sync into it is something they can read. The use-case pages are specific about which syncs should carry full detail and which should reduce to “Busy,” because getting that wrong is how a client name ends up on the wrong screen.

Each scenario started as a real question to support@hetk.io. The page documents the configuration the customer ended up with. If yours isn’t here, write to us. The list grows when people ask.