Organization
An Organization (often shortened to “Org”) is the root entity in Gloo AI’s multi-tenant architecture. All data, content, and users are scoped to a specific Organization. Every account belongs to at least one Org, and data is fully isolated between Organizations.Publisher
A Publisher is a sub-entity within an Organization that owns and produces content. All ingested content is associated with a Publisher. An Organization can have multiple Publishers, each representing a distinct brand, team, author, or imprint. You must create at least one Publisher before uploading content. See Manage Publishers.Tenant
Tenant is an alias for Publisher used within the Data Engine context. When the API or Studio UI refers to a tenant, it means the Publisher that owns the content being operated on.publisher_id
Thepublisher_id is the unique identifier for a Publisher, assigned by Gloo AI when the Publisher is created. It is required as a parameter in most Content API calls to scope operations to the correct Publisher.
You can find your publisher_id in Studio under Manage Organizations → View Publishers.
item_id
Theitem_id is Gloo AI’s internal UUID assigned to each content item upon ingestion. It uniquely identifies an item across all API operations (edit, inspect, delete).
producer_id
Theproducer_id is your own internal identifier for a content item, optionally provided at upload time. It lets you reference items using your existing IDs without storing Gloo’s item_id.
If you provide a producer_id at upload, you can use it to look up the corresponding item_id later via the Get Item by Producer ID endpoint.
User Roles
Users in Gloo AI are assigned roles that determine what they can access within an Organization.| Role | Permissions |
|---|---|
| Admin | Invite users, create and manage Publishers, manage content ingestion, view all analytics. |
| Editor | Upload content via Studio or API. |
| Viewer | View ingestion analytics and use components. |