Fastmail is worth considering when household members want separate email logins and shared editable calendars within one multi-user account. Use public ICS only for information suitable for anyone holding its read-only link.
Fastmail gives a household two different calendar-sharing routes. People in the same multi-user account can receive named permissions, including editing. Someone outside that account can receive a public, read-only calendar link. Choose the route before sharing the schedule: a link is not the same thing as a private invitation.
The useful result is a calendar each person can understand and use with the intended access. This guide follows a fictional household and gives you specific setup and removal checks. For the broader decision about what belongs in a shared schedule, start with our family-calendar privacy guide.
Check who has an account and who only needs a view
First list the participants and the calendar account each actually uses. Fastmail’s users-versus-addresses explanation distinguishes a separate user, with their own login, mailbox and storage, from an extra address delivering to an existing inbox. Adding an alias does not give a relative an independent user.
Write the calendar job beside each name: read the schedule, change events or manage sharing. A relative who only wants to know about a Saturday visit has a different need from the person arranging it. Also check the available account and plan arrangement before adding paid users; this guide does not quote a household price.
Fastmail’s strength here is the combination of separate users and calendar permissions within the account. It can suit a family wanting those tools together. If everybody will remain on unrelated services and must edit the same calendar, do not assume a public subscription will provide that workflow.
Match the account to the household
The personal-plan guide describes Duo for two people and Family for three to six, with Standard-level features including calendars and custom domains. Membership and calendar permissions are separate decisions. Count people needing their own login: an extra alias does not create another user. Confirm personal-use eligibility and the full local payment before adding the household.
Build a small household permission map
Imagine fictional household members Rowan and Sam arrange pickups, while relative Alex only needs selected visit information. The following is an original planning example, not a real family record or a configuration verified in a live account.
| Calendar and person | Intended arrangement | Acceptance check |
|---|---|---|
| Household Plans: Rowan | Owner responsible for access | Can identify everyone with access |
| Household Plans: Sam | Same-account user allowed to change events | Can change a harmless sample event |
| Visits: Alex | Read-only public subscription, only if its content is suitable | Sees the visit without an editing route |
| Personal: Rowan | Kept outside this sharing setup | No household or public access was enabled |
The separate Visits calendar prevents a convenience link from carrying the whole household timetable. That is an editorial design choice: create only the calendars you can maintain, and name them for their actual audience. If Visits is too sensitive for a public link, use another appropriate arrangement rather than filling it with sensitive events.
Give another user access inside the account
The same-account sharing instructions describe this route:
- Open Settings, then Calendars, and select the intended calendar.
- In Team sharing, enter the other user’s email address and add them.
- Choose viewing, changing events, or changing events plus sharing.
- Save, then ask that person to inspect the calendar in their own account.
Editing permits creating, modifying and deleting events. Give sharing control only to someone responsible for membership. Access can be changed again in the calendar’s Team sharing settings.
For Rowan and Sam, use a sample titled Household test, with no private location or description. Sam should change its time and add a clearly marked test event. Rowan should see the intended changes. Avoid testing deletion on a real pickup or assuming an action worked because a menu appeared.
Use a public subscription only for a suitable audience
Fastmail’s public calendar documentation describes read-only ICS files accessible to anyone holding the URL. They are intended for calendar clients, rather than a normal browser calendar page. Publishing offers a full-event version and an availability-only version.
- Select the calendar in Settings, then Calendars.
- In Publish, enable either full details or free/busy information.
- Copy the displayed address and save to activate it.
- Give the intended recipient the subscription address through an appropriate channel.
The same screen can disable publication or reset its address if it spreads beyond the intended audience. Resetting changes the link; it does not erase a copy someone already downloaded.
For Alex, Rowan should first inspect exactly what the Visits calendar contains. Availability may be enough for arranging a visit; full details may be appropriate for a deliberately public activity. Neither choice is a named-person access list. Do not treat a difficult-to-guess link as proof that its holder cannot forward it.
Check the recipient’s real result
Ask Alex to use the calendar application’s subscription function, rather than simply importing one downloaded file. A saved snapshot and a maintained subscription have different expectations; our calendar-download guide explains that distinction. Subscription refresh timing depends on the receiving service, so agree a separate channel for urgent changes.
Run three checks with harmless content. Can Alex see the intended calendar? Are the visible details suitable for this audience? Can Alex change the shared source, or only view it? Record the actual result instead of assuming that every calendar application presents subscriptions identically.
If the calendar is missing, check the complete copied address, whether publication was saved and whether the client used subscription rather than import. If the time is old, first establish which copy Alex is viewing. Our calendar-update checklist covers the wider difference between invitations, copies and updates.
Practise removal before relying on it
Make removal part of the sample exercise. For Sam, change the named user’s access in Team sharing, then check again from that user’s account. For Alex’s public route, disable publication or reset the address and deliberately check the old subscription route.
Separate the questions: can the old route fetch future calendar information, and what information already exists on someone else’s device? A stopped feed does not recall screenshots, copied appointments or downloaded ICS files. Keep that limit in the household’s expectations.
If a reset is needed, distribute the replacement only to the intended audience and update your private record of where it was shared. Also check whether the same calendar has another active sharing route. Removing one person or one URL is only one part of the access review.
Choose the arrangement you can maintain
Fastmail is a practical candidate when your household wants separate accounts and an editable shared calendar in the same service. The named-user route is the useful starting point for people who manage events together. A public subscription is useful for a deliberately shareable, read-only schedule.
Before choosing or expanding an account, finish the permission map and confirm the current user arrangement. Before adding real plans, prove one sample event, one permitted edit and one removal. That small exercise turns an attractive feature list into a setup the household understands.
Sources and verification
Editorial review 2026-10-18. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- Fastmail: Sharing calendars with other usersChecked Same multi-user-account calendar sharing through Settings/Calendars and Team sharing; view, edit and edit-plus-sharing permissions; saving, event-editing scope and access changes.
Limits: Applies to users in the same account, not arbitrary external editable invitations. Does not establish every third-party client's appearance or refresh behavior. - Fastmail: Calendar sharing via public URLChecked Public read-only downloadable ICS; full-detail and free/busy URLs; Publish controls and Save; reset or disable a public route.
Limits: Anyone with the link can access it. Reset/disable governs the route, not erasure of existing downloaded copies; no universal receiving-client refresh interval is established. - Fastmail: Using multiple email addresses vs. multiple usersChecked An alias reaches an existing account, while a separate user has distinct login credentials, mailbox and storage.
Limits: Not a quote for a particular current multi-user plan or a complete administrator-privacy specification. - Fastmail plan selectionChecked Personal Individual/Duo/Family with Standard-level features; Business mix-and-match Basic/Standard/Professional and storage/app boundaries.
Limits: Duo two users, Family three-to-six; personal family pricing is not a business seat quote.