Gaia 3.0 - Organizations, Roles, and Platform Access

Agent platforms become operational infrastructure when more than one team depends on them. At that point, access cannot be an afterthought. Teams need clear organizations, roles, user lifecycle controls, and non-human identities for automation.

With Gaia 3.0, Gaia's administration layer became much more complete.

The Problem: Multi-Team Work Needed a Stronger Control Plane

As Gaia adoption grows, administrators need more than project-level configuration. They need to manage who belongs where, what users can do, which automations can act, and how new or guest users enter the system.

The missing pieces were:

• a clearer organization model,
• role-based access across platform, teams, and projects,
• and account flows that work for humans and automated integrations.

Gaia 3.0 made those pieces visible.

Organizations Became a First-Class Surface

What shipped

Gaia 3.0 introduced a dedicated Organizations area with expanded management, clearer organization and project administration, organization creation, organization logos, organization login policy support, organization badges on recent projects, and improved handling for organization names, team paths, and instance hostnames.

Why this matters

Organizations give administrators a stable way to reason about teams and projects at scale. They also make cross-organization context easier to recognize in the product, which matters when users move between several operating environments.

Roles and User Management Got More Explicit

What shipped

Platform User Management lets administrators manage users centrally, assign roles, control access, and handle lifecycle states such as active or suspended. Platform Roles and Permissions add platform-level role definitions, while Organization roles for teams and projects make access enforcement more consistent across workspaces.

Why this matters

Governed agent work needs predictable permission boundaries. Users should be able to see and act only where they are meant to, and administrators should not need to rely on informal conventions to enforce that separation.

Human and Non-Human Access Both Improved

What shipped

Gaia 3.0 added guest login, anonymous sign-in, email one-time passwords, more reliable user provisioning, service accounts, multiple API keys per service account, execution principals in workflows, and project-level tool access management.

Why this matters

Modern agent operations involve people, embedded users, service principals, integrations, and scheduled automation. Gaia 3.0 gives those actors clearer entry points and cleaner attribution boundaries.

Why This Is a 3.0 Shift

Gaia 3.0 makes access management feel like part of the product rather than a background concern. Organizations, users, roles, guests, and service accounts now form a clearer operating model for multi-team use.

That matters because governed AI work depends on knowing who can act, which system they are acting through, and what boundary applies at the moment of execution.