For your team

Calendar

How the project calendar and your own calendar work, how repeating events behave, and which events your client sees.

Last updated:

Each project has its own calendar for its site meetings, deliveries and key dates. You also have your own: Calendar in the sidebar gathers every event from the projects you’re on, so you don’t have to check each one in turn.

You can view a day, a week, a month or a year; weekends are hidden until you untick Hide weekends. Anyone who can see the Calendar can add and edit events — an event belongs to the project, not to a person, so there are no invitations and nobody is notified when one is added.

Events

An event is a title, a time (or All day), an optional description, and a colour and pattern to tell types of event apart at a glance. New events aren’t saved until you press Create event; after that, changes to a one-off event save as you make them.

Your calendar

Calendar in the sidebar gathers every event from the projects you’re on — completed projects are left out — and shows which project each event belongs to, including when you open one.

The filter icon above the grid opens a row of project pills: click one or several to see only those projects, and All projects to see everything again. The icon stays highlighted while a filter is on.

Add event from here asks you to choose the project first; Create event stays disabled until you do, because an event always belongs to a project. Once created, it appears on both your calendar and that project’s.

Open any event and the project pill lets you move it to another of your projects. A repeating event moves as a whole series.

Repeating events

A new event can repeat Every week, Every 2 weeks or Every month — monthly meaning the same weekday, so a first-Tuesday meeting stays on the first Tuesday. Every series needs an end date; Navanto suggests 12 weeks out, and a series can run to at most 520 occurrences.

Whether an event repeats is decided when you create it, so a one-off can’t be turned into a series later.

Editing one occurrence takes it out of the series for good: it becomes a standalone event, stops repeating, and later changes to the series — including deleting the whole series — no longer touch it. Saving your changes asks Only this event or All events, and deleting asks Delete this event or Delete all events, so you choose each time.

Changing how often a series repeats, or its end date, always applies to the whole series.

What your client sees

Each event carries a Visible to client setting, off by default, and that is the whole rule: the portal calendar shows exactly the events marked visible, read-only. Marking an event visible — and any later change to an event your client can see — needs the Client portal permission, because it changes what your client reads. Client-visible events carry an eye icon on your calendar so you can tell at a glance.

On a completed project the calendar stays readable but nothing can be changed.