Events
Eventsevents.html
Events is where a team keeps its operating rhythm — the standing meetings, the publications and the deadlines that come round again and again. You describe each one once, with a rule such as the second Tuesday of every month, and the page works out every date it falls on for the whole year. Nothing is typed in date by date, and a date that moves because the rule says so moves everywhere at once.
Events belong to a team, not to you: everyone on the team who has access sees the same list. They are separate from tasks. An event is a thing that happens; a task is work somebody does about it, and you can add tasks for any occurrence of an event.
You will only see Events if you have access
Events appears in the navigation strip, between Team and OKRs, only when a team you belong to has switched it on and you have been given access. If you do not see it, ask a team admin — see Who can see Events below.
Year, Month and List
The page opens with one row of controls, drawn the same way as the top of Tasks. At its left, View offers three views, each with a small picture beside its name (the picture alone when the window is narrower than 1440 pixels; hover for the name). Next come Previous, the year or month, Next and Today, which step the calendar and are hidden in List, where there is nothing to step through. Today is grayed out while the year (or, in Month, the month) on screen is already the current one. At the right are Add event, Actions and Customize. All three views read the same events, so choosing one is only a question of how much of the year you want in front of you. While the events are still loading, the row is already there with the views dimmed. Point at a view for what it shows: Year Rhythm: each event as a lane across the twelve months, Month: one month as a grid of days or List: what is coming up, by week.
- Year is the rhythm view and the default. Events are drawn as lanes — Weekly, Monthly, Quarterly and dated, Special Events and Publications — across twelve month columns, with a line marking today. The lane names stay in place while the grid scrolls sideways. Press a lane to open that event. The header has two rows: the quarters across the top, with the months beneath them, so you can see which quarter a column belongs to without counting. Months that have already passed are shaded, and occurrences in them are drawn more quietly than the ones still ahead of you.
- Month is a seven-column grid of the days in the month, with each occurrence on its day.
- List shows what is coming up, grouped by week, for the next ten weeks. It is the quickest way to answer “what is on this month?”.
Every kind of event has its own shape as well as its own color, so the types can be told apart without relying on color. An occurrence that has already passed is drawn as an outline rather than faded, so it stays readable.
The left column and the right rail
The left column holds the Teams card (see Putting several teams on one page), a filter for each type of event (Weekly meetings, Monthly meetings, Quarterly and dated, Publications and Special Events) — each with a count — and a Show placeholders checkbox. Turning a type off hides it from every view. These choices are remembered for you.
The rail on the right has three cards: Coming up, the next occurrences; Event tasks, the tasks that have been added for events; and Your access, which says how you came to have Events on this team.
Every card on this page (Teams and Show on the left, the three on the right) can be folded and moved, as the cards on the Notes page can. Press the arrow at the left of a card's header, or tab to it and press Enter or Space, to fold it; a folded card shows a one-line summary beside its title (for example Next: Today Staff meeting or 2 teams). Press the ••• at the right of the header for Expand or Collapse, and Move up or Move down, or hold Alt and press the up or down arrow on a card. A card moves only within its own column. When a card is already first or last, the page says so rather than doing nothing silently. Which cards are folded and in what order is remembered for you, on this page only. Every card starts open.
Hiding a side
Each side can be hidden on its own, or both, so the calendar has the room. Press the arrow at the top of a side (Hide the Teams and Show panels on the left, Hide the Coming up panels on the right). The arrow points at the edge the side folds into, and a narrow tab is left at that edge: press it to bring the side back, and the cursor lands on that side's hide arrow. The tab's name says how many teams are showing, for example Show the Teams and Show panels (2 teams), so a hidden Teams card does not hide which teams you are looking at. The same two choices are in Customize › Layout as Show the left panels and Show the right panels, and each follows the other with no refresh. Your choice is remembered for your account, on every device, and is not changed by switching team or choosing other teams. Below 1024 pixels wide the sides already stack under the calendar, so the arrows and tabs do not show there and both sides stay in view; the choice you made comes back when the window is wide again. Folded cards and their order are unchanged by hiding a side.
Adding an event
Press Add event in the row at the top of the page (or choose it from Actions), or choose Create → Event from any page in the product. The side panel opens straight into the form, with Cancel and Add event pinned at the bottom. It asks for:
- Name and the team it belongs to.
- Type — a meeting, a publication or a special event.
- Repeats — see below.
- Owner, who must be a person on the team; plus Time, Where and Notes, all optional.
- Placeholder, a checkbox for an event you are still working out.
- Links — up to five labeled references for the event: the deck, the runbook, a shared folder. Add link adds a row; the button counts them once you have one, and stops at five. Each row takes a label and an address, and each has its own controls to open it in a new tab, edit the address or remove it. This is the same Links field a task has, so it behaves the same way here.
Underneath the fields a plain-English sentence restates the rule as you build it — for example Second Tuesday of every month — so you can see whether you said what you meant before you save.
How an event repeats
| Repeats | What you choose |
|---|---|
| Does not repeat (one day) | One date. The event happens on that day only, once, and never repeats. Use it for a one-off such as a special event booked once in the year. It is listed as, for example, Once on Dec 12, 2026. |
| Weekly | The day of the week. |
| Every other week | The day of the week. Alternate weeks are counted the same way across the whole year, including over New Year. |
| Monthly | Which week of the month and which day, such as the second Tuesday or the last Friday. |
| Monthly on a date | A day of the month, such as the 15th. A month that does not have that day, such as the 31st in February, uses its last day. |
| Quarterly | Which month of the quarter, and the same day rule as monthly. |
| Specific dates | One or more date ranges. A range that runs for several days is a single occurrence, identified by its first day. |
Placeholders
A placeholder is an event with a name and a rhythm but nothing settled yet. A team that has no events is offered a set of editable placeholders to start from. They carry no dates and no people, so nothing in them is made up for you. Edit one to make it real, or delete the ones you do not need. The Show placeholders checkbox hides them from the views without removing them.
Opening an event
Press any occurrence to open its drawer. At the top, a picker lets you move between the occurrences of that event. The drawer shows the owner, time, location and notes, and lists the tasks added for the occurrence you are looking at. Show on Calendar takes you to that date in the Calendar view of Tasks. Events are not drawn on the Calendar itself.
Use Edit to change the event: the same panel turns into the form, with Cancel and Save pinned at the bottom, so there is no pop-up to dismiss. Use Delete to remove it. Delete event asks you to confirm first (the box reads Delete “the event’s name”?), and removes only the event: tasks you added for it are kept.
If you press Cancel, press Escape or close the panel with changes you have not saved, the bar asks Discard your changes? with Keep editing and Discard. Ctrl+Enter (Cmd+Enter on a Mac) saves.
Saving an edit updates the drawer you edited from straight away: its picker, its dates and its task lists follow the new rule without closing and reopening it. If the new rule no longer has the date you were on, the drawer moves to the event’s next date. A task linked to a date the event no longer has stays linked and stays in the drawer, under Other occurrences, marked Not a date of this event now; unlink it, or link it to a current date, whenever you like.
An event with links shows a Links heading in the drawer, read-only — it appears only when there is at least one, so an event without them is not given an empty section to explain.
Changing one date or all dates
When a repeating event is opened on one date, its form has a This date box with a Date field, to move only that date to another day, and Cancel this date. A new event, or one that does not repeat, never asks anything extra.
When you press Save after changing something a single date can have (a date move, a cancel, the Name, Time, Where or Notes), the bar asks Apply these changes to: Only that date, or All dates. Choose one and press Apply, or Back to return to the form. Some changes can only go one way, and the bar says why:
- Repeats (and its day, week or month), Team, Type, Owner, Links, Placeholder and Task assignee change every date, so Only that date is off (Repeats changes every date.).
- Moving or canceling a date changes that date only, so All dates is off (Moving a date changes that date only.).
- A date that has passed cannot be changed on its own (This date has passed.), unless you are moving it to today or later.
- One date cannot leave its Time, Where or Notes empty while the event has one. To clear it, choose All dates; the bar says so.
Choosing All dates first counts the dates from today on that had their own value, such as a different place, and says so (for example 2 dates from today on have their own place.). Applying saves the whole event and those dates follow it again; earlier dates keep what they had. If you change how the event repeats while some dates are moved or canceled, the bar shows the count and offers Save and clear.
A moved date appears on its new day everywhere: the year, the month, the List (marked Moved from its old date), Coming up and Event tasks, and the occurrence picker says (moved from …). Its tasks and its assignee move with it. A canceled date leaves the views and lists and stays in the picker marked (canceled); open it and press Restore this date to bring it back. A date is moved or canceled, never both, so canceling a moved date ends its move: restored, it comes back on its usual day, and the form and the message both say so.
Adding a task for an occurrence
Inside the drawer, Add task opens a small dialog with a title already filled in, such as Prep: Steering Co — Oct 13. Choose when it is due relative to the occurrence: on the day, 1 day, 3 days, 1 week or 2 weeks before, or 1 day after as a follow-up. Choose who it is assigned to. The task is created the same way as any other task, so it appears on Tasks and on the Calendar like the rest of your work.
The due date is the reminder. A task you add by hand is reminded about the way every task is, when it comes due. The one thing Events can do on its own is the optional automatic task described under An automatic task before each date.
Events appears quickly, and the has-task dots and the Event tasks card fill in a moment later. If you press Add task in the first second, the dialog shows it is waiting for your tasks to load (Loading your tasks…) and then continues.
There is one task per occurrence. To prepare for next month’s meeting too, open that occurrence and add its task. Adding tasks by hand never repeats; to have one made for you before every date, name a Task assignee (next section).
Every task listed against an event can be opened from here. Each task card — in the Event tasks card on the right and in the drawer’s own list — carries a small button, Open the full task, which opens it in its own editor over Events — a task that lives on a team board opens in the board’s editor, any other task in the task editor — so you never leave the page. Close it and the card shows what you changed. Open on the board or Open in Tasks at the top of that window goes to the full page when you want it.
The destination is either My tasks or Send to board…. Sending to a board uses the same Add to board picker you use elsewhere, and lists only the boards you are allowed to add to. The event a task belongs to is shown in the task’s own Board & Events field, but only to people who have Events access on that team; everyone else who can see the task sees an ordinary task. (The old From event line has been retired.)
An automatic task before each date
An event can name a Task assignee. It is optional, and an event without one behaves exactly as described above. It is separate from Owner: the owner stays the accountable person, and the Task assignee is the person who gets a preparation task before each date.
Setting it. In the event’s form, pick someone in Task assignee (or Nobody) to set it for all dates. In an occurrence’s drawer, the Task assignee row shows who it is for the date you are looking at, with Change… beside it. The dialog asks Which dates: Only this date, This date and after or All dates (an event that does not repeat offers no choice). Nobody turns the task off for the dates you choose, so one date can be switched off while the rest keep their assignee. A date that has passed cannot be changed.
Who can be chosen. People on the event’s team who also have Events access there; you can choose yourself. Once the event is saved, the picker lists only them, and says so when nobody qualifies; while you create an event it lists the team’s whole roster, and someone without Events access is refused when you save (the event itself is still saved). You can set it only if you have Events access on the team and are on its roster yourself.
When. The task is made five days before the date, at 8:00 AM in the assignee’s time zone, and appears within the hour after that. The assignee’s time zone is the one they chose for their clock; if they never chose one, it is the zone of whoever set them, and failing that UTC. If the date is already inside five days when you save, it is made straight away. A date that has passed never gets one.
What it is. A task titled like Prep: Steering Co — Oct 13, due on the event date and linked to that date, so it is listed with the occurrence’s tasks. It lands in the assignee’s My Tasks; you own it and hand it to them, and it is never a board task. The assignee is told in the Message Center and by email, according to their Assignments notification setting, even when you assign yourself.
Once per date. Each date gets its task once. If the task is later deleted, completed or unlinked, STRIDE does not make it again; for a deleted one the drawer says Task deleted. If, when the time comes, a task linked to that date is already assigned to that person (one made with Add task or linked to the event, by anyone), STRIDE uses it instead of making a second one and sends no notice.
Changing the assignee. A task already made moves to the new person only while it is open and still with the person STRIDE set; one that was passed on or completed is left alone. Choosing Nobody leaves existing tasks in place; it never deletes one. When a change would replace choices made for particular dates, or leave a task behind with someone else (one that was passed on or completed, or one that stays when you choose Nobody), a box titled Change the task assignee? says exactly what will happen before you confirm. In the panel’s dialog, a change that only moves open tasks to the new person is stated in the dialog itself; in the form, which has no such line, the box asks you about that too.
No task is made for a placeholder, a deleted event, or a team with Events switched off. Events are not on the phone; the task itself appears there like any other.
Linking a task you already have
You do not have to create a task from the event. In an occurrence’s drawer, press Link existing task…, beside Add task and Send to board…. A picker opens with two tabs, each with a count:
- Mine & watching — tasks you own and tasks you are watching, each marked Owned or Watching with the owner’s name. It opens on this tab.
- Team tasks — existing tasks on boards you belong to that are not already in the first tab. Linking one does not change its owner or its board.
Each row shows where the task lives and its due date. A task already linked to this occurrence is shown as Already linked here and cannot be chosen; one linked somewhere else says what it is linked to and that linking here moves it. Search covers the tab you are on, and an empty tab offers a button to the other when that one has a match. Open tasks come first, then completed ones, each marked Completed; archived tasks are not offered.
A task links to one event date at a time, and linking never changes its due date. To remove a link, press Unlink on the task’s card under the event and confirm; the task itself stays where it was. The same link can be made, changed or removed from the task itself — see linking a task to an event.
Putting several teams on one page
If you have Events access on more than one team, the Teams card in the left column lets you put them all on one page. Each team appears as a chip, and Add a team lists the other teams you can add — your own teams, and, if you own an organization, every team in it. Every event still belongs to exactly one team, so removing a team’s chip takes only that team’s events off your page. Your selection is remembered.
Who can see Events
Events uses a single right, the same way OKRs does: if you have access to a team’s Events you can see its events, add and change them, and add tasks for them. There is no separate view-only level.
- Team admins always have access, as do Super Team Admins and the organization’s owners.
- Anyone else has access when a team admin has given it to them by name, or to a group they belong to. Group access is live: someone who joins the group gains access, and someone who leaves it, or leaves the team, loses it.
- Nobody sees Events for a team that has not turned it on.
A team admin of a team that is on the page also finds Events access… under Actions, in Page settings. It opens Team Settings at the Events tab. Nobody else sees that row.
If you open the Events page directly without access, it tells you so and shows nothing about any event.
Turning Events on for a team
Team admins open Team Settings from the account menu. The switch is in two places, and they are the same switch: the first card on the Events tab, and the Events card on the Teams tab. Events is off by default. The Events entry appears in the navigation as soon as you switch it on, with no reload, including when Team Settings is open on top of another page. Turning it off hides Events from everyone and deletes nothing; turning it back on brings it all back.
The Events tab, shown to team admins only, holds Manage Events access…. It opens a dialog with a People tab and a Groups tab for choosing who has access, the same way OKR access is assigned. Admins are listed as always having access and cannot be removed.
What you will actually see
- No events yet. The page offers one action to add an event, and the placeholders to start from.
- Events switched off, or no access. A short explanation of which it is, and what to ask for. Nothing about any event is shown.
- On a phone. Events is not part of the phone view, which is for tasks. Tasks added for events show up there as ordinary tasks.