For the complete documentation index, see llms.txt. This page is also available as Markdown.

Users

The Users section allows administrators to create and manage users, define their roles, assign groups, and control access across the Gaio DataOS environment.

Creating a New User

To create a new user:

  1. Click New.

  2. Select the User Type.

  3. Fill in the required user information (mail and password).

  4. Assign the user to a Group (optional).

  5. Select the interface Language.

  6. Click Save.


User Types (Roles)

User

Designed for business users and dashboard consumers.

Access:

  • Dashboards explicitly shared with the user

  • Read-only interaction with analytics and visualizations

Restrictions:

  • No access to Studios

  • No access to data pipelines, tasks, or modeling

  • No access to environment settings

Typical use cases:

  • Executives

  • Business analysts

  • Stakeholders consuming insights

Developer

Designed for users responsible for building and maintaining data workflows.

Access:

  • Studios (ETL, Analytics, AI, Tasks)

  • Dashboards

  • Project-level data sources and resources (based on assigned permissions)

Restrictions:

  • No access to global environment Settings

  • Cannot manage users or authentication providers

Typical use cases:

  • Data engineers

  • Analytics engineers

  • Technical analysts

Admin

Designed for full platform governance and system administration.

Access:

  • Full access to all dashboards and studios

  • Full access to all projects and data sources

  • Full access to Settings, including:

    • Users

    • Tags

    • Authentication providers

    • SMTP

    • White Label

    • AI and API keys

Typical use cases:

  • Platform administrators

  • IT and security owners

  • System owners


User Status

Each user account can be set to:

  • Active – User can log in and access the platform

  • Inactive – User is disabled and cannot log in


Groups & Permissions

  • Users inherit permissions from their assigned Group

  • Groups are connected to projects and sources using Tags

  • This model enables centralized, scalable access control


Best Practices

  • Assign permissions through Groups, not individual users.

  • Use the User role for dashboard-only access.

  • Use the Developer role for data and pipeline development.

  • Limit the Admin role to a small, trusted group.

  • Regularly review user access and inactive accounts.

Last updated