LearningSuite icon

LearningSuite

Interact with LearningSuite API (powered by agentur-systeme.de)

Actions56

Overview

The "Remove Hub Access" operation in the LearningSuite node allows users to revoke access permissions from a specified hub. This can be done by removing access for specific members, groups, and/or bundles associated with that hub. It is useful in scenarios where you need to restrict or update access control dynamically, such as when a user leaves a team, a group’s permissions change, or certain content bundles should no longer be accessible.

Practical examples include:

  • Removing a former employee's access to a training hub.
  • Revoking access for a group that no longer requires it.
  • Adjusting bundle access after content updates or licensing changes.

Properties

Name Meaning
Hub Name or ID The identifier of the hub from which access will be removed. You can select from a list or specify an ID via expression.
Group Names or IDs List of group identifiers whose access to the hub will be revoked. Select from a list or specify IDs via expression.
Bundle Names or IDs List of bundle identifiers to remove access for. Select from a list or specify IDs via expression.
Member Names or IDs List of member identifiers to remove access for. Select from a list or specify IDs via expression.

Note: At least one of Group, Bundle, or Member selections must be provided to perform the removal.

Output

The node outputs a JSON array containing the results of the access removal operation. Each item in the output corresponds to the processed input item and typically includes confirmation details or error information if the operation failed for that item.

If errors occur and the node is set to continue on failure, the output items will contain an error field describing the issue alongside the original input data.

No binary data output is produced by this operation.

Dependencies

  • Requires a valid API key credential for authenticating with the LearningSuite API.
  • The node depends on LearningSuite API endpoints to manage hub access.
  • Proper configuration of the base URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Common Issues:

    • Missing or invalid hub ID: Ensure the hub exists and the ID is correct.
    • No groups, bundles, or members selected: At least one must be specified to remove access.
    • Insufficient permissions: The API key used must have rights to modify hub access.
    • Network or API errors: Check connectivity and API status.

  • Error Messages:

    • "No handler for resource "hub" and operation "removeAccess": Indicates a misconfiguration or unsupported operation; verify the node version and parameters.
    • API response errors (e.g., 403 Forbidden, 404 Not Found): Usually relate to authorization issues or invalid resource identifiers.

  • Resolution Tips:

    • Double-check all IDs and selections.
    • Verify API credentials and permissions.
    • Use expressions carefully to ensure they resolve correctly.
    • Enable "Continue On Fail" to handle partial failures gracefully.

Links and References

Discussion