Skip to content

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

Users, groups and permissions

On this page (14)

This is where you invite people, define what each one can operate on the data and manage non-human access (service principals / API keys).

Concepts#

  • User (Member): a person with access to the workspace. They have a role (RBAC) and a set of fine-grained permissions.
  • Groups / service principals: identities for automation (integrations, API). A service principal is a non-human identity with defined scopes.
  • Role vs. fine-grained permission: the role (RBAC) says what the person can do on the platform; the fine-grained permissions refine what they can operate on the data.

The member's 7 fine-grained permissions#

PermissionKeyWhat it unlocks
Run pipelinerunPipelinerun ingestions/transformations
Run queriesrunQueryrun queries on the datalake
Insert datadataInsertwrite new rows
Update datadataUpdatechange existing rows
Delete datadataDeleteremove rows
Export dataexportDatadownload/export results
See PII dataviewPIIsee sensitive (unmasked) columns

By default, a new member comes in with all permissions turned off (least privilege) and the Invited status.

Availability#

  • Plans: all. The number of creators and viewers is limited by the plan (see Plans).
  • How it works: RBAC and service principals are fail-closed and covered by automated tests.

Permissions (to administer people)#

  • Managing members requires the admin/owner role (RBAC action member.manage).
  • Managing API keys/service principals requires admin/owner (apikey.manage).
  • Assigning roles is exclusive to the owner (role.assign).

Setup (step by step)#

  1. Go to Settings → Users & permissions.
  2. Invite person: enter the name and email, choose the role (admin/member/viewer) and check the fine-grained permissions. The platform issues an activation link — copy it from the screen or let it be sent by email, when delivery is configured in the environment.
  3. RLS attributes (optional): define attributes such as filial for row-level security — see RLS.
  4. Activate/deactivate: a member can be Invited, Active or Disabled.

There is no temporary password. The platform never sends a password by email and never shows a password on screen. The invitee sets their own password when opening the link — or, if they already have an ingestia.io account, signs in with the identity they already use. An existing user's password isn't changed by the invite.

How the invite works (what the invitee sees)#

The activation link is valid for 24 hours and works only once. When it's opened:

The person's situationWhat the screen asks for
Doesn't have an account yetsets their password (minimum 8 characters) and signs in
Already has an ingestia.io accountsigns in with their usual password (and the MFA code, if they use it) — the password doesn't change
Already signed in with the invited emailjust confirms: Accept invitation
Signed in with another emailthe screen offers to sign out and return to this invitation

The workspace and the role come from the invite, resolved on the server. None of that is chosen in the browser form.

When the link is no longer valid, the screen says why and what to do — and never reveals which workspace the invite was for or whether that email exists:

ScreenWhen it appearsWhat to do
"This invitation has expired"more than 24 hours have passedask the administrator to Resend invite
"This invitation was canceled"the administrator canceled it, or issued a newer linkask for Resend invite
"This invitation has already been used"the link is single-use and was already acceptedsign in through the login screen; if you don't recognize the acceptance, tell the administrator
"This invitation was blocked"too many attempts on this linkask for Resend invite
"Invalid invitation link"link doesn't exist or was copied only partiallyask for Resend invite

Resend, cancel and remove#

  • Resend invite issues a new link and invalidates the previous one immediately.
  • Cancel invite kills the pending link without removing the person from the list.
  • Deactivating or removing the member also kills the pending invite. Access to the workspace stops being resolved even in an open session — the check is made on every request, against the database.

"Invite to reissue" badge

A person invited before the invite cycle was fixed received a temporary password that didn't authenticate anywhere. Those rows appear in the list with the Invite to reissue badge. The fix is one click: Resend invite issues a link that works.

Validation#

  • The new member appears in the list as Invited, with the role and the summary of permissions, and with Pending invite, valid until ….
  • The activation link is shown for the administrator to copy — and disappears as soon as it's used.
  • After acceptance, the status becomes Active and the person enters the workspace with the granted role.
  • Attempts at actions without permission are denied (fail-closed) and can be audited.

Example#

At Comércio Aurora, Maria (owner) invites:

  • joao@example.com as admin (manages sources, dashboards and people);
  • ana@example.com as member with runQuery and exportData on, but viewPII off (Ana analyzes sales without seeing sensitive data);
  • store managers as viewer (they only view dashboards).

Cost#

  • Managing users and permissions: R$ 0.
  • Additional licenses have a commercial cost (additional creator; viewer packs) — see Plans.

Security#

  • Least privilege by default (everything off at signup).
  • No password is created, shown or sent by the invite. The activation link is stored only as a cryptographic digest (the value exists inside the link, once), expires in 24 hours, works only once and is invalidated by a resend, cancellation, deactivation or removal of the member.
  • Accepting an invite never overwrites the password of an account that already exists.
  • MFA available per member, and required at acceptance for those who already use MFA.
  • API keys expose only safe fields (never the raw hash/value) in the UI.
  • The See PII data permission (viewPII) separates who can see sensitive data.

Limits#

  • owner is structural (the workspace owner) — it's never granted to a member via the permissions JSON (fail-closed downgrades to viewer if someone tries).
  • Automatic provisioning via IdP (SCIM) stays off until it is enabled for your organization (see SSO and SCIM).

Troubleshooting#

SymptomLikely causeWhat to do
Member can't run a queryrunQuery off or viewer roleturn on the permission / raise the role
"Action not allowed for the role"RBAC denied it (fail-closed)adjust the role according to the matrix
I lost the activation linkthe link is shown only onceuse Resend invite (the old link is invalidated)
Invitee says the link "expired" or "was canceled"more than 24 h passed, or a resend invalidated the previous oneuse Resend invite and deliver the newest link
Invitee received a password and it doesn't workold-model invite (Invite to reissue badge)use Resend invite: the old password doesn't authenticate and never did
Invitee didn't receive the emailemail delivery not configured in the environmentcopy the link from the screen and deliver it through a trusted channel
"You're signed in with another identity"the person opened the link with another session openclick Sign out and return to this invitation
Member sees PII when they shouldn'tviewPII onturn off viewPII in the profile

Next steps: Roles (RBAC) and Row-level security (RLS).

Related links