Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-03

Screen guide — the app map

Every screen in the app, where each one is in the menu, what you do on it, and the exact name of the button that starts the task.

On this page (3)

This category exists for a specific reason. Tutorials teach the task ("publish version 1"); references explain the concept ("what a version freezes"). What was missing was the simplest and most searched-for layer: the name of the button. Someone with the screen open doesn't need a concept — they need to know where to click.

Here, screen by screen, is the literal text of the interface: buttons, fields, steps, filters, status badges, and empty-state messages.

How this page stays true

A project test checks that every label cited here actually exists in the screen's code, and that every app screen has a page documenting it. A button renamed without the docs following along breaks the test — that's how this guide doesn't turn into fiction.

Where each thing is in the menu#

MenuScreenWhat it's forGuide
HomeOverviewWhat ran, what failed, and what it consumedOverview dashboard
HomeArchitectureThe data path, from source to decisionOverview and architecture
ETL/ELTConnectionsRegister access to a system, onceConnections screens
ETL/ELTPipelinesBuild, publish, and operate loadsPipelines screens
ETL/ELTRunsTrack runs and recover from failuresRuns screens
DataConsoleSQL with cost per runData console screen
DataGovernanceWho sees what, and what comes out maskedData governance screen
DataLineageWhere the number came from and what breaks if it changesLineage and impact screen
(address /datalake)Your datalakeThe three layers and where the data livesYour datalake screen
BIDashboardsCreate, edit, publish, and share dashboardsDashboards screens
BIConnect BIRead the data in Excel, Power BI, Looker, TableauConnect BI screen
AIReportsThe AI Analyst: a written report, deliveredReports screens
AIQueriesA question in plain language becomes SQLQueries screen
Account (avatar)SettingsProfile, people, keys, your own cloud, and two-step verificationSettings screen
Account (avatar)CreditsBalance, top-up, and statementCredits screen
Account (avatar)Costs & forecastHow much the month should costCosts & forecast screen
Account (avatar)Plans · PricingSubscribe to the plan; the unit pricePlans screen · Pricing screen
Account (avatar)Audit logWho did what, and whenAudit log screen
Account (avatar)SupportConversations with Aiô and ticketsSupport screen
Account (avatar)The whole menuThe avatar menu items, in orderAccount screens
(entry)Sign in, create account, onboarding, MFA, inviteBefore a workspace existsEntry screens

The three confusions this guide clears up#

They're the ones that generate the most tickets, and all three have the same shape: two similar-looking actions with different effects.

Looks like the same thingBut
Publish pipeline and Run nowPublishing freezes the definition and does not read or write anything. Running is what moves data.
Turn on schedule and Run nowTurning it on enables automation starting from the next occurrence; it doesn't trigger anything now.
Replace credential and Revoke credentialReplacing swaps the secret and keeps everything running; revoking deletes the secret and takes down the pipelines that depend on it.

Next task#

Related links