Skip to content
Tukun.ai A Semantic-first Data Agent
Sign in

Accounts

Accounts are the main collaboration, billing, and access boundary in Tukun.ai.

Section titled “Recommended structure”

Most users start with one personal account. Teams should add a shared account only when there is a real collaboration, billing, or data separation requirement.

Common account patterns:

  • Personal account for individual exploration and early setup.
  • Team account for shared business analytics and common assets.
  • Separate test or demo account when non-production data must stay isolated.

Account hygiene

Section titled “Account hygiene”
  • Use clear names for data sources and dashboards.
  • Keep production and test data separate.
  • Remove unused credentials during onboarding cleanup.
  • Save repeated analyses as cards instead of relying on old conversation threads.

Access model

Section titled “Access model”

Give users the minimum role they need for their work. Keep credential and billing administration limited to owners or trusted admins.

Workbench scope

Section titled “Workbench scope”

The Workbench is the current execution surface inside an account. Conversations, cards, dashboards, and semantic assets remain scoped to the active account rather than to a separate workspace object.