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 who can interact with or view content within a particular hub.

Practical examples include:

  • Removing a user or group’s access after they leave an organization or project.
  • Revoking bundle access when certain content packages are no longer relevant.
  • Managing access control dynamically based on changing team structures or roles.

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 should 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 Groups, Bundles, or Members must be selected to remove access.

Output

The node outputs a JSON array containing the results of the removal operations. Each item in the output corresponds to the outcome of removing access for a particular entity (member, group, or bundle) or a summary object. If errors occur during execution, error details are included in the output when "Continue On Fail" is enabled.

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's backend services to manage hubs, members, groups, and bundles.
  • Proper configuration of the base URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Providing invalid or non-existent hub, member, group, or bundle IDs will cause errors.
    • Not selecting any of members, groups, or bundles will result in no action or an error.
    • Network or authentication failures may prevent successful API calls.

  • Error messages:

    • "No handler for resource "hub" and operation "removeAccess": Indicates a misconfiguration or unsupported operation.
    • API errors returned from LearningSuite typically include descriptive messages; ensure credentials and IDs are correct.

  • Resolutions:

    • Verify all IDs exist and are correctly formatted.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Use the "Continue On Fail" option to handle partial failures gracefully.

Links and References

Discussion