AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node operation, "Retrieve Exec Edit Calendar Permissions" under the "List" resource, is designed to query and retrieve executive-level edit permissions for calendar entries within a specified folder or list. It is useful in scenarios where you need to audit, verify, or manage user permissions related to calendar editing access in an organizational context. For example, an administrator might use this node to check which users have edit rights on a particular calendar folder or to update permissions accordingly.

Properties

Name Meaning
Foldername The name of the folder or calendar list for which permissions are being queried.
Permissions The specific permission level or type to check or retrieve (e.g., edit, view).
Removeaccess A flag or indicator specifying whether to remove access for certain users (likely yes/no or true/false).
Tenantfilter A filter parameter to specify the tenant or organizational unit scope for the query.
Userid The identifier of the user performing the query or whose permissions are relevant.
Usertogetpermissions The identifier of the user whose calendar permissions are being retrieved.

Output

The output of this node will be JSON data representing the permissions information for the specified calendar folder and user(s). This typically includes details about which users have what level of edit access on the calendar entries. The exact structure depends on the API response but generally contains user IDs, permission types, and possibly metadata about the calendar folder.

If binary data were involved (not indicated here), it would represent files or attachments related to the calendar permissions, but this node appears focused solely on JSON permission data.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard CIPP API.
  • Needs the base URL for the API endpoint configured in the node credentials.
  • Depends on the external AvantGuard CIPP service accessible via REST API.

Troubleshooting

  • Missing or invalid API credentials: Ensure that the API key and base URL are correctly set up in the node credentials.
  • Incorrect foldername or user identifiers: Verify that the folder name and user IDs provided exist and are correctly spelled.
  • Permission denied errors: The authenticated user may lack sufficient rights to query or modify calendar permissions; check user roles and privileges.
  • Network or connectivity issues: Confirm that the API endpoint is reachable from the n8n environment.
  • Invalid parameter values: All required parameters must be provided and valid; empty or malformed inputs can cause errors.

Links and References

Discussion