h2oGPTe icon

h2oGPTe

h2oGPTe is an AI-powered search assistant for your internal teams to answer questions gleaned from large volumes of documents, websites and workplace content.

Actions198

Overview

This node operation removes sharing permissions of a specified collection from all users except the original owner. It is useful in scenarios where you want to revoke access for everyone else who had shared access to a collection, effectively making the collection private to its original owner only.

For example, if a team has collaborated on a document collection but the owner wants to restrict access after the project ends, this operation can be used to unshare the collection from all other users at once.

Properties

Name Meaning
Collection ID The unique identifier (ID) of the collection whose sharing permissions will be removed for all users except the original owner. This property is required.

Output

The output of this operation typically contains the response from the API indicating the success or failure of the unsharing action. The main output field json will include the HTTP response details returned by the API endpoint that handles permission removal for the collection.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication with the H2O GPT API.
  • The node makes an authenticated DELETE HTTP request to the endpoint /collections/{collection_id}/permissions to remove sharing permissions.
  • Proper API credentials and network access to the H2O GPT instance are necessary.

Troubleshooting

  • Invalid Collection ID: If the provided collection ID does not exist or is incorrect, the API will return an error. Verify the collection ID before running the operation.
  • Insufficient Permissions: The user associated with the API key must have permission to modify collection sharing settings. Lack of proper permissions will cause authorization errors.
  • Network Issues: Connectivity problems to the API endpoint may result in timeouts or failed requests.
  • API Errors: The API might return errors if the collection is already private or if there are internal server issues. Check the error message for details.

To resolve these issues:

  • Double-check the collection ID.
  • Ensure the API key has sufficient privileges.
  • Confirm network connectivity.
  • Review API error messages and logs for more information.

Links and References

Discussion