GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation allows overriding a group member's permissions in a GitLab group by making a POST request to the GitLab API endpoint `/api/v4/groups/{id}/members/{user_id}/override`. It is useful for managing group member access levels programmatically, such as elevating or restricting user permissions within a specific group.

Use Case Examples

  1. Automatically update a user's permissions in a GitLab group when their role changes in an external system.
  2. Override a member's access level in a group as part of a CI/CD pipeline to ensure correct permissions before deployment.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the API request, useful for testing or public endpoints.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is POST for this operation.
Path Parameters Parameters required in the URL path to identify the group and user whose membership is being overridden.

Output

JSON

  • id - The ID of the group member whose permissions were overridden.
  • access_level - The new access level assigned to the group member.
  • expires_at - Expiration date of the overridden permissions, if applicable.
  • created_at - Timestamp when the override was created.

Dependencies

  • GitLab API authentication token or API key

Troubleshooting

  • Ensure the group ID and user ID are correct and exist in the GitLab instance.
  • Verify that the API token has sufficient permissions to override group member permissions.
  • Check the base URL to confirm it points to the correct GitLab instance.
  • Common error: 404 Not Found - The group or user does not exist or the path parameters are incorrect.
  • Common error: 403 Forbidden - The API token lacks permission to modify group members.

Links

Discussion