Team boards
Teamteam_board.html
New here?
This page covers everything. If you just want the core loop, read the two-minute version first.
Several people on one board at once
The navigation strip at the top of every page runs My Work · Tasks · Notes · Compose · Team · OKRs — My Work opens a menu of your own work (My team board, My OKRs and Help), and Team is this page. Below it, the view row is where the team switcher lives.
Your own open tabs stay in step. If you have this board open in more than one tab or window of the same browser, a task you create, edit, complete, move, archive, or put on or take off a board in one of them — here, on the Tasks page, or in the task editor — appears in the others within about a second. A tab only refreshes when it is showing a board the change touched. It waits while you have a task open, are typing, or are dragging a card, and catches up as soon as you stop.
A colleague's changes appear on their own when live editing is on. Live editing starts only when someone else has the same board open, and ends shortly after they leave. A board then shows a blue, glowing Live · 2 here label at the start of the buttons on the right of the header, with the avatars of the people looking at it. While you are the only one there it reads Live editing ready in plain gray. If others are on the board but your browser cannot open the live connection (a company network or a browser extension can block it), the label turns amber and reads Live editing can’t connect. Your changes still save, the board keeps refreshing when you come back to the tab, and it keeps trying to connect while the others are there; press the label to try again now. Reloading or another network may help. A card a colleague moves, adds or archives slides to its new place, pulses once and carries a name tag (Raj moved this) for a few seconds. Your scroll position, filters, sort and folded lanes stay as they are, and changes made outside the board, such as on the Tasks page or by email, appear within about a minute. All boards is not live.
An update never interrupts you. A colleague's edit to a card — its title, description, due date, owner or assignee — shows on the card straight away, even while you have a task or menu open. A card they moved waits: while you drag a card, have a task or menu open, or are typing in the board, the move applies when you stop. Typing in the search box at the top does not hold anything back. A task you have open takes their change too, unless you have an unsaved edit or are typing in it. The first save wins. If a colleague moved the card you were moving, your move is not saved, a message says who changed it, and the board shows their version. Press the label to see why live editing is off. While it is off, a colleague's changes appear when you press Refresh, or when you come back to the tab. While the label reads Live, coming back to the tab does not refresh the board as well: live updates already keep it current. If the connection drops or live editing turns off, the refresh when you come back starts again straight away.
If somebody saves a task while you have the same one open, your save is refused rather than silently overwriting theirs. Nothing of theirs is lost and nothing of yours is saved; the board reloads to show their version so you can check it and reapply anything still needed.
Teams, boards and who sees what
Three things stack up, and getting them straight makes everything else obvious:
| Team | A group of people. It owns boards, and it is where you invite colleagues. You can belong to more than one. |
|---|---|
| Board | One kanban board inside a team, with its own columns, topics, tags and its own list of who can open it. |
| Group | Optional. A named set of people — Engineering, Leadership — that can be given board access in one go. |
Being on a team does not give you every board
Board access is always explicit: you see a board because someone added you to it, or a group you belong to. A brand-new board is visible only to its creator until they add somebody — a board can hold sensitive work without leaving the team.
The Team tab appears when you can open a board
If you have not been added to any board, the tab is not shown. A team administrator or an organization owner can add you to a board, and the tab appears the next time the page checks. Administrators always see it, including before their team has any boards, because that is where the first one is created. If you are already standing on the team board when your access changes, the tab stays where it is rather than vanishing under you.
The board, top to bottom. The navigation strip runs My Work · Tasks · Notes · Compose · Team · OKRs — My Work opens a menu of your own work (My team board, My OKRs and Help), and the Calendar is one press away on Tasks. Under it is the view row, which is where the team switcher lives, with the four views and their counts; then the Focus strip, Team at a glance. On a narrower window the navigation drops its words and keeps its icons, so the strip you see may be shorter than the one drawn here.
Search everything
Search everything, in the navigation strip on every page (⌘K or Ctrl+K from anywhere), looks at your tasks and notes, the teams and boards you belong to, the people on your teams, and the objectives and key results you can see — typing at least two characters opens a dropdown grouped by kind. A toggle beside the box switches between Global and searching only the page you are standing on, where that page offers its own narrower search. The toggle stays at every window width; on a narrow window (about 700 pixels wide or less) it sits on its own line just above the box.
Every search box has a clear button. While a search field holds text, a round × appears at its right end; press it (or Tab to it and press Enter) to empty the field in one step — the list or results reset exactly as if you had deleted the text, and the cursor stays in the box. This works the same in the navigation strip, on every page search, in the Admin Console and in the pickers.
An objective or key result also matches on who owns it, not only its title, so typing a colleague's name finds everything they own. A hit found this way shows the owner's name on the result row, so it is clear why it is there.
Choosing a task from the results opens it wherever it actually lives — switching to the Watching tab for a task you are only watching, say — the app makes that switch for you and says so at the bottom of the work area (centered at the bottom of the screen on a narrow one), with about six seconds to Undo it.
Your first Organization and team
If you do not belong to an Organization yet, the team board shows one card, Create an Organization, with the setup order underneath it: Organization → Team → Board → People → Groups → Swimlanes. Tasks and Notes work without one; only the team features wait for it.
What a brand-new account sees on the team board. If you were invited, you do not need this: accept the invitation and you join that Organization instead.
- Press Create organization on the card. A dialog opens.
- Type the Organization name and the First team name (name the team for the group that will use the board), then press Create organization. You become the Organization owner and a Super Team Admin.
- The card becomes Your team workspace is ready. Your Organization and first team exist, but no board yet: press Open organization settings, then create your first board in Team settings → Boards.
- Invite colleagues at the top of People, then give them the board from their own row.
Not sure where to start? Not sure? Ask STRIDE under the button asks about creating an Organization.
It opens on the tab that matches where you opened it from. From Tasks, Calendar, Notes or the team board it starts on Teams; from the OKRs page it starts on OKRs, because that is almost always what you went looking for. Every tab is still there and one click away — this changes which one you land on, not what you can reach.
The team switcher sits in the view row under the navigation strip, not in the navigation itself. Changing team changes which boards are listed. With only one team there is nothing to choose between, so it simply names the team you are in.
Your teams, and switching between them
The team dropdown in the view row, just left of the board dropdown, shows which team you are in and switches between them. Switching changes which boards are listed, so the app moves to the board you were last on in that team — or its first board, if you have not opened one there yet. A new team is started from Team settings → Team, not from the dropdown — name it and press Create team. The Team tab there is the fuller view: every team you belong to, your role in each, a Switch to button, and what the current team contains.
The board you last opened is remembered, for each team separately, so signing in again opens it rather than making you pick it every time. Only choosing a board records it; a link that names a board still wins; and if the remembered board has been deleted, archived, or you have lost access to it, the app opens the first board you can see instead rather than an error.
The Team tab, with the whole strip beside it. Everyone sees Team, Preferences and View. Which of the rest you see depends on your role — see the surprises above and the table itself.
A new team starts empty
You become its first team administrator, with no boards yet — create one on the Boards tab, then add people to its roster. Nothing moves across from your other teams.
Deleting a team
At the bottom of the Team tab, a Delete this team row offers to remove it for good. A team administrator sees it; so does an Organization Owner for any team in their own Organization. The same action is also on the Admin Console's Teams and Boards section.
An empty team goes straight away. If it holds no boards, people, groups or objectives, pressing Delete team… removes it with no further confirmation.
A team that still holds anything can also be deleted, all at once — and that can include accounts
When the plain delete refuses because the team still holds boards, people, groups or objectives, the dialog offers Delete everything in it — the team, its boards and tasks, its objectives, key results and check-ins, its groups and whole roster, counted for you by kind. This cannot be undone.
One choice must be read before confirming: Keep the people's accounts, ticked by default. Ticked, everyone keeps their account and only loses their seat on this team. Unticked, anyone whose only team and only Organization membership is this one has their account deleted outright — every task, note and tag of theirs — while anyone belonging elsewhere is never touched beyond losing this seat; the dialog names how many of each.
It refuses if anyone on the roster is a peer Organization Owner, or if deleting this team's accounts would leave the Organization with no other team — remove that person first, tick Keep the people's accounts, or ask a System Administrator.
Either way, history is not destroyed: activity, email and purge records that pointed at this team keep their content and simply lose the team label.
Prefer Inactivate when you only want the team out of the way — it closes the team to its members, keeps everything, and can be undone later. Delete cannot.
Team roles
There are three roles in a team.
- Member — works on the boards they have been given.
- Team admin — runs the team: people, groups, topics, swimlanes, tags, and every board the team already has. Creating a new board is not theirs.
- Super Team Admin — everything a team admin does, plus six things that are deliberately rare.
Those six are creating a team, creating a board, configuring the team's email, importing a file of OKRs into the team, sending the team's invitations, and making somebody else a Super Team Admin. Administering one team is not by itself a reason to be able to create another.
“Running an import” is three different jobs, and only one of them is on that list. Importing a file of OKRs is the Super Team Admin one, refused below that role by the database. A file of tasks onto a board is not: whoever administers the board can do it — a team admin, Super Team Admin or Organization Owner on any board in their team, or a member made that board’s admin. Nor is importing people: it is adding people in bulk, so a team admin who can add one person can import fifty; its invitation emails go out only when the importer may send the team’s invitations, the separate, Super Team Admin act.
A team admin keeps everything else. They can still see the team's email settings, so they can explain why somebody was emailed; they just cannot change them. Trying anyway saves nothing and the pane answers plainly — “Only a team admin can change these.” A team admin cannot promote anybody to Super Team Admin, themselves included — only an existing Super Team Admin, or your Organization's owner, can hand it out.
Your first team is the exception to all of this. Anyone with no team at all can create one and becomes its Super Team Admin. Once you are in a team, creating another needs the role.
A team’s last Super Team Admin cannot step down or be removed — unless the Organization has an Owner to fall back on. Without one the team would be left with nobody able to change its email, import into it, or appoint a replacement. Where the Organization has an active Owner, that Owner is the backstop and the removal is allowed, so expect the Owner to pick the team up.
Super Team Admin is not the same as System Admin. A System Admin administers one whole organization from the admin console, and God Mode reaches the whole application; Super Team Admin only applies to the teams you are in.
Resetting somebody's password
A person's … menu in People also carries Reset password — the identical control in Organization People, and the admin console has an equivalent (a System Admin for their own organization’s people, God Mode for any account); see People in the administrator manual. Not offered on your own row.
Use this when email is not reaching them. The ordinary way back into a locked-out account is Forgot password? on the sign-in page, since that route never puts a password through you at all. Reset here only when that has failed, typically because the address on file cannot receive mail.
Confirming is immediate and has no undo: their current password stops working at once and they are signed out everywhere — every device, not only this team. You are given a one-off generated password, shown once on screen, to pass on outside the product. They must set a new one the next time they sign in.
Permissions by role: looking the answer up in the app
The exact answer — every capability, against all four roles, in one table — is inside the application, called Permissions by role. Open it while deciding what to give somebody. It describes what the system actually enforces rather than what a role’s name suggests: each row says who can do the thing and in what circumstances.
It opens from one place: the Permissions by role button in the header of the People pane, with nobody picked first.
Opening it costs you nothing you were in the middle of. It is a reference rather than a control — it reads, saves and grants nothing, and what you had ticked elsewhere is unchanged when you close it. Esc closes the table and leaves the dialog underneath standing. It is the same table for everybody, with no highlighted column, so you can look at it on somebody else’s behalf.
How to read it
Four columns. Member, Team admin and Super Team Admin are the team ladder, building on each other. Organization Owner is set apart on purpose: a role over the whole Organization, not a fourth rung on that ladder.
Four answers, each written out in words as well as drawn:
- Allowed — yes, for that role, always.
- Allowed in some cases — yes, but only in a stated one, and the case is written under the capability itself rather than hidden in a footnote.
- Not allowed — no.
- Not decided by role — something other than a role decides. Being added to a task as a collaborator is the example: granted per task, no role here gives or takes it.
Rows are grouped by how the decision breaks down — their own work, running a team they already have, changing the shape of things, and running the Organization. A short list at the foot says what the four columns leave out, including that administering a single board needs no team role at all.
Choosing which role to give somebody
Choose the lowest role that gives them what they need. Each step up adds acts that are hard to undo rather than merely useful. Roles are per team: somebody can be a Super Team Admin in the team they run and an ordinary Member in the other two.
Four that catch people out
- A team admin already sees everybody in the Organization — the whole roster, not only their own team’s part of it. Deliberate, not something you grant separately.
- But seeing everybody and assigning them are two different permissions. Moving people between teams, boards and groups across the Organization — and the license count — is the Organization Owner’s, and nobody else’s.
- Owning the Organization does not put you on its boards. An Organization Owner works on a board only by holding a place on it, like anybody else.
- Closing the Organization is not a flat yes even for its Owner. An Owner can delete one that is already empty; closing one that still has people in it needs God Mode as well — and the refusal arrives after you type the Organization’s name.
The fifth is the import split: importing a file of OKRs is a Super Team Admin’s, while importing tasks onto a board is the board administrator’s and importing people is a team admin’s.
Topics, Swimlanes, Tags and Bulk Import need either an administrator of that specific board or a team administrator — so a team administrator sees these four on every board in the team, not only the ones where they separately hold that board's own admin row.
If this page and the table ever disagree, the table is right
This page deliberately does not copy the grid out — a second copy is a second thing to keep true. The table is kept next to the code it describes, so it is the more likely of the two to be right, but it is written by people and can still be wrong. If the two disagree, go with the table and tell us.
People, groups and boards
This dialog is Team Settings. Once you belong to a named Organization, it retitles itself to your Organization's own name with eyebrow ORGANIZATION SETTINGS — same tabs, same doors in. This manual keeps saying “Team settings” since that is the name most readers see. See the Organization logo for the one place this matters day to day.
There are two ways in, both in the account menu under your initials. Board settings… opens it on the Boards tab with the board you are reading already picked out. Team Settings opens the same dialog on its Team tab. The board has no settings button in its strip; its Actions menu in the view row lists Board settings… too. Team administrators also see a direct link to each of the six tabs below, under Board settings… (in either menu), and get six extra tabs, in order: Groups, Boards, OKRs (a separate, smaller list of who may open the team's objectives and key results; see OKR access below), People, Email, and Bulk Import (one door onto the Import dialog, for tasks or for people).
People. Inviting is at the top, because it is where the flow starts; each row then says which boards and which groups that person has.
The roster, the role chip and a person's detail
The role chip changes a role. Each row has a chip for the person’s role on the team shown; the column header names that team (Role on the team), and the Team filter picks which team it is. Press the chip to choose another role. A chip can also read Not on this team — press it for Add as…, where you may add people — Inactive, or — for a team you cannot see. The Role filter asks about the role on that same team.
Press ⌄ or the name for the row’s detail. It holds Teams (a role chip for each team, and Remove from team on the open team), Boards and groups, and Account (Reset password, the invitation, Inactivate/Reactivate, and Remove). A person on no team reads Not on any team in this organization yet.; while the teams, boards and groups load it says Loading teams, boards and groups…, and a team with only you on it says Nobody else is on this team yet. Invite someone above.
Inviting somebody
Invite people by email address, at the top of the People tab — type one address, or several separated by commas, semicolons or line breaks, choose the Role, and press Invite. An Organization Owner also sees Invite to: This team or Organization only; Organization only invites to the organization with no team and no Role. Somebody invited from another organization joins as Member when they accept. Bulk import…, in the same card, opens the Import dialog on this team's roster with A list of people chosen (team administrators). Adding one person emails them their invitation as the row is saved, with no second step. An invalid address, or one already on this team, is skipped rather than holding up the rest; the status line names who was skipped and why, and for everybody who goes through it says which of three things happened: added and emailed, added with email switched off system-wide, or added but the message could not send right now (try again from Email invitations). In all three they are genuinely on the team — only the message is ever in doubt. Changing team or organization clears the box.
Until they create an account they are listed with no account yet — still genuinely on the team; when they register with that address the two connect on their own. Your team's own email switch does not apply to this — only the application-wide one, held by a God Mode holder, stops invitations. If somebody has signed up and still shows as waiting, check the address: people are matched by email, so a personal address instead of the invited work one leaves them looking unregistered — remove the invitation and re-add the address they actually used.
What the invitation looks like when it arrives. It comes from your team's name, headed by the team's own uploaded picture rather than this product's name, so a reader recognizes who is asking. A team that has not uploaded a mark simply gets no picture, and the message reads correctly without one. The sending address is unchanged.
There is no code in it. An invitation is a message rather than a credential: it carries a link that already knows the address you invited them at, opening the sign-in page's create-account tab with that address filled in — which stops somebody registering with a different address and landing outside the team. Nothing in it expires, so an invitation that sits unread for a fortnight still works. Re-send freely.
What does have a deadline is the six-digit code they are emailed after creating the account, to prove the address is theirs. That one lasts an hour and it is entirely between them and their inbox — you cannot see, send or reset it. Somebody stuck there shows on your roster exactly like somebody who has not registered at all; see Verifying your email address.
Once your Organization is named: a pending row gains two more actions
People moves to the Organization level — one roster covering every team — and a pending row for somebody who has not yet accepted their invitation shows three actions instead of one: Resend, Correct email…, and Revoke. Correct email… is for a mistyped address: it shows the address currently invited, you type the right one, and pressing Correct and resend keeps the same invitation and sends it to the corrected address — no separate revoke-then-reinvite. These disappear once the invitation is no longer pending.
An ordinary Member never sees this pane at all, once Organization People exists. Organization Owners, Team admins and Super Team Admins still see it.
The status filter at the top of the roster — Active, Inactive, or Pending — is the quickest way to see everyone still waiting on a sign-up, so you can decide for each one whether to Resend, Correct email, or Revoke.
Once Organization People exists, you can also grant access to several people at once. Tick the checkbox on each row — the header checkbox ticks or unticks everyone matching the current filter, across every page — and a selection bar appears. An Organization Owner gets Add to [team] as [role] · Boards · Groups · Apply: it grants all of it in a single press, from anywhere in your Organization. It only ever adds access, never removes it, and never lowers a role. A person with no account yet is still granted boards by their invited address, but is skipped for groups — which need an account — and the composer says so. A team admin gets Add to boards…, pre-filled with the selection; people not on the open team are left out, and the dialog says how many. While it works out what you may do with the selection the bar reads Checking what you may do with them…. Beside them is a destructive button, Remove pending…, which revokes every selected invitation still pending — it is disabled, with a reason on hover, unless your selection is all pending people and you are an Organization Owner.
Seeing who has stopped signing in
The Dormant filter beside Status narrows the roster to people with no sign-in for 30, 60, 90 or 180 days (the choices read No sign-in, 30 days and so on), and anyone who has never signed in — including an invitation nobody has accepted yet. While it is on, each person's row shows Last sign-in: and the date, or Never. A Team admin sees the dates of people on the teams they administer (the roster still lists everybody in the organization; the others simply never show as dormant); an Organization Owner sees everybody's. It only shows — deleting an account is a God Mode holder's job in the Admin Console. If the dates cannot be read, the filter is dimmed with the reason on hover.
Making someone inactive
A row's … menu offers Make inactive, applying across every team in this organization, not one at a time. They keep their history, but drop out of owner/assignee pickers and people filters. Reactivate undoes it the same way, everywhere at once.
If the person owns any objectives or key results, you are asked whether to reassign that ownership to someone else — one new owner, picked from active members of every affected team — or press Skip, just deactivate and leave ownership pointing at the now-inactive person, just no longer pickable for new work.
Emailing the invitation — and telling a board it has a new member
Adding somebody already emails them. This button is for the batch — people added before that existed, failed sends, and anybody on a board who needs telling. It sits at the top of People, labeled Email invitations (3) (counting who is stuck) or with no count if nobody on the team is waiting — the button still works: a board may have people to tell even when the team has nobody left to invite. Email board invitations is what you see if your authority is over a board rather than the whole team.
Emailing the whole team needs a Super Team Admin (or your Organization's owner) — the database refuses the send regardless of how the request is made. Emailing one board's roster only needs authority over that board — a board administrator can always mail the board they administer.
Pressing it opens Email invitations:
- Choose who first — the Invite dropdown: Everybody on this team, or People on a named board, with a count beside each.
- Then tick the people. On the whole team, everybody starts ticked. On a board, only people who have never registered start ticked — twenty colleagues with months of access is an email nobody can un-send. At most 50 in one send — a larger selection is refused with the number named rather than quietly trimmed; one send per team per minute, a board counted separately.
- Also send a copy to me gives you the real message, not a preview of it.
- The result is per person, not a total — sent, or skipped with a reason (registered since, duplicate address, no usable address, provider unreachable). Nothing is refused as a whole because part of it could not go.
Choosing a board changes who is emailed and what they are told — a registered colleague is sent a link straight to the board rather than to the sign-up page; somebody with no account is invited to create one, with the board named in its first line. Nobody who is not ticked is emailed. You still cannot invite an outside address straight onto a board — only the Boards dropdown on somebody's row in People, which only lists people already on the team.
If it says application email is switched off, nothing was sent — a God Mode holder turns it back on in the admin console's Application email switch.
Adding several people from a spreadsheet
Bulk import… in the People tab's invite card (or Bulk Import → Import a file…, choosing A list of people)
opens the Import dialog on this team's roster. It needs no AI. Choose the file (.csv, .xlsx or .xls), check
Columns (only Email address is required; Role, Groups and Boards are optional), read the
Review and press Import. Nothing is written until you do.
The review says what will happen to each row. New people are added with the role in the file, or Member when it has none. Somebody already on the team is Will update only when the file raises their role, or adds a group or a board — a role is never lowered, a name is never changed, nobody is removed, and a group or board the team does not have is listed and never created. An Organization Owner is never changed, and somebody switched off on this team is not switched back on here (turn them on in People). A role above what you may grant is not applied and says so. Somebody from another organization is added only by an Organization Owner, as an invitation to the organization.
The review also shows who will be emailed, before you press Import: invitations to people with no account yet, organization invitations, people who are told in STRIDE with no email, and people who are not emailed and why. Email them when I press Import is a switch, on by default, and it is shown only to a Super Team Admin: a team admin adds the people and a Super Team Admin sends the invitations. An invitation email cannot be recalled, so Undo (on the last screen and in Import history, for 30 days) removes an invitation nobody has claimed and puts back a role the run raised, and keeps and names anybody who has signed in since and anything changed since the run; it says how many emails had already gone. If an invitation email cannot be sent, the last screen says so in an amber note beneath Imported, not as part of the success: the people were still added, and Email invitations on People tries again.
Read the result carefully, because a run can half-succeed. The report counts four things: Imported (on the team now), Skipped as duplicates (already on the team), Not imported (rows this page never attempted because something was wrong — fix the spreadsheet and import again), and Refused by the database (rows that were attempted and turned down — a permission or constraint, not your file that is wrong, shown in the database's own words).
A run with any refusals is reported as a failure, not a success, even when some rows went in — the closing line names both halves. The people who were added really were added; only the refused rows are still outstanding, so re-importing the whole file again is the wrong move.
Giving somebody access
Each person's row carries two dropdowns: Boards and Groups. Open one, tick what applies, and close it — changes save as you tick. Closed, each names what is chosen.
- Boards gives one person access to one board. The star beside a board makes them an administrator of it.
- Groups is usually the better answer — give the group access and everyone in it gets in, including anyone added later. It also stays right when a new board is added later.
- A board reached through a group is ticked but locked — remove them from the group, or the group from the board.
- The Boards count on the People list, and the Boards list in the Admin Console's account detail, include boards reached through a group. The account detail says which: member via group …, or also via group … beside a board they are on directly.
Being on the team on its own grants nothing. Access comes from a board, or a group that has one.
OKR access — a separate list from boards
A team has boards, plural, so board access is a person-by-person and group-by-group choice. A team has one OKR space, so who may open it is a single list, kept on its own OKRs tab in Team settings, between Events and Topics — not another dropdown on the People row. The first card on that tab is the switch that turns OKRs on for the team (the same switch as the Objectives and key results card on the Teams tab), so you can turn OKRs on and choose who has access in one place.
The Health thresholds card on the same tab sets where the OKR colors fall for the whole team: Ahead, On track, Slightly behind and Behind. Only Team admins move its handles, and Reset to defaults returns the team to the product’s own bands. Everyone else on the team sees the same scale, read-only, in their OKR Settings.
Team membership alone does not grant OKR access
Team membership does not automatically grant OKR access. Team Admins have administrative access. Other Team members must be explicitly granted access through Team Settings → OKRs.
New OKR access defaults to deny for normal Team members until explicitly assigned. The first time you open this tab, the list of people with explicit access starts empty — nothing is broken; select who should have access and press Save.
Pressing Manage OKR access… opens the picker: a search box, Select all/Deselect all (acting on whatever the search shows), and Select new members, which ticks everyone eligible who does not have access yet without touching who is already ticked.
Unlike the board and group pickers, this list is reconciling, not only adding. It opens with everyone who currently has access already ticked, so unticking somebody and pressing Save removes their access — this tab is the only place OKR access is granted. Team Admins are shown, ticked, and labeled Access via Team Admin role — their row cannot be unticked, since they already administer every OKR in the team.
You can select somebody who has not signed in yet — tagged has not signed in yet; the grant activates the moment they sign in.
Anyone not selected does not see OKRs in their navigation for this team, even if OKRs are switched on for the team as a whole — the team switch and this list answer two different questions, managed separately for each team. See the OKRs page's own explanation.
Events access — the same picker, with groups
Events is switched on per team, exactly like OKRs. In Team Settings, the switch (off by default) is the first card on the Events tab — shown to team admins only — and also a card on the Teams tab; they are one switch, and flipping either moves both. Turning it off hides Events from everyone and deletes nothing — turn it back on and it is all still there. Below it, the Events tab holds Manage Events access…. Once Events is on for the team, the Open Events link beside it goes to the Events page. The manual for the page itself is Events.
The picker has a People tab and a Groups tab. Tick everybody who should have Events access for this Team, then Save. On the Groups tab, tick the groups whose members should have Events access for this Team; a group’s count shows in its tab (Groups (n)), and a team with none says This Team has no groups yet. Group access is live: the people in the group have access while they are in it and on the team.
- Team admins always have access. They are listed as such, ticked, and cannot be unticked or written to the list.
- It works while Events is off. You can set up who has access before you switch the team on; nobody sees Events until you do.
- If the list cannot be read, the card says Could not check access, and the picker says Could not load who currently has Events access with the reason. Nothing has changed; try again.
Finding the right people
The Show filter at the top narrows the list to one or more groups. It opens on All groups every time, showing everyone, including people in no group at all. Ticking several groups shows anybody in any of them.
- People — invite, promote to team admin, give board and group access, remove. Deciding which role to hand somebody: see Permissions by role, opened from a person's own row.
- Groups — create a group, then fill it. Find someone at the top of the editor: click it to browse, or start typing a name or email and the list narrows, offering only people not already in the group. Select all puts everyone with an account in at once. Remove everyone asks first and leaves an Undo removal button beside the list.
- Boards — rename and delete boards, and grant group access to them. Creating one needs a Super Team Admin; everything else is an ordinary team admin's.
Somebody is missing from the group list
A person can only be ticked into a group once they have registered an account — group access is held against the account, not the invitation. Anyone still waiting is listed grayed out, marked no account yet, and becomes tickable as soon as they register.
Four tabs configure the board you are looking at rather than the team: Topics, Swimlanes, Tags and Import. Each starts with a Board selector saying which board it is editing.
There is no separate Roster tab. Who can open a board is granted from People — a person's own row, or a group that has the board — and read back from Who is on this board in the view row, which also says who administers it. Preferences is available to everyone — it holds your own display choices and affects nobody else: what an exported report includes. (The Links section switch on tasks is in My settings → Tasks.) View is yours too, and holds how this page presents the board to you.
Ask STRIDE is in the header of Team settings, before the close button, on every tab. It opens the panel beside the window, which stays open. On a wide screen the panel is a full-height strip on the right and the window moves left to make room; on a narrower screen the window gets narrower instead. When you close Ask STRIDE the window goes back to its own size and place. It is set to the tab you are on: a chip such as Team settings › People says so, and × on it clears the scope. Its starter questions are written for that tab. It sends only the name of the tab, never what is set in it, and you can still ask about anything. On the Organization, Teams, Boards, People, Groups and Swimlanes tabs, a new Organization owner who has no AI key yet can still ask setup questions when a God Mode holder has switched on starter help: each question passes a quick security check and is answered from STRIDE’s own help, with no steps or tours; the panel says so. What it sends is in the Account help.
Where the board's controls are
Under the navigation strip is the view row, one line wherever the window is wide enough: the Team and Board pickers, the four tabs (Board, Owned, Completed, Archived, each with an icon and its own count), who else is on the board right now, the who is on this board button, Actions and, last, an icon-only Customize. The team switcher is in that row, not in the navigation above it. How the board is laid out is in Customize — press the Customize button (the sliders icon) at the right end of the view row or V, or choose Customize… from the Utilities rail’s ••• menu (see Customize: how the board looks). Actions holds Add task, New topic…, Follow this board, Export this board…, Clone board… (for whoever may create a board, see Cloning a board or a topic), Import…, Board settings… and, for team administrators, the six admin links; the same list is in the menu under your initials.
Under the view row is one strip, the same one Tasks has, folded by default. It carries the board's figures as chips (Total tasks, Complete, Open tasks, Overdue, Due this week), Mine as a quick chip, then the board's tools: Add task with a New topic… chevron, Organize, Filters, Clear (once something is filtered) and the fold-all button. The figures are filters: pressing one narrows the board. The chevron at the strip's left drops down the breakdown — Tasks by status, Tasks by tag and By assignee — and shuts it again.
Every control names itself when you point at it, and to a screen reader. The four tabs are Board views; the Complete figure reads Open the Completed view; the Add task chevron opens a menu named Add to this board, whose New topic… reads Add or manage this board's topics; and the Filters menu ends with Clear all filters.
Organize says what the board is doing (Grouped by topic · Smart) and opens Customize at its Organize section, where Group this board by topic and Sort cards by are set.
One button folds every topic band, and it says what the next press will do. While every band is open the button is lit and reads Collapse all topics. Press it and it turns off and reads Expand all topics. Fold a single band by hand and it turns off as well, because not everything is open any more — so the next press opens the rest rather than shutting the ones you left. On Owned, Completed and Archived it reads sections instead of topics. It is not drawn at all when there is nothing to fold: with Group by Topic off, the board is one row of lanes and has no bands.
Tasks by tag shows a single row; +NN more opens the rest in place.
The strip's tools, to the right of the figures. The fold-all button is drawn here as a fresh board draws it — off, offering Expand all topics, because a new board keeps its empty No topic band folded.
The people list: who still has work, and how far along
The people icon beside the Board selector opens the board's people list. On the Board tab it answers one question — who still has work to finish?
- People with work that is not complete, or whose only remaining work is on hold, are listed. Finish everything — with nothing left on hold — and you drop off the list; someone whose sole remainder is on hold stays, with their row saying so. It is a list of what is outstanding, not a list of who is on the team.
- Least complete first. Somebody at 0% is at the top. Where two people are at the same percentage, the one with more still to do comes first.
- Each name carries its figures — 3/5 for cards done out of cards held, then the percent.
- Picking a name filters the board to that person. Anyone picked stays on the list even at 100%.
The other tabs still list everybody. On Owned, Completed and Archived the list is the full board membership. Unassigned is not on this list — it is a pile rather than a person, shown in the By assignee column of the strip’s breakdown.
Work that is On Hold does not count toward anyone’s total or percent. A task in the On Hold lane is neither open nor done, so it is left out of the people list, the By assignee cards, and the board's export — if somebody reads 3 of 5 done · 60%, none of those five is on hold.
Somebody whose only remaining work is on hold still has a card — it is not the same as having nothing. Instead of a percent it reads N on hold. Somebody with a mix keeps normal N of M done · P% with · Q on hold added beside it. Only somebody carrying genuinely nothing — no open, done or on-hold work at all — has no card.
The On Hold lane's own count, and the Tasks by status breakdown, are unchanged — those answer a different question, and hiding a status from a breakdown of statuses would simply be wrong. Blocked and Monitor still count as open.
See topics on the board
Each topic is a band of lanes, with a colored rail and dot in the topic's own color, so a topic is easy to find by eye. Its header says how much is left: 6 open · 3 done, and a slim meter fills as the done share grows. A topic that is ready to archive is the one with no open cards left.
The Topics strip under the board's strip gives one chip per topic with its open count, and No topic for tasks not filed under one. It is on by default. Hide it and show it again with Show the topic strip in Customize's Layout section (there is no separate button for it); the switch works on the Board view of a single board that has topics, and says so otherwise. A chip writes the same selection as the Filter menu's Topic section, so a chip and the menu never disagree. With Group by Topic off, each card carries a small topic chip instead, because the band is no longer there to say it.
A topic only has a band while it holds live work. Once every card on it is archived, the band goes, and the topic stays in the topic picker for new tasks. Filing a new task under it brings the band back, so live work is never hidden.
Sort: putting the cards in the order you want
Sort cards by (every board) is in Customize at its Organize section, which the strip's Organize link opens (it says the order in force, such as Grouped by topic · Smart). It orders the cards in every lane, under every topic, at once. It offers the same four orders as the task list:
- Smart — starred cards first, then by due date, undated last. The default.
- Due date — the calendar order, ignoring the star; undated last.
- Title — alphabetical.
- Newest — most recently created first.
The order is remembered, on every board and session, and is separate from the task list's own sort.
Always compact
The board is always compact: short cards, so more of each lane is on screen. A card shows its title, assignee, due date and a one-line description; open the card for the full description and everything else. There is no Comfy view and no switch.
Every lane is the same width however many cards it holds; use Lane width in Customize for Fit or Fixed.
Customize: how the board looks
Customize (the icon-only button at the right end of the view row, V when you are not typing, or Customize… on the Utilities rail’s ••• menu) opens one panel with every view choice, in the same order on every page; each row says how it is kept (Saved follows your account). Layout: Lane width (Fit to screen or Fixed width), Keep the bands in view while scrolling, Show the topic strip, Show Team at a glance, Show By assignee. Organize: Group this board by topic (this board only) and Sort cards by (every board), the strip’s Organize link opens this section. Display holds Theme and app font… and All settings…. Defaults: A board you have not arranged opens on and Group a new board by topic (also in Board settings… › View). Utilities is the side panel of cards and widgets. The board’s actions — Export this board…, Task import…, Board settings… and the admin links — are not view choices, so they live in Actions and the menu under your initials. The general guide to the panel, its sections and its tags is in Customize: every view option in one panel.
Pinning the bands, or letting the page scroll
Above the board sit the view row and the strip. Normally they stay put while the board scrolls underneath them.
Keep the bands in view while scrolling turns that off and on. It is a switch in Customize's Layout section (see Customize: how the board looks); there is no pin button on the bar.
Unpinned, the bands scroll away and the lanes get the whole page; pinned, they stay. The choice is saved to your account. Unpinning does not remove the bands, it just stops holding them on screen — scroll back to the top and they are there.
Adding work to a lane
+ Add task at the foot of any lane opens a line right there. Type a title and press Enter — the task lands in that lane, under that topic, owned by you — and the line stays open for the next one. Esc closes it. More… opens the full form with what you typed already in it; it is the same task in your own list too, not a copy.
A new card appears straight away, and says so while it is being saved. Whether you press Enter here or Create task in the full form, the card is on the board at once and carries a small Saving… label until the save is confirmed. On a slow connection the label reads Still saving…, and a message says so too — keep the page open until it goes. If the card sorts below a lane's card limit, the lane opens out so you can see it.
If a save cannot be completed, the card is taken back off the board and a message says why. Nothing you typed is lost: the form reopens with it, or the title goes back into the lane's line, so you can try again. If the connection simply stopped answering, saving again is safe — the task will not be created twice.
Moving a task without dragging
Every card you can edit carries its lane as a chip at the bottom of the card. Pressing it opens a short Move to lane menu; pick a lane and the task moves exactly as dragging it does — useful on a touch screen or without a mouse. From the keyboard, press m on a focused card to open the same menu. The lane the task is already in is ticked and cannot be chosen.
The lane that finishes work is marked · completes in that list: move a task there and it is complete, in your own list too, dated the day it was done. That mark comes from how the lane is configured, not its name — a lane merely named “Complete” that was never set up that way does not count. Reopening the task restores the date it had before.
On a card you can only read, the lane is shown as plain text. If a task is sitting in a lane that has since been renamed away, the chip says so and still offers every live lane.
Merging two cards. Drag a card over the middle of another and hold for about a second: the target says Release to merge, and letting go asks Merge these two tasks?. The same menu and the m key also carry Merge with…, which opens a picker for the keyboard. One task keeps going and the other is completed and linked, never deleted. A card dropped on empty lane space still moves to that lane, and cards from different boards (in All boards) cannot be merged. The whole rule, the undo and what comes across are in Merge two tasks.
Finding your own work on a board
Mine, a quick chip in the strip, shows only work whose next action is yours — tasks assigned to you, plus tasks you own that nobody is assigned to. Press it again to see everybody's. It is the same filter as clicking your own card in By assignee (in the breakdown), and combines with a topic or date range if you have one set.
That differs from the Owned tasks tab: board tasks you own that you have taken off your own task list.
Working the board
- Columns are swimlanes and can be named anything. Drag a card between them, or use the lane chip.
- Topics group cards into bands. Collapse a band by clicking its header. A topic with no cards shuts, one with cards opens, and nothing is remembered: your own toggle lasts only for this board and view until you reload.
- Any single swimlane can be folded away too, per topic — see Folding a swimlane away.
- Sections open or shut by what is in them. Owned, Completed and Archived sections, swimlanes, topics and a task's checklist categories open when they hold something and shut when empty, except a checklist's Complete category, which always starts shut. The add row stays reachable: an empty swimlane stays open when no lane in its topic has a task. Retired topics open, since their header only appears when they hold tasks. A shut lane still takes a dropped card and highlights while you drag over it. Nothing here is remembered; your own open or close lasts for the board and view until you reload.
- Owned, Completed and Archived are separate views. Finished cards stay visible in the board's completion lane; archiving a card is what takes it off the board.
- Search is in the navigation strip, and Organize (in the strip under the view row) sets Group by. New topic…, in the Add task chevron and in Actions, opens Team settings on the Topics tab with the cursor already in the name box.
To-do 2
Active 1
Blocked 1
Done 0
A topic band with its swimlanes, under the four views and their counts. The band header folds the topic, and at its right-hand end one small button folds every lane in that band and no other — lit while they are all open, and named for the band it belongs to, so a screen reader hears Collapse all lanes in “Roadmap” rather than eight identical buttons. Every lane ends with + Add task, and every card you can edit carries its lane as a chip.
Putting topics and swimlanes in order
Drag a row by the grip on its left. In Team settings → Topics and → Swimlanes, each row has a handle; pick it up and drop it where you want, and the board follows. It works from the keyboard too: Tab to the grip and press ↑ or ↓. Active and inactive topics are ordered separately. Only a board administrator sees the grips.
Team configuration: Boards, Groups, Topics, Tags and Swimlanes
These five tabs in Team settings are where the board's shape is configured. Boards and Groups are covered above in People, groups and boards. Topics and Swimlanes are the board's two axes — a topic groups cards into a band, a swimlane is a column within it. Every tab's settings open folded to a title and remember what you opened only for this sign-in — see Every section starts folded.
Tags, and the vocabulary they draw from
Team settings → Tags is where a board's own tags are created, renamed and retired — separate from personal Studio tags and the quick way to add one from inside a task. Type a name into New tag name to add one; renaming waits for you to leave the field since it rewrites every task carrying that tag. Only a board administrator sees this tab's controls.
Retire, don't delete — the same rule for tags and topics
Inactivate is the button you want almost every time: it hides a tag or topic from the pickers while leaving it exactly as it is on every task that already carries it. Retired tags and topics sit in their own Retired card, and Reactivate puts one back in one click.
Delete is the separate, deliberately harder action underneath it. Deleting a tag or topic removes it from every task that had it — a topic's tasks fall back to No topic rather than disappearing. There is no bulk delete, only bulk inactivate.
If tags cannot all be deleted in one go, a message titled Some tags weren’t deleted says how many were, names the ones that were not, and explains that some tasks may already have lost those tags.
Topics carry one more button below Delete: Archive N tasks archives every task filed under that topic, open and completed alike, and leaves the topic defined. Nothing is deleted, and Restore in the Archived tab brings them back.
Archive a topic
A board administrator can archive every task on a topic in one action. Open the ⋯ menu on the topic's band and choose Archive topic…. It is offered to board admins only; members do not see it. The dialog counts the tasks first: open and completed, how many people own them, and how many are also shared to another board. A task shared elsewhere is archived there too, and the dialog says so.
Open tasks are archived as well. When there are any, an amber warning lists up to five of them by title and owner, then +N more, listed in Archived afterwards for the rest, so you see what is going before you confirm. Nothing is deleted: the tasks move to the Archived tab, and the topic is not retired. It stays in the topic picker, and it is not made inactive.
After you confirm from the band, Undo appears straight away and reverses that archive. Later, the topic's header in the Archived tab reads archived as a topic with the date, and a board admin sees Restore topic… there for as long as that archive is still open. It restores that same batch and nothing else. A task you archived on its own before the topic was archived stays archived. No email is sent for any of this.
The band's ⋯ menu lists Show only this topic, Add task in this topic and Collapse lanes for everyone. Board admins also get Topic settings… (on a real topic, on a single board) and Archive topic…. On No topic that last item reads Archive untopiced tasks…. If the database refuses the archive, the dialog shows the database's message with a Close button, and nothing changes.
The same action is on the topic's row in Team settings → Topics. Its button reads Archive N tasks and runs the same archive, so the two always do the same thing. It is not a delete.
The completion lane: which swimlane finishes a task
In Team settings → Swimlanes, one column is headed Completes tasks: a checkbox per row, only one checked at a time. Whichever swimlane carries it is where dropping a card marks the task complete — not a swimlane merely named “Complete” or “Done”. Renaming the lane afterwards does not move that meaning.
A board can also have no completion lane at all — clearing the checkbox is allowed, and a board in that state simply has no drag-to-finish; tasks are still completed the ordinary way, from the task editor. Checking a new lane automatically clears whichever had it before, enforced by the database so two people racing cannot both win.
Finishing a task on the board is done with the Mark complete tick on the card, or the Complete button in the task editor, or by moving it into the completion lane. Choosing a lane that is merely named “Complete” from a task's status menu does not finish it. Only the lane carrying the completion checkbox does that.
A brand-new board starts with five swimlanes already in place — To-do, Active, Blocked, Monitor and Complete — and Complete is already checked as the completion lane.
Owner, assignee, and leaving a task unassigned
Owner is who is accountable for the task. Assignee is who is doing it. They are often different people and neither implies the other.
A task can be left unassigned. Owner → Unassigned is a real state: an unassigned task stays on the board and appears in nobody's personal task list.
Assigning somebody who is not on the board
The Assignee list offers your whole team, not only people already on this board — anyone who cannot open the board is marked not on this board. Picking one of them asks you first. To be assigned a task, a person has to be able to open the board it is on — otherwise the task carries their name and they never see it. So the app says so and offers to fix it in place:
- Yes — they are added to the board and the task becomes theirs.
- No — nothing happens. They are not added, the task is not assigned to them, and the assignee goes back to whoever it was.
Only a board or team administrator can add somebody to a board. If you are not one, you are told which and asked to have an admin add them — enforced by the database, not by the message.
A name that is not a person on your team
Imported tasks and people who have left can leave a name in the Assignee field belonging to no account — those are assigned as they always were. A name two people share is left as-is too: the app does not guess which.
Collaborators
Collaborators is a picker now, not a box you type into. It shows one circle per person, with their initials, and a gray circle with a person outline at the end. Press that gray circle and a search-and-tick list opens — the same dialog Notes and the OKR editor already use to choose several people at once.
The list offered is this board's own roster of registered accounts, not the wider team the Assignee field offers. Naming somebody as a contributor records that they are helping and lets the app email them about the task; it does not grant them anything else, so there is no access question to ask and no prompt to add them to the board.
A name from before the picker existed is shown, but cannot be ticked
A collaborator with no registered account still shows, marked not a registered user — it cannot be ticked or removed from here, display only. A leftover first-name duplicate of somebody already shown by their full name is hidden rather than shown twice; an ambiguous name is kept rather than guessed at.
Show in my tasks
Under Owner, the owner sees Show in my tasks, deciding whether the task also appears in their own task list — ticked by default.
- Ticked — the owner sees it in Tasks as well as on the board.
- Unticked — it stays on the board and leaves their personal list.
- Unassigned — nobody gets it in their personal list this way.
The assignee always sees it
This setting is about the owner's own list. If a task is assigned to you it is in your task list whatever the owner has chosen. Only the owner sees the tick box; handing the task to a new owner starts them off ticked.
Assigning a task you own to somebody else moves it to On team boards. It leaves your own list and stays on its board, so it shows under On team boards rather than Watching. Assign it back to yourself, or clear the assignee, and it returns to your list. Only you move your own task: if somebody else changes it, your list is left as it was.
Opening the same task in Tasks
A task in your own list shows My Task under its title, opening the same task in Tasks — not a copy. Absent when the task is not in your list, though Tasks opens any task you can read either way.
Folding a swimlane away
Press a swimlane's heading to fold it to a narrow strip with its name and count still on it; press again to open it. It is folded for that topic only — the same lane under a different topic is unaffected. Each topic header also carries one button that folds every lane in that band and no other, named for its own band — Collapse all lanes in “Roadmap”, say — rather than left as eight identical buttons, and offering Expand all lanes once pressed. An empty lane folds like any other, reading No tasks when open.
Folding is yours, not the team's
Which lanes you keep folded is a personal view setting, saved with your account. The fold-all button in the strip's tools is a different control: it folds topic bands, not the lanes inside them (sections, on Owned/Completed/Archived). The two are deliberately not merged, because a single button could not honestly say which of the two a press was about to act on.
A column called "Complete" does not finish anything
Swimlanes are yours to name, including calling one "Complete" — naming it does not mark its cards done. A task is complete only when somebody ticks it complete.
Ticked something by mistake? There is a way back
Completing a task moves the card to the board's completion lane (and lists it on the Completed tab), and a short Undo appears at the bottom of the work area (centered at the bottom of the screen on a narrow one) for about six seconds — and waits while your pointer is on it or you have tabbed to it — putting the card back in its swimlane. That is deliberately different from reopening a task from the Completed tab, which sends it to the first swimlane instead — reopening is picking the work up again, undo is correcting a click.
Anyone on the board can edit its tasks
If you can see a task on a board you are a member of, you can change it — title, status, due date, assignee, topic, tags and description — without owning it or being assigned to it. Owner and assignee record accountability; they no longer decide who is allowed to type.
Two things stay with the owner: Deleting — only the owner, since a task can sit on several boards and deleting it would remove it from all of them; not even a board administrator can. Handing it over — only the owner or a board administrator, and it is a one-way door. All of this is enforced by the database; you can only edit tasks on boards you belong to.
Email notifications for the team
Team settings › Email decides what leaves the app as an email. The Message Center is unaffected by everything on that tab — turning email off only turns off the copy that arrives in an inbox.
Email is off for every team until a team admin turns it on. Once on, five events can send an email, four on from the start:
- Direct @mentions — somebody names you in a comment.
- Task assigned — only when the assignee actually changes. Saving a task again sends nothing.
- Note shared — only when the person is added.
- Objective or key result ownership — being made accountable for something.
A direct @mention can also carry a short summary of what changed, written once, by whoever wrote the comment, using their own AI Assistant and their own key. If they have not set one up, nobody who was mentioned gets a summary — everybody gets exactly the email they always have. Your own AI Assistant makes no difference either way: you do not need one to receive a summary somebody else wrote.
The fifth is different: a task you watch is updated — something you asked to follow. It is off until it is switched on, needing both halves: this team's tick here, and your own A task I watch is updated. See watching a task that is not yours. Changes to a task you are not watching stay off.
Ordinary comments and OKR progress are not on this tab at all, and that is a correction rather than a change — they used to appear as ticks a team admin could switch on, and switching them on never sent anything. They are emailed now, as your own choices in Settings › Email; a setting your team had before is kept rather than deleted. Comments reach you by @mention, and OKR progress is on the board. You are never emailed about something you did yourself, and one event never emails you twice. You choose which address receives them in Account › Notification email.
Task reminders are a sixth thing, and they start on
Switching a team's email on also makes task reminders available — a schedule somebody sets on one task, not an event the team chooses. A reminder is a sixth thing that can send email and it is not one of the five above: nobody switches it on. See email reminders on a board task.
The Email tab carries a tick for reminders, the only one on the tab that starts ticked. Unticking it does not silence reminders on its own: a reminder to somebody stops only when every team of theirs that sends email has unticked it. One team cannot switch off mail another team is willing to send. A reminder on a task on no board at all passes no team tick at all.
The switch that reliably works for one person is that person's own. Anybody can stop every task reminder addressed to them from Settings → Email in Tasks — no team setting overrides it.
Working from an email on a board task
The board’s task editor carries the same email action Tasks does: the paper-plane Follow-up button in its header and, on a task that came from an email, Draft follow-up… on the email’s card. Both open the same follow-up dialog: you say what the email is for, it is drafted in your email style, and you edit it and open it in Outlook yourself. Nothing is sent for you. With no AI assistant configured the button builds the email from your own words instead. See Working from an email.
If a task arrived by email, the message is saved on it and a card under the description opens it — see Reading the email a task came from. Tasks created by email are always personal, so that card appears on a board task only if it was shared there afterwards. “Update from email” used to sit beside the composer and has been removed from both editors.
The task editor saves as you type
There is no Save button on a task that already exists. Change a field and it is stored a moment later. Close the editor with the ✕ when done. Cancel is gone for the same reason — change something back if you made a mistake, or use the undo offered when you complete or delete.
The line at the bottom of the editor says where your change has got to: Changes save as you type, Saving…, or All changes saved in green with the time. A refused save shows a red message saying your last change was not saved, with nothing lost. It stays until you next edit something — see there is no Save button.
Opening a task and just reading it changes nothing. A new task still has a button — Create task brings it into being, then it saves itself like every other task. If somebody else saves the same task while you have it open, nothing of theirs is overwritten — your change is not saved, and the editor and the board both reload to show their version.
Opened from a note, it is this same editor. A board task linked from a note opens in a window over the note, with every section the board's editor has. Open on the board, beside the ✕, takes you to the task on its board. Whichever way you close it — the ✕, Esc, a click outside, or Open on the board — what you typed is saved first. A link to another task inside it opens that task in the same window, in its own editor, and Close still returns you to the note. Any other page of the application a link points to opens in the full window after your changes are saved, and a link to another website opens in a new tab — neither is loaded inside this window.
Complete, archive, and never delete
The top of the editor carries a tick to mark the task complete — press it again on a finished task to reactivate it — and a lidded-box icon that archives the task. A team task is never deleted outright; archiving keeps a record of where the work went.
The Completed tab still has its own Archive row action, and the Archived tab has Restore — the editor's icon is a second door to the same place. Archiving is open to any board member, an ordinary edit not a delete. A personal task — one on no board — stays fully deletable by its owner in Tasks.
Archive completed… on the Completed tab, or on a completion lane, opens Archive completed tasks, which archives many finished tasks at once. Nothing is deleted: Restore archived… on the Archived tab opens Restore archived tasks and brings them back.
The task editor. The tick and the archive icon sit on the left beside the title; on the right, in order, are Share, the eye that watches the task, the envelope that decides whether a watched update also emails you, and the ✕ that closes it. Two tabs: Details and Comments, whose heading carries the number of them. There is no Save button and no Cancel — each field is stored a moment after you change it.
Watching a task that is not yours
At the top right of the task editor are three controls: Share, the eye and the envelope — none of them sit beside the tick and the bin, which are on the left of the title row — then the ✕ that closes it — the same editor everywhere you meet it.
Share copies a link straight to this task. A link is not a grant — the same access rule that governs opening the task normally governs opening it from a link.
Press the eye to start watching; press again to stop. You do not have to own the task or be assigned it. It changes nothing about the task — no reassignment, no addition to your list, and nobody is told you are watching.
From then on, a change to the task reaches you in Messages under Watching, and gathers on the Watching tab in Tasks; see tasks you are watching. It reports what other people do, never what you do yourself.
It can email you too, off until you switch it on. A watched update always reaches Messages; it reaches your inbox only if A task I watch is updated is on — the envelope beside the eye is that switch, the same setting as Settings → Email. It belongs to your account, not to this task — switching it on here decides watched-task email everywhere, for every task you watch. A comment on a watched task is covered separately by Somebody comments without mentioning me.
Following a whole board, or a single lane
Follow a whole board from Actions, or a single lane from the lane's header. You are emailed when a task is added to it, when a task on it changes, and when someone comments on one of its tasks. For a lane, you hear about a task while it is in that lane, including the move that takes it out.
The lane control is Follow this lane in the lane header's ••• menu (it reads Stop following this lane once you follow it, and the lane shows a quiet Following tag). The board control is Follow this board in the view row's Actions menu, a toggle that shows a tick once you follow the board; it is not offered on All boards.
You can follow a board only if you are a member of it. If you leave the board, your follow is removed.
Turning off A followed board or lane changes in Settings › Email stops the mail without unfollowing.
There is no follow control on the phone.
Email reminders on a board task
The board's task editor carries the same Reminders section Tasks does — between OKR and Attachments — with one difference: on a board you choose who is reminded. Full description: email reminders on a task.
The board's Reminders section. The difference from Tasks' is the line in the middle: on a board you choose who is reminded.
Unfold Reminders and press + Email reminder. It starts as a working reminder — daily, at 09:00, from today, to you — and you change it from there.
- How often, Time of day and Starting are the schedule.
- Who is reminded offers the people on this board only; you are in that list yourself, marked (you).
- There is no Save button — every change saves as you make it, and a sentence under the fields reads it back: Daily at 9:00 AM, from Sep 8, 2026, to 3 people.
The time is held in the time zone it was set in; a reminder set elsewhere names that zone.
The reminder is yours, not the task's. Two people can each keep their own reminder on the same card. Remove reminder removes yours only, asking first and naming who stops being emailed.
A reminder needs at least one person — unticking the last name is refused. Remove reminder is how you stop it altogether. Somebody you named can take themselves off, and if they were last, the reminder stays with nobody on it, reading Nobody is selected, so nothing is sent.
Completing the task stops it, and so does archiving it — nothing is sent until it comes back. Reopening or restoring starts it again on the schedule that was already there.
If somebody names you, you can see it and take yourself off it. A reminder you did not create appears in a block of its own below yours, headed Somebody else set this reminder and named you on it, with one button: Stop reminding me — different from Remove reminder above it: Remove reminder takes away a reminder you created yourself, and Stop reminding me takes you off one somebody else created.
- You do not have to ask the person who created it — your place on somebody else's reminder is yours to give up.
- Their reminder carries on for the rest of the people on it, so you come off without disturbing anybody else it names.
- You cannot change it and you cannot delete it. See it and leave it is the whole of it.
- Only the person who created it can put you back on — leaving is not something you can undo yourself.
- The person who set it is not told. Nothing is emailed to them; you're simply off the list next time they look.
Shut, the Reminders heading counts these after your own line — 1 set by somebody else, or 3 set by other people — so a reminder somebody else is sending you is not hidden behind a folded section.
That is different from stopping reminders altogether, and the two can read like turning reminders off while doing different things. Stop reminding me takes you off one reminder; every other reminder on every other task still reaches you. To stop the lot, switch task reminders off in Settings → Email in Tasks — one switch, every reminder on every task and board, and it changes no schedule anywhere: you stay named on everything, and switching it back on starts them arriving again.
Stop reminding me takes you off one reminder only. To stop all of them, switch task reminders off in Settings → Email in Tasks — one switch, every reminder, every task and board, and no team setting overrides it. See a reminder somebody else set, that names you.
The section is not shown at all until the task exists, or if this team has not switched email on — see email notifications for the team.
Making a new tag without leaving the task
Beside the tag chips in the task editor, + New tag… opens a color swatch and a name box. Type a name, press Add or Enter, and the tag is created on this board and put straight on this task. Escape backs out without closing the task.
It is offered to team and board administrators only, and only on a task you can edit — the database is what refuses a tag from anybody else, and the button is hidden to match rather than to decide. If a name is already taken on this board you are told so.
Everything else about tags — renaming, recoloring, deleting — lives in Team settings, since those affect every task the tag is on.
Formatting a task's description
The description box is the same height as the one in your own task editor, growing with the window. It has the same formatting bar the Notes editor has: bold, italic and underline, bulleted and numbered lists, headings and quotes, text size, Color and highlight, typeface, and alignment. On a narrow window the groups fold into a more menu. Formatting is kept with the task, reading the same on the card, in the editor and in an exported report.
Tidy formatting with AI is at the end of the bar, after Undo and Redo. It lays the same words out better — headings, lists, spacing. It is structure only: every fact, date, number and table is preserved exactly as written. It is one step: Undo brings your original back. The button appears only when you have an AI assistant configured.
The description also takes Markdown shortcuts as you type, with the same lists, Divider, emoji and link card as a note. The table of shortcuts is in Markdown shortcuts.
Work nobody has scheduled: the No date switch
Under the due-date field in a board task is a switch marked No date — the same control, in the same place, as in Tasks. Turn it on and the due date is cleared; the field itself reads No date; the card on the board reads No date too, and drops out of any due-date window you filter by.
Turning it off sets the due date to today and puts the cursor in the field, so you can change it with one keystroke. The switch is only telling you whether the task has a due date, so it moves on its own: type a date and it turns itself off.
It does not wait to be saved. It is stored a moment after you move it, like every other field on the task — see The task editor saves as you type. On a task you are only able to read, the switch is grayed out along with everything else.
A checklist item's link to a task
A board task's checklist is the same checklist a note has — five categories (To-do, In progress, On hold, Complete, Parking lot), the same … menu, right-click, drag and Move to — see The checklist on a task. Its items can be flagged high priority (the flag beside the tick, or Alt+P) for everyone on the board, and Heads down pins them above the categories for you; see Flagging an item as high priority, and Heads down. An item can point at a team task and at one of your own tasks, both at once:
- Make a team task makes a brand-new task on this same board, in this same topic, and links the item to it.
- Make a task, just below it, makes a brand-new task of your own from the item — assigned to you, on no board — and links it as the item's task.
- Link to a team task searches every board you belong to; picking one only records the connection — nothing is written back to the far task or its board. Picking one of your own tasks there — they are listed as Your task · will be added to this board — moves it onto this board, into this topic, automatically, and links it as a team task. (If that move cannot run on this page, you are told so in place rather than it failing silently.)
- Link to a task connects one of your own tasks without moving it.
- Open its task / Open its team task open the linked task's editor over the board, and Unlink clears a connection without touching either side.
- Comment opens this task's Comments tab with the item's text as a starting line.
Each item has a title and a description, in two columns, and both are edited in place as on any checklist. The avatar button on an item assigns the task to someone; its picker lists that board's members, and anybody not on a team with you is grayed out with Not on a team with you. Make a team task from an item assigns the new task to you.
The description is one line at rest: text that does not fit fades out at the end, and the full text is in the tooltip. It grows when you click into it and shrinks again when you leave.
Beside a linked item, one chip reads Task or Team Task with the task's due date, followed by the assignee's initials, such as Team Task · Today (hover for the full title); once the task is finished it reads Team Task · Complete instead of the date. Its color is the task's status: green complete, red overdue, yellow due today or tomorrow, plain gray later or undated. It turns to a dashed gray label once the target is gone — the item's menu still offers Unlink. Moving an item into On hold moves its linked team task into this board's On Hold lane, if the board has one.
The checklist's own … menu has Remove the checklist…. Once an item has made one of your tasks, its confirmation lets you choose to delete them too: it deletes only the tasks this checklist made. A task that was only linked is kept, and so is every team task (a team task is archived on its board, never deleted). The confirmation names each task first.
A checklist item can also connect to an objective or a key result — a third, independent link. Link to an objective / Link to a key result search the team's own OKRs; its chip is purple, reading Objective or Key Result, and grays out the same way if deleted or access is lost.
Turning highlighted text into checklist items
Select some text in a team task’s description, then press the checklist button in the formatting bar (Add to checklist) or Ctrl+Shift+9 (⌘+Shift+9 on a Mac). The button is on only while text is selected. Each line or bullet becomes one checklist item, as plain text: formatting, images and links are left out, and bullets, dashes and numbers at the start of a line are dropped. A line of 120 characters or fewer is the title; a longer line is cut at a word and the rest becomes the item’s description. The items go to that team task’s own checklist.
Items land at the end of To-do, in the order you selected them, and the text you selected is not changed. An item already on the checklist is skipped, and the message says how many (Added 2 checklist items · 1 already there). The message has an Undo that removes exactly those items. A selection of more than 50 lines asks you to confirm first. A comment box has no such button, and neither does a checklist you can only read.
Comments, mentions and attachments
Every task has a Comments tab. It is where the state of the work actually lives — “waiting on legal”, “moved to next sprint” — and anyone who can see the task can add to it.
The comment box is at the top of the Comments section. Type at the top; newest first; scroll down for older. A comment you post appears first, and the list opens at the newest one.
Mentioning someone
Type @ in the comment box. A short list of the people in your teams appears — keep typing to narrow it, arrow keys move, Enter or Tab picks. Picking somebody does not post the comment; you still press Post. Same in every comment box in the application.
It searches on either name — @jo, @doe and @john doe all find John Doe. You can also just write @First Last anywhere in a comment; replying to somebody does this for you.
- The list is the people on THIS piece of work. A task's list is everyone on its boards' teams; an objective or key result belongs to exactly one team, so its list is that team. If you are in two teams and commenting on something owned by one of them, the other team's people are not offered: they have nothing to do with this work. Somebody in a team you are not part of never appears, and typing their name out does not mention them either — enforced by the database. Mentioning somebody not on this board is fine and often the point: it gives them the message, not the board.
- A first name on its own is not a mention. “@John” is just text.
- The mention follows the person, not the name — a later display-name change updates old comments too.
If two people in your teams have the same name
Typing that name mentions neither of them. Pick them from the @ list instead, which shows their email address to tell them apart.
Editing a comment that mentions someone
Mentions follow the text: take a name out and that person no longer has the message; add one and they get it. Anyone still named keeps the message they already had. Deleting the comment removes its messages with it. A mention behaves as one piece — a single Backspace takes the whole name out.
The message center
It covers every team you are on, not just the one on screen. One personal inbox: a mention on any board of any of your teams is in it, and each message names the team as well as the board. The unread count is the total across all of them.
View task takes you there whatever team you are in — switching team, opening the board and the task, never a destination you lack access to.
View task opens the task in a floating editor over Messages. Closing it returns you to the same place in your messages.
Being mentioned puts the comment in Messages, the same window in Tasks and on the board, personal rather than team-based: it shows every mention you can see, whichever board it came from.
Each message shows who mentioned you, what they said, which task, and which board. Unread, All, Threads and Watching are the tabs; the last two are described in the task manual under tasks you are watching.
When something is waiting, the bell lights up and carries the count. Nothing is marked read just because you opened it — a message clears on Mark read, or when you open the task it points at (also scrolling to and highlighting the comment). There is also Mark all as read.
Closing that task brings you back to Messages, not the board. A task opened from the board still closes onto the board.
Reacting to a comment
A team task has the same comment thread and the same reactions as a task on Tasks, in the task pop-up and the framed editor alike. Under every comment: 🙌 High five, 👍 Thumbs up and ❤️ Heart.
- You have one reaction per comment. Press a different one to switch; press the one you chose to take it back.
- A reaction notifies nobody: no email, no Messages entry, no badge.
- You cannot react to your own comment or to a line the system wrote.
Tidying a comment up
Under the comment box, Format and Bullets rewrite rough notes into something a colleague can read. Your original is kept until you accept via a Use this / Cancel row. A rewrite that would drop an @mention is discarded rather than offered.
Tidy formatting with AI, at the end of the comment's formatting bar, is different: Format and Bullets rewrite words; Tidy changes no word at all — it lays what you wrote into paragraphs, a list or a heading, preserving any formatting you applied. One Ctrl+Z or the Undo tidy button reverts it. All three need an AI assistant configured and are absent otherwise; see tidying a comment's formatting.
Writing a comment from an email
Press From email… under the comment box, paste the email (or
drop a .eml file) and press Draft the comment. The assistant
writes a compact summary — one sentence on what changed, and at most
three bullets — above a line giving the date and time the email was sent,
who sent it and the subject.
Nothing is posted. The draft lands in the comment box for you to edit; you still press Post comment.
The date comes from the email, not from the assistant
Read from the email's own Date: or Sent: line. If missing, the header says date not stated in the email rather than guessing.
Comments waiting to be read
When somebody else comments on a task, its card shows a highlighted comment count, same treatment as the bell. Mark all read and Mark unread are in the ••• menu (Conversation options) beside the sort button, and the comment box folds to one Add a comment… row when the task has comments (press it, or start typing, to open it); posting a comment, or moving to a task's Comments tab, marks its comments read. Read state is yours alone and follows you between Tasks and the team board.
Turning a comment into a task
After posting a comment containing something somebody agreed to do, a small Possible action item card appears with a suggested title, owner and date. Press Create task or Ignore. It never creates anything on its own, and never invents an owner or deadline the comment did not state.
Attachments
Drag a file onto the task, or press Choose files…. Anyone on the task's board can open its attachments, as can its owner and assignee; only the uploader can remove a file. Attachments appear once the task exists.
The size limit is written under the dropzone — set by a system administrator and can change, so this page does not repeat a number of its own. Anything larger is refused by the server as well as by the page. A handful of file types that a browser would run or render as a web page cannot be attached at all.
Files you have already attached are never affected
If an administrator lowers the limit, nothing you have already attached is removed or blocked — every existing file stays and still opens. The new limit applies to the next file somebody chooses, and to nothing else.
For something large, link to it rather than attach it — put the shared-drive or SharePoint address in the description.
Attaching a file does not share the task
A file inherits the task's visibility and nothing more.
Owned — board tasks you keep off your own list
Beside Board, Completed and Archived there is Owned: the board tasks you own with Show in my tasks off.
- Only your own tasks appear.
- A task already in your task list is not here, including one there because it is assigned to you.
- Completed and archived work stays in its own tabs.
- Show in my tasks on a row puts it straight back.
It behaves like Completed: the same grouping, section headers, fold-all button (Collapse all sections) and search box.
Which board a setting is for
Topics, Swimlanes, Tags and Import all belong to one board. Each starts with a Board selector saying which, changeable there without closing settings. Picking another board switches the board behind the dialog too. Tabs belonging to the whole team — People, Groups, Email — have no selector.
The team and board dropdowns
Both sit in the view row, sorted alphabetically; hovering a shortened board name gives you the whole of it.
Creating a team or a board is done in Team settings — on the Team and Boards tabs. Making one is only offered to a Super Team Admin (or your Organization's owner), except that anyone with no team at all can create their first one. Creating a board is a Super Team Admin action (or your Organization's owner); running one is not: a team admin still renames, deactivates and manages who can see it.
Test workspaces
The browser tests keep their own organization, teams and boards. If you can see some of them without being on them (as a god-mode user, an Organization Owner or a team admin), they are left out of your organization, team and board lists, the team board's pickers, search and the Admin Console tables. To include them, turn on Show test boards: at the foot of the organization switcher, or in My Settings → Workspace → Test workspaces. A board you are on is never hidden, and a link to a test board still opens it.
Where the tabs are
The board's tabs read Board, Owned, Completed, Archived, at the left of the view row, after the pickers. Owned sits beside Board because it is live work.
Recently completed, and how far back it looks
On the Completed view the toolbar grows a picker reading All completed or Recently completed · last N days, starting at 7 days. It is a team setting, not a personal one, and that is deliberate: everybody looking at the same board should mean the same thing by "recently". A team administrator changes it in Settings → Team (3, 7, 14 or 30 days), for everyone at once.
A completed task with no completion date is not recent
The window uses the date the task was completed. A task marked done before the app started recording that date does not appear in a window asking "when" — it is still on the Completed tab.
How long a swimlane gets, and the rest behind View all
A lane shows the first 5 tasks and ends with a button reading View all 8 tasks · +3 more. Press it and the rest appears; the button becomes Show less. Five is exact — a lane holding exactly 5 shows them all with no button.
It is a team setting covering every board the team owns. A Team admin changes it in Settings → Team under Swimlane length, for everyone at once. A Super Team Admin can too — this is ordinary team administration, not one of the six things reserved to that role. A Member is not shown the control.
Expanding a lane is yours, and it is temporary. Opening one lane leaves every other lane as it was, and nothing is remembered: reload the page and every lane is back to the team's number.
Searching or filtering shows everything, past the limit
As soon as you narrow the board, the limit stops applying and every lane shows every match, with no View all button anywhere. Clear the filters and the lanes go back to the team's number.
Lanes are the Board tab
Owned, Completed and Archived are lists rather than columns, so this setting applies only to the Board tab.
Widening a lane, and Fit or Fixed
Lane width in Customize's Layout section is the Fit to screen / Fixed width choice (it is not drawn below 1024px wide, where Fit does not apply). Fit is the default from 1024px wide: the board shares the width of the screen between the lanes, and the busiest lanes take two or three card columns, so more cards are on screen at once. Fixed is the one-column board. Your choice is saved for this page.
In Fit, each lane's header carries a small columns button that steps through automatic, 1, 2 and 3 columns, then back to automatic. In Fixed it widens the lane to two card columns and back, as before. More than one lane can be widened at once, and each is independent. The width you pick is a temporary view only, and it is not remembered: reload the page and every lane goes back to automatic, nothing saved.
Narrowing the window never adds a column
In Fit the board works out how many columns each lane gets from the screen width and the cards in it. Making the window narrower can take a column away from a lane, but it never gives one back, so a lane does not get wider in columns as the screen shrinks. The cards then stretch a little to fill the leftover width, up to 264px. An empty lane stays at one column. Each topic group is fitted on its own row, so a lane folded in one group takes only a narrow strip there and does not hold back the open lanes beside it.
Not the same as folding, and not the same as View all
Folding a lane shrinks it to a narrow strip and is remembered, per topic. Widening adds columns to one lane and forgets itself on reload. View all reveals more rows in the lane; widening adds a column, and the two can be used together.
The figures above the board, and filtering by them
One strip sits between the view row and the board, and it is a control rather than a readout. Its figures are five chips for the board as narrowed — Total tasks, Complete, Open tasks, Overdue, Due this week. Its chevron drops down the breakdown: Tasks by status, Tasks by tag and By assignee, the same work divided between people.
Pressing a figure narrows the board to it. Overdue shows work due before today, Due this week today through Saturday, Complete opens the Completed view, Total tasks clears every filter. Only one is ever lit.
Topics are filtered from the Filters menu along with the due-date window; people are filtered from the By assignee cards, Mine, or by name search.
The strip starts folded, and remembers how you left it, saved to your account. Press the chevron beside Team at a glance (or Tab to it and press Enter or Space) to open the breakdown; folding keeps the figures as a single row. By assignee has its own chevron inside the breakdown and folds to its header alone. Show Team at a glance and Show By assignee in Customize do the same.
The utility rail
Down the right of the board is the utility rail, shared with Tasks, Notes and the Calendar: four cards — Time, Weather, This month and Quick links — each with its own menu and fold. The rail is per page, including card order; drag a card by its handle to reorder, or focus one and press Alt with an arrow key. Its width is shared across the four pages — drag the divider, or set it on the View tab of Team settings, whose own sections are named for what they arrange — Board defaults, The bands above the board and The utility rail. The rail's header, its ••• menu and Customize panel's Utilities section are the same as on every other page: Widget settings opens Settings > Widgets, and Reset section restores this page's defaults. Which cards a page shows is in Customize › Utilities (Customize… on the rail’s ••• menu, or Customize Utilities… on a card’s own menu) or Settings → Widgets. To show or hide the whole rail, use Show the Utilities panel in Customize › Utilities, the same switch as on Tasks and Notes (there is no separate Utilities button in the board's toolbar), or the › arrow at the top of the rail.
The rail, top to bottom. A card's … menu is where its own settings are — time zones, weather locations, the months to show, and managing the links.
Quick links
A team can publish as many links as it needs to everybody on it — runbook, sprint board, on-call rota. There used to be a limit of five; there is no limit now, and a longer list simply scrolls. They appear in the Quick links card alongside your own, each opens in a new tab so you never lose the board.
You see the description, not the address — hover for the tooltip.
Only http and https addresses can be opened.
Which of them you see is yours to decide. A team link arrives switched on; switch it off for yourself and it leaves your card while staying in the list to switch back on — you are never editing the team's copy. Saved to your account. Reach this from the card's … menu → Manage links…, or Settings → Time, weather & links.
A team administrator defines them in Settings → Team: one row per link plus an Add a link button, each with a switch, a description and an address. A row shows to the team only once it has both and its switch is on; whichever is missing is said underneath. Clearing a row leaves it where it is rather than shuffling the rest up. This is a team setting; if you are not an administrator the section is not shown.
Switching a link off keeps it
A link with its switch off stays saved; it just stops showing to the team. The row says “Saved, and switched off”.
By assignee. Each card carries the person's initials, their percentage and how much of their work is done; the due-date window lives on this band's header. Press a card to narrow the board to that person — the selected card is highlighted, a banner states everything that is applied and how many tasks are left, and Clear all removes the lot.
- Picking a topic from the Filters menu adds that topic to the filter.
- Clicking a person card adds that person, including their Completed and Archived work.
- Where a task has no assignee, the person rollup falls back to its owner.
- By assignee narrows to the topic you have selected, while the topic bars themselves stay unfiltered as the selector.
- Both bands fold on their own, and remember it.
- Which tab you are on is not a filter.
Filtering by due date
Due from and to on the By assignee band's header narrow the whole board to tasks due in that window; you can set just one.
4w, 8w and 12w beside the fields are shortcuts for a window around today, half back and half ahead. Hover one to see the exact dates. Clear dates is the way off.
It starts on Any due date, and that means everything. Untick it to use a range; Clear filter puts it back. The range applies to the board, the Completed and Archived tabs, the analytics figures and the exported report.
A task with no due date is hidden while a range is set
A date range asks "what is due in this window," and a task with no due date is not due in any window — the note beside the fields says so while a range is on.
Clear dates drops the range and leaves other filters alone; Clear filter in the blue banner drops everything at once.
Picking more than one
Selections add up. Click two topics and you see both; add two people and you see their work within those topics. Click a highlighted card again to drop it, or Clear in the blue banner to remove everything.
"in Roadmap or Support, assigned to Kate Ross or Priya N"
Within one kind — two topics, or two people — selections are an or. Between the two kinds it is an and: those people, in those topics.
Everything downstream follows the same selection: the assignee rollup, the tab counts, and a board export covering exactly the filtered set.
Team Insights — how your team is actually using it
The figures above the board describe one board. Team Insights describes the team: who is using the application, how much work is moving, which capabilities people reach for. Open it from Team settings → Team, above Objectives and key results, pressing Open Team Insights. It opens on top of the settings window; closing it with × puts you straight back where you were, without reloading the board. Only a team administrator sees the card.
Three views, one date range
Overview opens first: active users, tasks created, tasks completed, team adoption, an activity chart, and capability usage. User Engagement lists every member with what they did. Activity & Audit Trail is the chronological record. The date range at top-right (default Last 30 days, or 7/90 days, this quarter, custom) applies to all three.
Narrowing what you are looking at
The bar under the heading filters every view at once — by board, user group, person, or OKR area. Clear filters resets these four without touching the date range.
Filtering by a person changes what two figures mean
A board or OKR area filter narrows which work is counted; a person or group filter narrows who did it, so Tasks Created/Completed are marked Attributable tasks only with no period comparison, since per-person attribution began partway through most periods. Team adoption disappears while one person is selected.
An OKR area shows its objectives and key results, not just their tasks
Choosing an area widens User Engagement and the audit trail to show what happened to the objectives and key results in that area, alongside linked tasks. An objective or key result that has since been deleted cannot be placed in an area any more, so its activity is left out of an area-filtered view rather than guessed at — it still appears when no area is chosen. A board and an area together narrow to task work only, since an objective is not on a board — the two filters at once cannot show OKR activity, only the tasks on that board and in that area.
"Active" means somebody did something real in the period — created or changed a task, wrote a comment, set a reminder, linked work to an OKR. Team adoption is the percentage of members that is. Opening a page is not activity and is not counted — there is no presence indicator.
Why some older work has no name against it
Per-person attribution is newer than team totals, so a long period shows full team totals while per-person columns cover only the recent part. A row whose author was never recorded reads Unknown actor rather than guessing.
What it does not show you
Team Insights is not surveillance. It shows names, counts, last-active times and the title of what changed. It does not show IP addresses, locations, devices or browsers, and it does not show what anybody wrote.
The team mark, and the Organization logo
The small picture in the top-left corner of every page, beside the team name, has two homes depending on whether your Organization has been set up yet.
Today: the Team mark, in Team settings
A team administrator chooses a PNG, JPEG or WebP (not SVG), resized to fit a 30×28 slot, never stretched — a wide logo sits smaller in the slot rather than being squashed to fill it. “Use the default” removes it; removing the picture is the default, leaving the team's name beside the corner with nothing else to turn off.
Once your Organization is named: the Organization logo takes over
The Team mark card stands down. Organization logo, in organization settings → Organization, is one card that replaces the old Organization mark and Organization files cards. Upload a logo… sets the logo in one step: images only (PNG, JPG, WebP, GIF or AVIF, up to 5 MB), fitted to the slot and never stretched. The card says This is your organization’s logo. once it is set, Loading your logo… while it is being fetched, and That image could not be shown safely. Upload a new one. when the stored image cannot be drawn.
Other uploaded images (n) and files (n) is folded under the logo. Each image there has Use as logo and Remove; older PDFs stay listed and removable, but new uploads are images only. Remove beside the logo clears the logo and keeps the file; Remove on a file row deletes the file.
Only an Organization Owner can change it. The logo shows beside the organization’s name and in invitation emails. Everybody in the Organization sees the same logo; your own team’s name still stays the word beside it.
A team's invitation mark is a separate, older picture and does not follow either of these — an invitation is headed by whatever mark that team itself uploaded through the Team mark card; see inviting somebody.
When the board area says you have no access
If the board area says No board access, the team has boards but none of them has been shared with you yet. An organization owner or a team admin can add you. The team picker, board controls and utility rail all disappear while this notice shows. If you belong to more than one team you can still switch — press your team's name, then Teams.
That is different from “No board open” (you have boards and have not chosen one) and “Could not read the boards” (the server did not answer).
Inviting people outside the Organization to meetings
This switch is retired. STRIDE no longer emails meeting invites to anyone, so Organization settings has no switch for inviting people outside the Organization. A typed outside address still goes into Outlook’s To when a member finishes a meeting in Outlook. See the calendar help.
One AI key for the whole Organization
An Organization Owner can set one AI key for everybody in the Organization, so nobody has to create an Anthropic or OpenAI account of their own. Each Organization sets its own: open Organization settings → Organization and press the header of the Organization AI assistant card (the Datadog card is the next one down). Only Organization Owners open that tab. Your own choice of which key your requests use, if you have more than one, stays in My Settings → Account under AI key for your requests.
- Choose Claude (Anthropic) or ChatGPT (OpenAI) and paste the key.
- Press Save and turn on. STRIDE tells you how many people will use it and how many have a key of their own saved, then tests the key once. The key is stored encrypted and is never shown again, not even to you: the card shows only the provider and the last four characters, who set it and when, and whether the last request worked.
What changes for members. Every AI request by an active member, on every page, in Ask STRIDE, the week brief and Tasks by email, uses this key. Members’ own keys are put aside for 30 days, not deleted: if you turn the organization key off within 30 days, each person gets theirs back. After 30 days the put-aside keys are deleted. A person who joins later has theirs put aside the same way. Their Settings → AI shows Provided by your organization and names the provider, with no key box. Requests go through STRIDE’s server, so the key never reaches anybody’s browser.
If the key stops working (refused, out of credit, rate limited) nobody falls back to a personal key. Members are told the organization’s key was refused and that an owner can fix it; the card shows Needs attention with the reason. Press Replace key to paste a new one, or Test to check again. Turn off deletes the key from STRIDE and returns members’ own keys.
Usage, last 30 days lists each person’s requests and tokens, busiest first, so you can see what drives the bill. The usual per-person limits apply to everyone (120 requests an hour, 600 a day, 12 heavy ones an hour). Every AI request on the organization’s key is counted, including Ask STRIDE, the week brief, Tasks by email and the change digest; Open AI insights shows it by person, feature and model over 7, 30 or 90 days.
STRIDE support. If STRIDE’s own support staff set, replace or turn off the key on your behalf, the card says Set by STRIDE support, not a person’s name. A person with access to more than one Organization, or who also keeps a key of their own, chooses which key their requests use under AI key for your requests on the same Account tab: each Organization with a key, My own key · Claude (Anthropic) or · ChatGPT (OpenAI) (STRIDE support only), or Automatic: an organization’s key (the current one, or the one you joined first), which is the default. Automatic always uses an organization’s key while any organization you belong to has one: the one you are working in if it has a key, otherwise the one you joined first. Your own key is used only when none of your organizations has a key, or when STRIDE support chose it.
The confirmations. Turn on the organization key? names how many people will use it and how many own keys are put aside. Change the organization key’s provider? appears when a replacement key is for the other provider. Turn off the organization key? says whose own keys come back. A member’s Settings → AI heading reads AI assistance while the organization provides the key.
Leaving an Organization
At the bottom of Organization settings → Organization, Leave this Organization ends your own membership. You lose every team, board and group it gives you; work assigned to you is unassigned, and objectives you own are left unowned. Your own Tasks, Notes and Calendar stay with your account.
If you are the only Organization Owner and other people are still here, you cannot leave yet. Promote somebody else first. If you are the only person left, leaving closes the Organization — use Close this Organization below.
Closing an Organization
At the bottom of Organization settings → Organization is a Close this Organization card, in the same red danger-zone styling as every other permanent action. It only appears when there is nobody left to protect — you are the sole active Organization Owner and no other membership exists — the same condition that lets a sole owner leave and close it that way instead.
Pressing Close this Organization… explains exactly what goes: its Teams, Boards, Topics, Tags, Swimlanes, Groups, OKRs and Events, permanently. Your own Tasks, Notes and Calendar are unaffected. To confirm, you type a phrase the product shows you, naming the Organization by its real name — the phrase comes from the server, never something you have to remember or guess the wording of — and the button stays refused until what you typed matches it exactly.
Customize email — what your team's messages say
Directly under the team mark in Team settings is Customize email, where a team sets what its invitation says and how every message from it looks. Only a Super Team Admin can change it. A team admin can read every word of it, but the controls are inert.
Empty means the standard message
Every wording field starts empty, and empty is a real answer — it means “send the standard wording”, not “send nothing”. Reset to default puts every field back to empty — there is no separate switch.
What you can set
- Messages come from — the name shown in the inbox. The sending address does not change and cannot.
- Invitation subject and Invitation message, the latter with the app's usual formatting bar.
- Above every notification — a short optional line riding on top of mention, assignment and share messages.
- An accent color, Font, and Show our logo — read by every message from the team.
Tokens: writing one message that fits everybody
Parts that differ per recipient are written as tokens, filled in when the mail sends: [Team], [Name], [Inviter], [Link], [App]. The buttons insert one at the caret in whichever field you last had open.
Images
Up to three, each its own row, placed top or bottom — an
https:// address or embedded data:image. Insecure
http:// addresses and SVG files are refused. The team mark rides separately
whenever Show our logo is on.
The preview
The panel beside the editor shows the composed message with your real team name, mark
and accent. The preview stays light even when you are in dark mode —
email is light in every mail client, so a dark preview would show nobody's real inbox —
and an https://
image shows as a labeled placeholder rather than loading. If somebody else changed
the template while you had it open, your save is refused rather than overwriting
theirs, with what you wrote kept in the boxes.
The team's colors, and your own
A team can publish one color of its own, and so can you. Where either exists you get a third theme option — Custom — beside Light and Dark. The two stack: your own color wins, and your team's applies when you have set none. Your own color is under Your theme color in Settings → Workspace — Save my color stores it, Use my team's default gives it back.
Only a team administrator sets the team's default, in Settings → Workspace under Team default theme. The application derives the whole palette from the chosen color, holding contrast ratios and keeping status-color hues distinct; the preview beside the picker is the derived palette rather than the color you chose, so what you approve there is what the team gets. Which of the three you look at is still your own choice, remembered in your browser.
Importing a spreadsheet someone else made
Team settings → Bulk Import is one door onto the Import dialog (the same one as Actions → Import… on a board, described
below). Import a file… opens it with Into set to the board the tab is on, Import history lists past
imports, and a file dropped on the box opens the dialog with that file chosen. A reader who administers nothing here is told there is nothing to import into. For a
spreadsheet with its own columns choose A task list with columns: it needs no AI, and it can also update tasks already on the board.
Dropping an Excel or CSV file is safe: a workbook renamed .csv is recognized by its contents, never read as text.
- Choose A task list with columns, then the file (
.csv,.xlsxor.xls) and which board it goes Into. - Check Columns. Headers this app knows —
title,due date,status— are matched automatically and marked matched by name. For anything else, press Map with AI, which reads your headers and five sample rows and proposes which column is which. If an earlier import into this board used the same headers, Use the columns from that file is offered. - Change anything wrong — every field is a dropdown.
- Read the Review: New, Will update, Unchanged and Not written, with a before and after for every task that would change. Untick any row, or choose Skip them, only add new to bring in only the new ones.
- Press Import. Then Undo, for 30 days, puts back what it changed and removes what it added, and leaves anything somebody has worked on since.
The AI proposes; you decide
Nothing is imported until you press Import, and the AI can never overrule a column matched by name. A task is matched to an existing one by its id, then its description, then its title; a row that matches more than one task is not written and says why, and a blank cell never changes anything. Columns with no equivalent here are listed rather than imported. Map with AI needs the API key from Tasks' Settings; without one the button is disabled and importing works by column name as always.
What is in an exported report
A report is a printable page, opening in a new tab, through your browser's own Save-as-PDF. There is one export: Export this board in the menu under your initials — it asks what to cover before it builds anything, so a report about one topic is that export with the topic filter on.
Roadmap is a little over half done, with the import spec the main thing outstanding. Security review has been blocked with Kate for two weeks and is the one item with no recent activity.
The report: a written summary, the figures, a completion bar, the rollup by topic and then by assignee, then every outstanding task with its latest comment. Completed tasks are listed at the bottom, and the scope you chose is stated under the title and again in the footer.
What the report contains:
- A summary paragraph — see the note below.
- Figures and a completion bar, segmented by status.
- A card per person, ordered by who has the most outstanding.
- Every outstanding task grouped by column, with assignee, due date, tags, description and last comment — or a note that there are none.
- Completed tasks at the bottom, with who finished them and when.
The summary needs an Anthropic API key
With a key saved in Tasks' Settings, the report opens with a short written summary. Without one, nothing else is missing. Archived tasks count toward the figures.
Choosing what goes in the report
Open Team settings → Preferences. Under What an exported report includes there are two switches: Latest update — one line under each task, the most recent comment, on by default — and Comments — the whole thread, off by default. Both are yours alone and remembered. A very long thread prints its most recent twenty comments and says how many it left out.
Exporting the board as a PDF
Export this board… in the menu under your initials is where an export starts. It asks what to cover before it builds anything:
- What is on screen now — exactly what the filters, search and date range show, across Board, Completed and Archived together. This is where it opens.
- On screen, without archived work — same selection, archived tasks left out.
- Every task on this board — ignoring every filter.
So filtering to one person and exporting asks you to confirm that is what you meant — the answer is not remembered between exports.
The scope picker. Each option carries the number of tasks it would cover, and the note under them says what no report contains.
Summarize a board or topic export
With an AI assistant configured, pressing Export also writes a short Summary at the top — a few paragraphs on where it stands, what is blocked or overdue, what has gone quiet. It is written automatically, with nothing to review before inclusion.
No one's name is sent. What goes to your assistant is each task's status, due date, a slice of description, and up to 140 characters of its most recent comment — never who it is assigned to or who commented. A very large export sends only the first 200 tasks (120 for a single topic).
With no assistant configured, or the request fails, the report still builds, the Summary block simply left out. Not offered from the All-boards view.
What no report contains
No scope includes attachments or checklists. Comment threads appear only if turned on in Team Settings → Preferences.
The report has these two sections beyond the figures:
- A "By topic" table — one row per topic with its own completion bar.
- Outstanding tasks grouped by topic, then by column, matching the board's order.
The report says what it covers
A filter is stated under the title ("Filtered report — 9 of 24 tasks on this board") and in the footer. The report does not follow the Board / Completed / Archived tab — it always covers all three.
Importing tasks from a file — Import… → Notes or a list of action items
Turns a Word document, spreadsheet or plain-text list of action items into tasks on a board and topic, reading it with the AI assistant so columns do not have to be labeled the way this app would label them. It is Actions → Import… on a board, then Notes or a list of action items under What is this file?. Only a board admin or team admin sees it — the import can create a topic. The older Task import wizard still sits behind that answer, so the steps below are unchanged. On an answer that uses your AI assistant the button after choosing the file reads Read the file; pressing it is the only moment the assistant is called.
It reads Word (.docx/.doc), Excel
(.xlsx/.xls), CSV and plain text. The older
.doc and .xls now work as well, including ones that are not
really Word or Excel at all — a page saved out of a wiki or web app often carries a
.doc name while actually being a web page inside, and those read fine too. A
table works best; a plain list of lines works too.
- Choose the file.
- Say where it goes. Pick the board — only ones you administer are offered — then a topic, or Create a new topic and name it. If you administer a board you have never joined, pressing Import adds you to that board so the tasks can be attached there, and that join is recorded in the audit trail.
- The assistant reads the file. A very large file is read in several passes, and each pass says which one it is on. There is a limit to how much of a file gets read in one import; past it, the preview says how many lines were not read, so you can split the file and import the rest separately. Cancel while it works and nothing is written.
- Review the preview, and choose what to bring in. One row per task found, each with a checkbox, plus Select all/Deselect all. The count above the list says how many of how many will be imported, and only the checked rows are.
- Press Import. It tells you how many tasks landed and in which topic.
What the assistant decides, and what the app decides
The assistant reports the names and timing words it finds. It never picks a person and never works out a date — the app does both.
- Owner and assignee are looked up in your team's people list. A name that matches nobody — or matches two people — is left Unassigned, and the row still imports. The preview says which rows those are.
- Due dates can be a real date or a time horizon ("2 weeks"). A date landing on a Saturday or Sunday moves to the Monday. Timing it cannot make sense of leaves the due date empty rather than guessing.
- Columns do not have to be named the way this app names them — the assistant maps by best judgment, and anything left over is kept in the task's notes.
Imported tasks stay off everybody's personal list, and you are the owner of record
Every imported task arrives with Show in My Tasks switched off; the owner can tick it in from the task itself. You, not the file's owner column, are the owner of record of every row — which is what lets you undo the import.
Undo, so you can fix the file and try again
Undo import removes exactly what that import added — the tasks, and the topic too if created — and nothing else. Needs an AI assistant configured.
Importing a whole project plan — Import… → A project plan
For a spreadsheet that holds a whole project: a checklist with a column
for each person, a week-by-week plan, a tracker or a risk log. In Import…
the first question is What is this file?; choose
A project plan, tracker or checklist and press Continue. STRIDE
reads how the file is laid out, groups the work into topics, and shows you all of it before
anything is written. Only a board admin or team admin sees it, and it needs an AI assistant configured. It reads Excel (.xlsx
or .xls) and CSV files up to about 10 MB.
- Choose the file. Press Choose a file, or drag it in. The file is read in your browser first, with nothing sent anywhere, and the Sheets found table lists every sheet, what it looks like and how many rows it has. Only the visible sheets that look like a list of work start ticked; tick any other to read it too. A sheet that is a contact list is never imported as tasks.
- Set up the import. Pick the Board. If the file schedules work in weeks, answer When is week 0?; otherwise Start date (optional) is the date any “N days after” timing is counted from, and left empty the tasks import without a due date. When the file shows what is done, choose how to treat it under Completion in your file. Anything we should know? is an optional note that steers the reading; it is not saved with the import. Estimated cost to your AI key sits beside the row, request and time estimates, and above $1 you tick a box to confirm it.
- Press Analyze. This is the first time anything is sent. A large file is read in parts, and the progress says which. Cancel reading writes nothing.
- Review the plan. See What the review shows below. Press the button at the foot, such as Import 120 tasks and 18 checklist items into 7 topics. It tells you what was added. If the import cannot finish, it removes what it had written, says so, and Back to review returns you to the plan.
The same capability is listed in the AI menu’s Explore AI capabilities as Turn a project plan spreadsheet into tasks to review.
Completion: a template, or a record of finished work
Treat it as a template: import every task as not started turns the file’s done marks into the schedule — a task marked done in week −6 becomes due in week −6 of your project. Keep what the file says is done imports done rows as complete, dated the week they were marked. In either choice a row the file marks not applicable is skipped, listed under Skipped with the reason; the review cannot add it back, so add it on the board afterwards if you want it.
What the assistant decides, and what STRIDE decides
The assistant reads the layout and proposes each row: what kind of row it is, a tidier title, its topic, who is named, and when it falls as an offset (“two weeks after the lease is signed”). It never returns a date, and never picks a person. STRIDE works out every due date from your start date, moving a weekend to the Monday, and matches each name once. Your team’s member list is never sent to the assistant, but the sheets you ticked are, including any names in them, using your own key or your organization’s.
What the review shows
- Every row has an answer. The summary counts rows as tasks, checklist items, merged and skipped; Skipped lists each skipped row with its reason. A file over 2,000 rows reads the first 2,000 and says how many were beyond the limit. A row the assistant could not read is marked Not analyzed, imports as a plain task in an Unsorted topic unless you untick it, and Retry these rows reads just those.
- People in the file. For each name, Who is this? offers your board’s people or Leave as text. A name matching two people is marked More than one match and is assigned to nobody until you choose; one with no match is marked Not on this board. Your choice applies to every row.
- Topics and tasks. Each topic shows its tasks. Rename a topic, edit a task’s title or move it to another topic, or untick it. A topic with the same name as one already on the board is reused; the others are created when you press Import. Group topics by and Change these (completion, start date) re-work the plan on screen without reading the file again, and your edits stay.
- How STRIDE read this file says which columns it took the task text, people, timing and completion from. A task whose timing came from the assistant carries a Timing: assistant chip. A due date already in the past is flagged.
- Re-run with new context reads the file again with what you tell it. The new plan replaces this one, including the edits you made here, and it says so first. Nothing is written to the board. Above $1 you tick a box to confirm the cost first, as in setup; the figure leaves out the layout unless you tick Read the layout again too.
- If an earlier import into this board was laid out the same way, setup offers Use the layout from that file, which skips reading the layout again and costs less.
Imported tasks stay off everybody’s personal list
As with the other import, every task arrives with Show in My Tasks switched off, and you are the owner of record. Everyone marked on a row who is on the board becomes a contributor; anyone who is not is named in the task’s description.
Undo, and Import history
The last screen offers Undo import. Later, Import history — Actions → Import history… on the board, and Import history in Bulk Import — lists the imports into that board (and its clones) with an Undo button for 30 days; All imports widens the list to every place you can see. Only the person who ran the import, or a team admin, can undo it. An import that never finished (a closed tab) shows as Didn’t finish and can be undone once an hour has passed.
After an undo, Back to history returns to the list.
- The plan screen shows what will be removed and what stays, and why; Continue then asks you to confirm.
- Undo removes only what nobody has touched since. A task stays, and is listed by name, if it was edited, has a comment or an attachment, had another contributor or watcher added, is linked to a note, an OKR, an email or an event, has a reminder, or was moved to another board. A topic goes only if the import created it and it is now empty.
- A reverted import stays in the history, with what it removed and what it kept. After 30 days the Undo button is replaced by The undo window has passed; the record is kept for a year.
Undo is the one place a team task is removed rather than archived, and only because nobody has worked on it yet.
Cloning a board or a topic
Set a board up once, then copy it for the next similar project. Clone board… is in the board’s Actions menu, and Clone… is on the board’s card in Board settings → Boards. Clone topic… is in a topic’s ••• menu on the board, and copies one topic, and optionally its tasks, onto this board or another board you administer.
- What comes across. Choose Structure only (the lanes, the topics as named and the tags), Structure and tasks, reset to To-do (the default), or Structure and tasks as they stand. Archived tasks, comments, files, watchers, reminders and links to notes, emails and events are never copied; a task’s own web links are. Completed tasks cloned as they stand stay completed, so they appear in the new board’s Completed tab.
- Assignments are cleared unless you choose Keep; a person who is not on the new board is cleared and named in the review. Due dates can be shifted to a new start date, kept or cleared, and STRIDE works the new dates out for you.
- Where. A board can go to its own team or another team in the same organization, with a new name, and by default with the same people and groups. A cloned topic’s tasks land in the lane of the same name on the other board, or in its first open lane.
- The review shows exactly what will be copied before you press Clone, and nothing is written until you do. A clone of more than 1,000 tasks is refused.
- Who. Cloning a board creates one, so only a Super Team Admin of the team it goes to (who also administers the board being copied) or the Organization Owner can do it. Cloning a topic needs you to administer both boards. A clone sends nobody an email.
- Undo is in the message after the clone and, for 30 days, in Import history, where the clone is listed as Cloned from “…”. It removes the copied tasks nobody has touched since, and the new board too when nothing on it changed. The board you copied from is never changed.