On this page

Enable and understand notifications

Set browser notification permission and distinguish it from in-app messages and completion emails.

Browser notifications, in-app messages, and completion emails have different controls. Enabling one does not automatically enable all of them.

Enable browser notifications

When your browser supports notifications, open the app's notification bell to inspect permission. The indicator is green for granted permission, red for blocked permission, and blue before a decision.

Choose Enable in the permission dialog and respond to the browser's prompt. Notifications Enabled confirms permission. Keep the app tab open while a response is being generated; notification permission does not make a closed tab continue the response workflow.

If the dialog says Notifications Blocked, open the browser's site-permission controls, allow notifications for ArchiBoost, and refresh the page after checking for unsaved work. Follow the instructions in the dialog. The app cannot override a browser denial. If the browser does not support notifications, the bell and permission dialog are unavailable.

Read in-app messages and badges

Success, warning, and error messages report the outcome or status of an action inside the app. Badges can draw attention to an item or state. Read the associated text before deciding whether to retry. These indicators do not require browser notification permission and are not proof that an email was sent.

Request completion emails

For a running zoning analysis, use Email me when it's done or Email me when offered and check its confirmation. QA/QC intake has a separate notification-recipient step. Those workflow controls determine the requested emails; the account Profile screen does not currently offer editable notification preferences.

Related

Still need help?Email us

Documentation