One data source and one member.
The source can be a CSV, a read-only warehouse role or the REST API. Alert rules, scheduled exports and the rest of the team can all wait until something is on screen.
26 short answers, each checked against the current release. Type it the way you would ask a colleague.
26 answers in 7 topics
One data source and one member.
The source can be a CSV, a read-only warehouse role or the REST API. Alert rules, scheduled exports and the rest of the team can all wait until something is on screen.
Most teams are reading a live board the same afternoon.
The slow part is agreeing what a customer means in your own data, and that is a conversation, not a setting.
Yes, from Settings → Workspace → Duplicate.
It copies boards, alert rules and role definitions and deliberately copies no data, so a second region starts set up and empty.
Someone who will still be here in a year.
Ownership can be handed over at any time, but a workspace owned by an account that has already been deleted needs a support ticket to fix.
18 percent off every paid plan.
Switching partway through a month credits the unused days against the annual invoice instead of refunding them separately.
Within 45 days of the invoice, we refund it in full.
After that, the workspace keeps the plan you bought until the twelve months are up, then moves to Free, the free plan. Your data stays where it is.
By the people who signed in during the billing month.
Invitations don’t count. A member who never logs in is never charged for, so inviting people generously costs nothing.
Yes, on Pro and Max, with 30-day terms.
Send the PO number before the first invoice and it is printed on every line from then on, which keeps payments from sitting unmatched.
Nothing breaks. The extra rows show up as one line on the next invoice.
Data keeps coming in, and the workspace owner gets an email on the day it starts, not at the end of the month.
Yes. Share that one board with them as a Viewer.
They see that board and its data, with no way to browse to anything next to it and no workspace-wide search.
Yes, on Max, for adding and removing people.
A new hire gets a seat on the next sync, and someone who leaves loses access in the same sync that marks them gone, so nobody has to remember to do it by hand.
Turn off the Export permission for their role.
Exporting is a permission, not a plan feature. With it off, the download buttons disappear instead of showing up and then failing.
Yes. Every change to settings, roles and thresholds goes into the audit log.
Each entry shows who made the change, the old value and the new one. Max keeps the log for seven years; other plans keep two.
Postgres, MySQL, BigQuery, Snowflake and Redshift.
Each connection uses a read-only role that you create, and Basalt never writes anything to a connected warehouse.
200 MB per file.
Match the columns once and Basalt reuses that on every later upload. The first fifty rows are previewed, so a bad date format is caught before anything is saved.
Every hour on Basic and every fifteen minutes on Pro.
Max can also refresh on demand through the API, which is how most teams tie a refresh to the end of their own nightly job.
The board keeps its last good version and shows a banner naming the missing column.
It won’t quietly plot zeros, because a chart that silently reads zero is worse than one that stops.
Yes. When two rules could fire, the narrower one wins.
A rule can cover one board, one segment or the whole workspace. That is how one workspace serves two departments with nothing in common.
Email, Slack, Microsoft Teams, PagerDuty or a webhook, and several at once.
If a delivery fails, it is retried for an hour and then written to the rule’s own log.
The number crossed the threshold, came back, then crossed again.
That counts as two events, which is correct but noisy on a jumpy metric. Set a cool-down on the rule and only the first of a run is sent.
Yes, weekly or monthly, to people who don’t need a Basalt login.
The PDF uses the filters the board had when you scheduled it, not whatever filters it happens to have when it runs.
Each recipient’s own, if they have a Basalt profile, and the workspace’s otherwise.
That is why one schedule can arrive an hour apart for two people on the same list, and why it shifts with daylight saving time.
A million rows for CSV and 50,000 for Excel.
Past either limit, the export is split into numbered parts that are sent together, instead of failing at the end of a long run.
No. Basalt runs in your phone’s browser and can be added to the home screen.
It works on screens as narrow as 360 pixels on iOS and Android, which is one less thing for your IT team to roll out and keep updated.
Boards you opened in the last day stay readable for about four hours.
Anything you acknowledge while offline is saved and sent as soon as you are back online.
Max workspaces tie each session to an IP address by default.
Switching from mobile data to office Wi-Fi ends the session. An admin can turn this off for staff who move between networks all day.
Send it to the team. We read every question sent from this page, and the common ones end up here.