Notifications
The bell sits at the bottom of the sidebar, beside your profile picture and name. It carries an unread count and everything that has happened to you across every project. With the sidebar collapsed it sits just above your avatar. Inside a project, it's at the bottom of the Files panel, beside your account button.
Open it from the sidebar and two sections come first:
- Waiting on you - issues assigned to you and requests you can decide, such as "3 issues assigned to you" or "Oldest waiting 4 days".
- New in your teams - what's recently arrived in the teams you belong to.
Your newest notifications are listed underneath. The bell inside a project shows the list only; open it from the sidebar to see what's waiting on you.
The bell isn't the tasks tray. That's the Tasks button in the top-right corner, and it shows work that's running now.
The bell, the assignment digest and Send notifications now, then deciding a request from Requests.

What you get told about
| Notification | When |
|---|---|
| You were mentioned | Someone @-mentioned you in an issue thread |
| New comment | Someone commented on an issue assigned to you |
| Assigned to you | Someone assigned you a finding or a markup comment. Several at once arrive as one notification, such as "3 issues assigned to you in Kingsway", which opens My issues |
| A run finished | A check, checklist, audit, comparison, review or code upload you started has finished or failed - or a teammate cancelled it |
| A QA/QC run stopped | A QA/QC run made no progress for a long time and was stopped |
| Your chat reply is ready | A long chat reply finished, was stopped, or stopped with an error. By default this only appears when you weren't there to see it - see Choosing what reaches you |
| A checklist didn't start | A chat turn got a checklist ready to run but it wasn't launched, or the checks set to run on a project didn't start. Open it to launch them |
| Someone is waiting for approval | A new person signed up to your organization and needs an owner to let them in (owners only) |
| Someone joined | A new member joined your organization, or joined as a viewer (owners only) |
| A share was requested | Someone wants to share something with your team or the organization, or replied about a request - see How access works |
| A request was decided | Your request to share something, join a team, open a checklist, change a label or add to team or organization memory was approved or declined |
| A project was shared with your team | A project is now shared with a team you're in |
| Something you shared was deleted | Someone deleted an item you had shared |
| A file is already uploaded | You uploaded a file the project already has |
| A code book is with our team | A code you uploaded needs preparing by hand, and we're on it |
| A code book is ready, or published | A code book you uploaded is ready, or your request to publish it to the organization was decided |
| A code book is out of date | A newer edition of a code book your projects use was published, or it was amended, withdrawn or replaced |
| An RFI changed | An RFI you follow in Procore was updated |
What arrives by email
- Assignments arrive as one digest, not one email each. When someone assigns you issues, we wait until they have stopped assigning you anything on that project for 15 minutes, then send one email: "Sam assigned you 5 issues in Kingsway", listing the issues you still hold, most severe first, with View all in Issues. Each new assignment restarts the 15 minutes. If the issues were reassigned or closed in the meantime, no email is sent. Assigning yourself is emailed straight away.
- Share and join requests, and the answers to them, are emailed to whoever needs to act. Owners are also emailed when someone is waiting for approval to join the organization.
- Long runs email you when they finish. Any run you started that takes longer than 10 minutes sends an email when it's done, with the results attached where there are any. Runs that finish close together are bundled into one email. This is on by default: turn off Email me when my long-running tasks finish in Settings → Preferences, or use the mail icon on a single run in the tasks tray. You can also ask the chat to email you when what's running now is done.
- Long chat replies email you when they finish, if nothing reached you in the app.
Mentions, comments and code book currency notices stay in the app.
Sending assignment emails now
If you've just assigned a batch and want people to hear about it straight away, look under the search bar in the project's Issues tab. While your emails are waiting, a strip there reads, for example, "2 people have 5 new issues waiting to be emailed", with how long until they send by themselves. Press Send notifications now to send them all at once - one email per person. Only you see the strip for your own assignments.
The held emails strip under the Issues search bar, with Send notifications now
Choosing what reaches you
In Settings → Preferences (on the Settings tab of My Dashboard):
- Email me when my long-running tasks finish - on by default. Under it, Which issues should the email list? chooses Only what that run found (the default) or Every open issue on the project.
- When a chat reply finishes - Put it on the notification bell: Only when I missed it (the default) or Every reply, plus an optional Desktop notification. Email me when a long chat reply finishes and Email me if nothing reached me are both on by default.
What you can do with it
- Open one. Clicking a notification marks it read and takes you to whatever it's about.
- Mark all read. Clears the count in one go.
The unread count refreshes on its own while you work, so you don't need to reload to see something arrive.
On the legacy layout the bell has no Waiting on you or New in your teams sections. See The legacy layout.
Product updates
Updates, in the top-right corner beside Tasks and Help, shows what's new in Structured. Open it for the latest changes, or click View all updates for the full list. Click Email me updates to get them by email; Unsubscribe stops them.
