The text in quotes and in bold is the text on screen.
Where it is: avatar menu (top right corner) → Settings, or directly at Settings.
It's the workspace owner's screen. People who joined as members and only use dashboards go straight to the BI area and don't see this screen.
The title is Settings. On the left are five sections, in two groups:
| Group | Section | What it's for (text on screen) |
|---|---|---|
| Personal | Profile | "Your preferences — they apply to you, not to the rest of the team." |
| Personal | Help | "Support, documentation and how to get help." |
| Administration | Access | "Who is in the workspace, with which role, and what each role can do." |
| Administration | Integrations and keys | "Connections to other systems, the service account and programmatic access keys." |
| Administration | Workspace | "The customer's environment: workspace details, own cloud and account deletion." |
On a phone, the sections become tabs that scroll horizontally.
Profile#
- Language / Idioma — choose between Portuguese and English. The choice is saved in your browser and applies only to you.
- Appearance — the interface has a single, light theme. The dashboards' theme (colors, fonts, and visual style) is something else: it's set in the editor of each dashboard, in Dashboards.
Help#
- Support — when the workspace is linked to the platform's central account, a form for opening a ticket appears: Subject, Description (optional), and Priority (Low, Normal, High, or Urgent), with the Open ticket button. Without that link, the card explains what's missing and who can fix it.
- Documentation — the Open the documentation link takes you to these pages.
The fastest way to ask for help
Access — invite a person#
The card is Users & permissions. Nobody receives a password: the invitation is a single-use activation link, and the person creates their own credential when opening the link.
Open the Access section
In Settings, click Access (Administration group).
Fill in the invitation
In the Invite user form, fill in Name and Sign-in email. Choose the Role in the workspace: Administrator, Member, or Viewer.
Decide on two-step verification
Check MFA enabled for this user if this person should use a code from the authenticator app to sign in.
Generate the invitation
Click Invite and generate link. While saving, the button shows Saving….
Hand over the link, if the email doesn't go out
The screen says whether the email was sent. If it wasn't, use Copy link and send the link through a trusted channel. Generate new link replaces the link (the previous one stops working) and Hide hides the box.
At the end you should see: the person in the list with the Pending invite badge and the sentence "Pending invite, valid until …".
What you can do with each person
| Button | What it does |
|---|---|
| Deactivate / Reactivate | Blocks or restores access, without deleting the record |
| Resend invite | Issues a new link; the previous one stops working immediately |
| Cancel invite | Undoes an invitation that hasn't been accepted yet |
| Delete | Removes the person from the workspace |
The status badges are Active, Disabled, Pending invite, Invite to reissue, and Active (legacy link). Each person also shows MFA: yes or MFA: no.
What each role can do
Right below the invitation are four read-only cards — they show, they don't change anything:
- Roles and what each one does — each role with the number of actions it allows.
- What this person can do today — click someone's name and see, action by action, what they can do, and under Data this person sees the tables and columns that are hidden or masked for them.
- Hide, mask and deny are different things — Hide makes the item disappear, Mask shows the data disguised, and Deny blocks the action.
- Where each rule is applied — Role in the workspace, Access group (data governance), and Per-item BI permission appear as Applied on the server. The Permission boxes on the member's record appear as Informational only.
To understand roles in detail, see Roles (RBAC).
Integrations and keys#
Three cards:
- Integrations — the status of the environment's connections, with the Connected or Not configured badge.
- Service Account — a service account just for your workspace, for external tools that ask for that type of key. Buttons: Download key (JSON), Copy key (JSON), and Rotate key. Rotating invalidates the current key, and the screen asks for confirmation first.
- API keys — the key you take to Power BI, Looker Studio, Tableau, or Excel. Read-only access, only to your workspace, and every use is recorded.
Create an API key
Open the card
In Settings → Integrations and keys, scroll down to API keys.
Start the key
Click New key and give it a name that says where it will be used (for example, "Power BI — Finance").
Create it
Click Create key.
Copy it now
The key appears only once: "Copy and save it now — for security, it won't be shown again." Right below, ready to paste, come the OData feed URL (Power BI / Tableau / Excel) and a REST example (curl).
At the end you should see: the key in the list with the Active badge and "Last used: never". To cut off a tool's access, click Revoke — the key stops working immediately and doesn't come back.
Right after creation, the API keys card shows the full key with the warning to copy it now and, below it, the OData feed URL and the REST example (curl) — that's why this screen has no screenshot: the image would publish a key.
More details in Credentials and rotation.
Workspace#
The Workspace card shows Name, Customer ID, Subscribed plan, Datalake project, and Data region. The last two are set up by the platform and can't be changed here. If there's no subscription, the plan appears with the Sign-up reference — no subscription badge.
Own cloud (Enterprise)
The Own cloud (Enterprise) card is for those who want the datalake running in the company's own cloud account — the data stays in your account and the cloud is billed directly to you by the provider. Without it, the workspace uses the platform's shared environment. The badge says Active or Disabled.
Here the provider's name appears, and that's on purpose
This is the only part of the screen that names the cloud provider (Google Cloud, with BigQuery and Cloud Storage): the project is yours, and you'll open its console to grant the permissions.
The card has the How to set it up (step by step) guide, in five stages:
Create (or choose) the project in Google Cloud
Write down the Project ID. The project needs active billing.
Enable the APIs
Enable the BigQuery API and the Cloud Storage API.
Create the service account
Give it the BigQuery Admin and Storage Admin roles on the project.
Generate the JSON key
Download the file and paste its contents into Service account key (JSON). The key is stored encrypted and never shows up again.
Save and activate
Fill in Project ID (your GCP project) and, if you want, Landing bucket (optional) — if left blank, we create it. Click Test and activate own cloud. Then open Datalake and click Provision datalake to create the three layers in your project.
At the end you should see: the Active badge and a success message. To change the key later, paste the new one and click Save new configuration. To go back to the shared environment, Disable (back to shared).
Danger zone — Delete account and data
Permanent after 30 days
Deletion erases the workspace and its settings, the connected sources, the queries and dashboards, the datalake data in all three layers (bronze, silver, and gold), cancels the subscription, and deletes your user account. To request it, type EXCLUIR (or the workspace name) and click Delete account and all data (in 30 days).
The request opens a 30-day grace period: nothing is deleted, the environment keeps working (you can query and export) and only scheduled runs are paused. A red banner at the top counts the days. To give up, click Cancel the deletion. See Governance and LGPD.
Account security — two-step verification (MFA)#
Where it is: avatar menu → Account security.
Open the screen
In the avatar menu, click Account security. The screen is called Two-step verification.
Scan the QR code
Use an authenticator app (Authy, 1Password, or another). If you can't scan it, use the key shown under "Can't scan? Use the manual key:".
Type the code
In 6-digit code, type the number the app shows.
Enable it
Click Verify and enable MFA.
At the end you should see: the app takes you back to the screen you were on. From then on, every sign-in asks for the authenticator code. If verification was already on, the screen takes you straight back.
The Two-step verification screen shows the QR code, the manual key right below it, and the 6-digit code field with the Verify and enable MFA button.
More in Authentication, login, and MFA.