Plan together with YakoPlan shared calendars

Choose a calendar and invite people

Sign in and use a calendar you can administer. Read-only public links are free. Sending administrator invitations requires your own Premium plan; invitations also depend on each person's shared-calendar allowance and the calendar's collaborator limit. Local plans are not shared automatically.

1. Open Shared calendars and choose the calendar you want to share. Review its contents before giving someone access.
2. Invite the person as a viewer, editor or administrator. Use a viewer when they only need to follow the plan; choose a role with more access only when the work calls for it.
3. Review members when the project or group changes. Revoke access from Shared calendars when someone no longer needs the calendar.

Match sharing to the work

For a small project, a colleague who follows milestones may only need viewer access, while the people maintaining the plan need an appropriate editing role. Keep private preparation in a separate calendar. Share the calendar that contains the agreed dates, rather than assuming every personal task belongs in the shared view.

A scheduled work date and a deadline still mean different things. If you move preparation from Tuesday to Wednesday, review the final deadline independently. Day notes can keep useful context close to the dates, while recurring events help represent work that returns each week.

Use public links for read-only access

Public calendar links are free and read-only. Visitors need no account and do not use a shared-calendar slot. This is useful when someone needs to view a schedule without helping maintain it. Treat the link as shareable: send it only when the calendar is suitable for everyone who may receive that link. Set an expiry where appropriate and revoke the link when it is no longer needed.

Sharing does not automatically publish local-only calendars. It also does not make offline account edits immediately visible to others. Reconnect and check synchronization before relying on a change that another person needs to see; version conflicts are reported rather than silently replacing newer work.