GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Cube Documentation home page
  • Demos
  • Changelog
  • Community
  • Get Started
  • Documentation
  • Admin
  • Embedding
  • Reference
  • Cube Core
  • Recipes
  • API
  • Preferences
  • Inbox

This view

  • Original page
  • New address

GeezerVison is showing docs.cube.dev — Inbox - Cube Documentation

The inbox collects notifications about events in Cube that concern you: a teammate mentions you in a comment, an alert fires, a new Cube version is released, and more. Each user has their own inbox. It is the same in every deployment of the account.
To send a dashboard by email or Slack after a scheduled refresh, see Notifications.

​
Opening the inbox

Click Inbox at the bottom of the sidebar. When you have unread notifications, its icon turns purple and a badge shows how many. The inbox has two panes. The left pane lists your notifications, newest first, under Today, Yesterday, or a date. Its header reads Inbox, followed by the number of unread notifications. When you have read everything, no number is shown. Click a notification to see it in full in the right pane. Until you select one, the pane shows No notification selected. Click Open to go to what the notification is about. New notifications appear as they arrive. You don’t need to reload the page.

​
Notification types

NotificationWhen you get itWho gets itOpen goes to
MentionSomeone mentions you in a dashboard comment, or edits a comment to add a mention of youEach mentioned user, except the authorThe comment on the dashboard
ReplySomeone replies in a dashboard comment thread you wrote inEveryone who started or replied in the thread before, except the author. A reply that also mentions you sends a mention insteadThe reply on the dashboard
AlertAn alert fires or resolvesRecipients of the alert who are Cube usersThe deployment’s Status page
BudgetUsage crosses a budget thresholdUsers who get the budget’s notifications and have a Cube accountNo Open button
Scheduled task runA run of a scheduled task finishes or fails, if the task notifies by InboxThe task’s recipients who can view the task and read its deployment. For a failed run, only its creator, if they are a recipientThe run’s chat thread. If the run failed before it started a thread, the task’s page.
New Cube versionA deployment runs an older version than the latest one on its update channelAdminsThe deployment’s Settings page
End of supportA deployment runs a Cube version that is about to reach end of support. You get one notification with each end-of-support email.AdminsThe deployment’s Settings page
Production build failedA build of a deployment’s production branch failsThe user who started the build. If no user started it, for example a Git push, or that user is deactivated: adminsThe build and its logs
Dashboard reviewSomeone requests a review of a dashboard or a new revision of it, comments on the review, approves, requests changes, or publishes the reviewEveryone taking part in the review, except the person who acted: the requester, the reviewers, and anyone who commented. Only those who can still view the dashboard.The review page. For a published review, the published dashboard.
Scheduled refresh failedA scheduled refresh of a dashboard fails, or its notifications don’t reach some or all recipientsThe user who created the scheduleThe dashboard
Access requestSomeone requests access to a workbook, a dashboard, a folder, or a chatThe owner and up to 9 users with direct Full access, 10 at most. For a chat, only its ownerThe item, with its Share dialog open on the request
Access request declinedSomeone declines your access requestThe requesterThe item’s no-access page, where you can request access again
Shared with youSomeone shares a workbook, a folder, or a chat with you, or gives you more access to one, directly or through a groupThe user, or each member of the group, except the person who shared itThe workbook, or its dashboard if it is published. The folder or the chat.
Model syncA dbt pull or push, a Snowflake semantic view pull or push, or a Databricks metric view publish finishes or failsThe user who started the sync. For an automated dbt sync, the users on its notification list. Otherwise: adminsThe IDE. If the sync made a branch to review, the changes on that branch.
AI tokensThe account runs out of AI tokens, or an automatic AI tokens top-up failsAdminsThe Billing page
Invite acceptedA user accepts your invite and joins the accountThe admin who sent the inviteThe new user’s page
Report deliveryA report delivery fails or starts working againThe owner of the delivery, if the delivery has Inbox notifications on. While the owner’s Google account can’t open the spreadsheet, also admins, at most once a day, whatever the delivery’s settingsThe delivery
ChangelogCube publishes a new changelog entryAll usersUsually no Open button, since the entry shows in full in the right pane. If the entry is no longer in Cube, Open goes to the public Cube changelog.
A scheduled task run notification has the task name in the title, for example Daily signups finished or Daily signups failed. For a finished run, it shows the start of the agent’s answer. If the answer has no text, for example when the run only built a chart, it shows how the run started and how long it took. For a failed run, it shows the error. For a run that a conditional task’s condition started, the title reads Daily signups: condition met, and it shows the change the check found instead of the answer. Only the creator’s notification shows the figures; everyone else’s says that the condition started to hold. Mentions and replies in comments, shared items, and access requests also arrive by email, unless you turn that off under Notifications on the Preferences page. The inbox does not send other notifications by email or Slack. Alerts and budgets send their own email, as set up on the alert or budget, and end-of-support notices come with their own email, as do dashboard review notifications. A scheduled task can also notify by email or Slack, as set up on the task. A report delivery can also notify its owner by email or Slack, and emails admins while the owner’s Google account can’t open the spreadsheet.

​
Read and unread

A new notification is unread. It has a purple dot and a bold title. When you select a notification, it becomes read. Opening the inbox does not mark anything read. To change the state of one notification without selecting it, open its ⋮ menu or right-click it, then choose Mark read or Mark unread. The ⋮ menu shows when you hover over a notification, and it is always visible on a touch screen. To mark all notifications read, open the ⋯ menu in the header and choose Mark all read.

​
Deleting notifications

To delete one notification, open its ⋮ menu or right-click it, then choose Delete. Cube deletes it immediately, without a confirmation. To delete many notifications at once, open the ⋯ menu in the header:
  • Delete read notifications deletes every notification that you have read.
  • Delete all notifications deletes every notification, read or unread.
Cube asks you to confirm both actions. You can’t undo a delete.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.