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 specific collection from a specified user. It is useful in scenarios where you want to revoke a user's access to a particular collection, ensuring that the user no longer has any rights or visibility over that collection's content.

Practical examples include:

  • An administrator revoking access for an employee who has left a project.
  • Managing user permissions dynamically by removing access when it is no longer needed.
  • Ensuring data security by restricting access to sensitive collections on demand.

Properties

Name Meaning
Collection ID The unique identifier of the collection from which sharing will be removed.
Username The username of the user who will lose access to the specified collection.

Output

The output of this operation is the full HTTP response returned by the API after attempting to remove the sharing permission. This typically includes status information indicating whether the removal was successful or if there were errors (e.g., user not found, collection not found, or insufficient permissions).

The json field in the output contains the parsed response body from the API call.

No binary data is involved in this operation.

Dependencies

  • Requires an API key credential for authentication with the external service managing collections and permissions.
  • The node sends an authenticated DELETE HTTP request to the endpoint /collections/{collection_id}/permissions/{username}.
  • Proper configuration of the base URL and API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing Collection ID or Username parameters.
    • Insufficient permissions of the API key to modify collection sharing settings.
    • The specified user does not have sharing permissions on the collection.
    • Network or connectivity issues preventing API communication.
  • Error Messages:

    • 404 Not Found: The collection or user specified does not exist. Verify the IDs and usernames.
    • 403 Forbidden: The API key lacks permission to unshare the collection. Check credential scopes.
    • 400 Bad Request: Missing required parameters or invalid input format. Ensure all required fields are provided correctly.
  • Resolution Tips:

    • Double-check the Collection ID and Username values.
    • Confirm that the API key used has adequate permissions.
    • Review API documentation for correct usage and parameter requirements.
    • Test connectivity and API availability.

Links and References

  • Refer to the external API documentation for collections and permissions management for detailed information on the endpoint and expected responses.
  • Consult n8n documentation on setting up API credentials and HTTP request nodes for integration best practices.

Discussion