Share a Collection
Overview​
By default, Collections in Enterprise h2oGPTe are private and only accessible to the creator. You can share Collections in three ways:
Additionally, Collections can be shared with specific users with certain permitted actions or IdP (Identity Provider) groups. To share a Collection with a particular group, specify the group's ID. This level of access control ensures that only the intended users or groups have access to the Collection and its content.
When discussing the role of identity providers (IdP) in Enterprise h2oGPTe, it is essential to distinguish between IdP roles and IdP groups. IdP roles are used to grant or restrict access to various system features and functionalities within Enterprise h2oGPTe. These IdP roles can be mapped to internal Enterprise h2oGPTe roles for seamless integration.
On the other hand, IdP groups serve a different purpose. They are used as entities for sharing data within Enterprise h2oGPTe. By mapping these groups to entities such as Lightweight Directory Access Protocol (LDAP) groups on Keycloak, Enterprise h2oGPTe enables seamless data sharing with specific users and teams.
It is worth noting that while LDAP groups on Keycloak are one example of how groups can be mapped in Enterprise h2oGPTe, this is not the only way. The configuration of Keycloak to inherit group information from LDAP is just one possible implementation, and other identity providers and group mapping strategies may also be used.
- Once a Collection is made public, any authenticated user of the system or API can view and interact with the Collection.
- To learn about roles and permissions in Enterprise h2oGPTe, see Roles and Permissions.
Document delete permissions​
To delete documents from a Collection, users must have the Delete documents permission (assigned via Roles and Permissions). See Roles and Permissions to learn more.

Beyond that, who can delete depends on ownership and permissions:
- Collection owners: Can delete any document in their Collection, regardless of document ownership. No additional collection-specific permission is required.
- Document owners: Can delete their own documents from any Collection, even if they don't own the Collection.
- Users with collection delete permission: Can delete documents they don't own from Collections they don't own, when granted the collection-specific delete permission during Collection sharing. Remember, this permission allows deletion of non-owned documents within the shared Collection.

To learn how to share collections, see Instructions to share a collection below.