Notifications and their settings
On this page
| Where | The bell in the top bar (Notifications / Известия) → panel; See all notifications (Виж всички известия) → full page /notifications; settings behind the gear in the panel or the Notification settings button on the full page. |
|---|---|
| Who can | Every company member. There is no separate permission: you receive notifications only about projects and items you already have access to, and each row says why it reached you. Settings are personal. |
| Related | The interface: sidebar, top bar, switching, Reviewing, approving, countering, rejecting, Contracting schedule and packages, Sharing, comments and mentions |
How notifications work
- Per company. You see the notifications of the company selected in the sidebar. Without a selected company the panel says "Notifications are kept per organization, and none is selected yet." (Известията са отделни за всяка организация, а още не е избрана нито една.) with the button Choose an organization (Изберете организация).
- Two tabs. Needs action (Изисква действие) holds items that wait for you to do something; they have a deadline when there is one, show as overdue and carry a Review (Прегледай) button. Activity (Активност) holds everything else: something happened, nothing is asked of you.
- The counter on the bell shows how many items need action from you, not how many are unread. Reading an item does not lower the counter; doing the work does. When nothing is waiting, there is no counter.
- Live. The counter, the panel and the page update by themselves when something happens; you do not need to reload.
- No confirmations. Marking as read and changing a setting show no confirmation message; you see the result on screen.
- Not deletable. You cannot delete a notification. Notifications leave on their own (see "How long notifications are kept").
The bell panel
Click the bell to open the panel. It contains the heading Notifications (Известия), a gear button Notification settings (Настройки на известията), Mark all as read (Маркирай всички като прочетени), the two tabs and, at the bottom, See all notifications (Виж всички известия), which opens the full page. The panel is for a quick look; the full page adds search, filters and history.
Empty tabs say "Nothing is waiting on you. The ball is in someone else's court." (Нищо не чака вас. Топката е в другите.) and "No new activity on your projects." (Няма нова активност по вашите проекти.). Older items load with Load more (Зареди още).
- The bell with the counter of items that need your action.
- Mark all as read.
- The gear that opens Notification settings.
- The Needs action and Activity tabs.
- A notification row with its reason line and its action button, here Open the package.
- See all notifications, which opens the full page.
Anatomy of a notification row
| Part | What it tells you |
|---|---|
| Actor | The person who caused it, or "BuildColab" for automatic notifications such as reminders. |
| Sentence | What happened, with the people, the item and the project, for example "Pay application #3 for {contract} is awaiting approval ({amount})". |
| Time | How long ago, for example "just now" (току-що). |
| Unread / Непрочетено | A dot until you open the row. |
| Due: {date} / Срок: {date} | Only on Needs-action rows that have a deadline. After it passes: Overdue (Просрочен) or Overdue by N days (Просрочен с N дни). |
| Reason: … / Причина: … | Why it reached you (see the table below). |
| Button | Review (Прегледай) on Needs-action rows. On Activity rows a button that names the destination: Open the offer (Отвори офертата), Open BoQ (Отвори КСС), Open project (Отвори проекта), Open file (Отвори файла), Open folder (Отвори папката), Open the package (Отвори пакета). |
Clicking a row marks it as read and opens the exact item: the offer request, contract, payment application, bill of quantities (BoQ), file or package. A row with nothing left to open (for example a very old record) is only marked as read.
| Reason (EN / BG) | Meaning |
|---|---|
| you are the responsible person / вие сте отговорник | You are responsible for the item, for example the person responsible for an offer request or a contracting package. |
| you are the approver / вие сте одобряващ | You approve this change order or payment application. |
| you are responsible for this pay application / вие сте отговорник за отчета | You were assigned to the payment application. |
| you are a member of the project / член сте на проекта | You are on the project team with access to that module. |
| it concerns you / засяга вас | The event is about you, for example you were added to a project. |
| you are a company administrator / администратор сте на фирмата | You receive it as an administrator of the company. |
| you have access to the file / имате достъп до файла | A file or folder you can access changed. |
| you own the file / собственик сте на файла | Someone commented on your file. |
| you are part of the discussion / участвате в дискусията | Someone replied in a comment thread you take part in. |
| you were mentioned / споменати сте | Someone mentioned you with @ in a file comment. |
| you wrote the comment / автор сте на коментара | Your comment was resolved. |
| you uploaded the file / вие качихте файла | The 3D/BIM model you uploaded finished or failed processing. |
Grouped rows
Some events are merged into one row instead of one row per change. BoQ edits are grouped per BoQ per day: "{person} made 14 changes to BoQ "{name}" — project "{project}"", or "{person} and 2 more made…" when several people edited. File uploads, new versions, comments and deletions are grouped the same way. Click Show the changes (Покажи промените) to see the individual changes, for example "{position} · Quantity: 120 → 145", "Price: … → …", "Added: …" (Добавена позиция) or "{n} items deleted"; Hide the changes (Скрий промените) folds them again. A group stores at most 20 changes; beyond that you see "{n} more changes" (още {n} промени). Next to the time, active group (активна група) means the next change will be added to this row; group closed (групата е затворена) means the next change will start a new row. A group closes when you read it or when it reaches 20 changes. Expanding the changes does not mark the row as read.
Done items
When the work behind a Needs-action item is done (the payment application is approved, the offer request is answered), the row does not vanish at once. It moves to the bottom of the tab with the pill Done (Извършено) and the note "leaves this tab after 24 h" (излиза от таба след 24 ч), so you can see what was cleared, including work a colleague did for you: an action item is resolved for everyone it was sent to. At most 20 done items are shown; all of them remain in the history.
Pop-up notifications
A new notification can pop up as a card in the top-right corner of the screen (your own confirmations, such as "Saved", appear at the bottom-left). This happens only if the item's section is set to Pop-up notification for that project, which is the default.
- At most three cards are shown at once.
- Cards for items that need action stay until you close them; other cards close by themselves after 6 seconds.
- Click a card to open the item and mark it as read; Dismiss (Затвори) closes the card without opening it.
Every notification, by section
The table lists every notification BuildColab sends, grouped by the section (module) that controls it in the settings. "Needs action" rows count on the bell until the work is done.
BoQ (КСС)
| Notification | Sent when | Who receives it | Tab |
|---|---|---|---|
| {person} imported BoQ "{BoQ}" ({n} items) — project "{project}" | A BoQ import from Excel finishes. | Project members with access to offers and BoQs. | Activity |
| {person} made {n} changes to BoQ "{BoQ}" — project "{project}" | Positions are added, deleted or their description, quantity or price changes. Grouped per BoQ per day. | Project members with access to offers and BoQs. | Activity |
Offer requests (Запитвания)
| Notification | Sent when | Who receives it | Tab |
|---|---|---|---|
| Received an offer request "{request}" — project "{project}" | A client sends your company an offer request. | The responsible person in your company, among members with the Received bid requests permission. | Needs action |
| The offer request "{request}" was revised (added: {a}, removed: {r}, unchanged: {k}) — project "{project}" | The client issues a new revision of a request you received; a new answer is expected. | Same as above. | Needs action |
| The offer request "{request}" was updated — project "{project}" | The client changes the name or note of a request already sent to you. | Participants still taking part in the request. | Activity |
| The deadline of the offer request "{request}" moved: {old} → {new} | The client changes the deadline. | Participants still taking part. | Activity |
| The documents of the offer request "{request}" changed (added: {a}, removed: {r}) | The client adds or removes attached files. | Participants still taking part. | Activity |
| The offer request "{request}" was withdrawn by the client[: "{reason}"] | The client withdraws the request, optionally with a reason. | Participants still taking part. | Activity |
| Your offer for "{request}" was chosen — project "{project}" | The client awards the request (wholly or partly) to your offer. | The winning participant. | Activity |
| {partner} answered the offer request "{request}" with an offer | A partner submits an offer to a request your company sent. | People who can act on the request (edit right on Outgoing bid requests); other project members with access to offers get it as lower-priority information. | Activity |
| {partner} requested an update for "{request}" | The client asks your company to update an offer you submitted. | The responsible person in your company. | Needs action |
| {partner} responded to the update request for "{request}" | A partner answers the update you asked for. | Project members with access to Outgoing bid requests. | Activity |
| Send the request for quotation / Collect the offers / Choose the contractor / Sign the contract for package "{package}" — project "{project}" | A contracting-schedule step of a package is coming up. How many days before is set in the package's reminder setting. | The package owner; if the package has no owner, the people who can edit the contracting schedule. | Needs action |
| The request for quotation for package "{package}" was not sent on time (or: offers not collected, no contractor chosen, contract not signed on time) | The deadline of a package step has passed. | Same as above. | Needs action |
| The schedule moved the start of package "{package}" {n} working days later / earlier | A change in the construction schedule moved the date the package is anchored to. The package does not change its dates by itself: open it and apply or ignore the change. | Same as above. | Activity |
No notification is sent when a partner declines your request, when a request is closed, or to participants whose offer was not chosen; they see the outcome on the request itself.
Contracts (Договори)
| Notification | Sent when | Who receives it | Tab |
|---|---|---|---|
| {partner} sent you a contract proposal for {contract} | A client sends your company a contract proposal. | The responsible people. | Needs action |
| {partner} accepted / declined the contract proposal for {contract} | The other side answers your proposal. | Project members on your side. | Activity |
| A change order was submitted for {contract} ({amount}) | The other side submits a change order. | The approvers. | Needs action |
| {partner} accepted / declined the change order for {contract} | The other side answers your change order. | Project members on your side. | Activity |
| {partner} replaced the change order for {contract} with a newer one | A submitted change order is superseded by a newer one. | Project members. | Activity |
Reports (Отчети)
| Notification | Sent when | Who receives it | Tab |
|---|---|---|---|
| Pay application #{n} for {contract} is awaiting approval ({amount}) | A payment application is submitted to your company. | The approvers get it as an action; other project members with the Reports permission get it as information. | Needs action / Activity |
| You have been assigned as approver for pay application #{n} | Someone assigns you to a payment application. | The assigned person. | Needs action |
| Counter-proposal on pay application #{n} ({amount}) | The approver answers your payment application with a counter-proposal. | The responsible people on the submitting side. | Needs action |
| Pay application #{n} was approved / "Your pay application was approved. Invoicing is next." | A payment application is approved. | Project members with the Reports permission on both sides. | Activity |
| Pay application #{n} was rejected | A payment application is rejected. | Project members with the Reports permission. | Activity |
| Pay application #{n} was withdrawn | The submitter withdraws a payment application. | Project members with the Reports permission. | Activity |
File manager (Файлов мениджър)
| Notification | Sent when | Who receives it | Tab |
|---|---|---|---|
| {person} uploaded {n} files to "{folder}" | Files are uploaded to a folder you can access. | People with access to the folder. | Activity |
| {person} uploaded {n} new versions of "{file}" | A new version of a file is uploaded. | People with access to the file. | Activity |
| {person} restored an earlier version of "{file}" | An older version is restored. | People with access to the file. | Activity |
| {person} shared "{file}" with you | Someone shares a file or folder with you. | The person it was shared with. | Activity |
| {person} left {n} comments on "{file}" | Someone comments on a file. | The file's owner. | Activity |
| {person} posted {n} replies in a discussion on "{file}" | Someone replies in a comment thread. | The people in that thread. | Activity |
| {person} mentioned you in a comment on "{file}" | Someone writes @your name in a comment. | The person mentioned. | Activity |
| {person} resolved your comment on "{file}" | Your comment is marked as resolved. | The comment's author. | Activity |
| {person} deleted "{file}" / {n} items | Files or folders are deleted. | People with access. | Activity |
| The model "{file}" is ready to view / could not be processed | Processing of an uploaded 3D/BIM model finishes or fails. | The person who uploaded it. | Activity |
Team (Екип)
| Notification | Sent when | Who receives it | Tab |
|---|---|---|---|
| {person} added you to project "{project}" | You are added to a project team. | The person added. | Activity |
Schedule (График) and Work tasks (Работни задачи)
These two sections already have a row in the settings, but no notifications are sent for them yet. Work tasks inform people by e-mail instead: when a task is assigned to you, when someone comments on a task you created, are assigned to or commented on, and when you are added to a board. These e-mails are not affected by the notification settings. See Tasks: details, subtasks, comments, activity.
The full notifications page
Click See all notifications at the bottom of the bell panel to open /notifications, titled Notifications (Известия) — "Everything on your projects, in one place." (Всичко по вашите проекти на едно място.). There is no sidebar entry for it.
- Project (Проект) filter: All projects (Всички проекти) or one project.
- Section (Модул) filter: All sections (Всички модули) or one of the eight sections. Both filters apply to the whole list on the server, so Load more keeps loading the narrowed list.
- Search: "Search by person, item or project" (Търси по човек, обект или проект). The search looks only through the notifications loaded so far. If nothing matches you see "No matches among the notifications loaded so far. Load more to keep searching." — click Load more and the search continues.
- Mark all as read: with a filter active, it marks only what the filter shows ("…only the ones shown by the current filter"). The search is not applied: it marks everything under the current filter.
- History (История) and Notification settings buttons open side panels next to the list.
- The search field, which searches the loaded notifications.
- The Project filter.
- The Section filter.
- Mark all as read, limited to the current filter.
- The Notification settings button.
- The History panel with the Item, Reason and Channel columns.
History
The History (История) panel is a record of the notifications of the last 90 days: what was sent, why and how. It follows the same filters and tab as the list. Drag its edge to make it wider; Close the history (Затвори историята) hides it. It is a record only; nothing can be done from it.
| Column / value (EN / BG) | Meaning |
|---|---|
| Item / Обект | The offer request, contract, payment application, project or file concerned. |
| Reason / Причина | The same reason as on the row. |
| Channel / Канал | "in the app" (в софтуера) or "in the app + email" (в софтуера + имейл). |
| Statuses | Unread (Непрочетено), Read (Прочетено), Done (Извършено), Not done (Неизвършено), Overdue (Просрочено). |
If new notifications arrive while you scroll, you may see "The history changed while you were reading it, and some rows are missing here." (Историята се промени, докато я преглеждахте…). Click Reload (Презаредете).
How to mark notifications as read
- Click a row: it opens the item and marks that row as read.
- Click Mark all as read in the bell panel: all unread notifications of the selected company are marked as read, in both tabs.
- Click Mark all as read on the full page: only the notifications shown by the current Project and Section filters are marked.
Notification settings
Settings decide how loudly a notification arrives, not whether it exists. They are personal and are set per project, because the same section can be essential on a project you run and noise on a project you only follow.
How to change your notification settings
- Click the bell, then the gear Notification settings (Настройки на известията). On the full page, click Notification settings instead. To return to the list in the panel, click Back (Назад).
- Choose a project in Choose a project (Изберете проект). Only projects you take part in are listed.
- For each section, click one of the three icons: Pop-up notification, Counter only or No notifications. To set all eight sections at once, use the All sections (Всички модули) row at the top; it shows a common value only when all eight sections match.
The change is saved at once, without a confirmation message.
| Delivery mode (EN / BG) | What happens to a new notification |
|---|---|
| Pop-up notification / Изскачащо известие (default) | It pops up as a card, appears in the list and raises the counter where relevant. |
| Counter only / Само брояч | Nothing pops up; it appears in the list and raises the counter where relevant. |
| No notifications / Без известия | It is hidden from the list, the counter and the history. Exception: Needs-action items always stay in the tab and the counter (they just do not pop up). |
The panel says so itself: "Notifications that need action always stay in the tab and in the counter, whatever you choose." (Известията „Изисква действие" винаги стоят в таба и в брояча, каквото и да изберете.). So you can safely mute a whole section: an obligation never disappears, it only stops interrupting.
| Section (EN / BG) | What it covers |
|---|---|
| BoQ / КСС | BoQ imports and edits. |
| Offer requests / Запитвания | Received and revised requests, changes to a sent request (name, deadline, documents, withdrawal), chosen offers, received offers, update requests and answers, and every contracting-schedule reminder for packages. |
| Contracts / Договори | Contract proposals and change orders, and their answers. |
| Schedule / График | The construction schedule. No notifications are sent here yet. Muting it does not mute package reminders. |
| Reports / Отчети | Payment applications: submitted, assigned, countered, approved, rejected, withdrawn. |
| File manager / Файлов мениджър | Uploads, versions, sharing, comments, mentions, deletions and 3D/BIM model processing. |
| Work tasks / Работни задачи | Reserved for task-board notifications; none are sent yet (task boards use e-mail). |
| Team / Екип | Being added to a project team. |
Contracting-schedule reminders follow the Offer requests row, because every package step is a tender step. Approaching and overdue package steps are Needs-action items and cannot be muted; only the "schedule moved the start of the package" information follows a No notifications setting.
- The back arrow returns to the notification list.
- The project picker (Choose a project): the settings below apply to this project only.
- The All sections row sets all eight sections at once.
- One section row with its three delivery icons: Pop-up notification, Counter only, No notifications.
Rules of the settings
- A setting applies only to notifications created after you change it; existing ones are not re-evaluated.
- Notifications that belong to no project, such as "Received an offer request", always use the default, Pop-up notification.
- Settings affect only notifications inside BuildColab. E-mails that features send on their own (for example offer-request invitations or task-board e-mails) are not affected.
- If the panel cannot load, you see "The settings could not be loaded." (Настройките не можаха да бъдат заредени.) or "The projects could not be loaded."; with no projects yet: "There are no projects to configure yet." (Още няма проекти за настройване.).
How long notifications are kept
| Notification | Kept for |
|---|---|
| Read notification | 90 days |
| Unread notification (including ones hidden by No notifications) | 180 days |
| Needs-action item that has been done | Leaves the tab after 24 hours; deleted 90 days after it was done |
| Needs-action item still open | Never deleted while the work is still open |
| History panel | Shows the last 90 days |
Common questions
Why does the bell show 3 when I have read everything?
The counter counts items that need action, not unread items. Three things are still waiting for you, for example a payment application to approve. Open the Needs action tab and do the work; the counter drops when each item is done.
I set a section to "No notifications" but payment applications still appear. Why?
Items that need your action, such as a payment application awaiting your approval, always stay in the Needs action tab and the counter. No notifications only stops them from popping up. Informational notifications of that section are hidden.
How do I stop pop-ups for one project only?
Open the bell, click the gear, choose the project and set All sections to Counter only. Other projects keep their own settings.
A colleague approved the payment application. Why is it still in my Needs action tab?
It is shown as Done for 24 hours so you can see that it was handled. It no longer counts on the bell and leaves the tab after 24 hours.
Do I get notifications by e-mail?
Notifications are delivered inside BuildColab: the bell, the panel, the full page and the pop-up cards. Individual features send their own e-mails, for example invitations to a company; one e-mail to each partner the first time an offer request is sent to it (later changes, revisions and withdrawals arrive as in-app notifications only); e-mails when a contractor accepts or declines a contract proposal and for change orders (a new contract proposal itself is in-app only); and task-board assignments and comments. The notification settings do not change those e-mails. Each e-mail is in Bulgarian or English: the recipient's profile language when the address belongs to a BuildColab account that has one, otherwise the language of the person whose action sent it, otherwise Bulgarian (task-board e-mails: the recipient's profile language, else Bulgarian).
My search finds nothing, but I know the notification exists. Why?
Search looks only through the notifications loaded so far. Click Load more until older notifications are loaded, or narrow the list with the Project and Section filters, which apply to everything.
Can I delete a notification?
No. Notifications leave on their own: done action items after 24 hours from the tab, and all notifications according to the retention periods above.
Why don't I see notifications from my other company?
Notifications are kept per company. Switch company with the Organization chip in the sidebar to see that company's notifications.