Latest Content

How to Detach a Role from a Group

Updated on 08 April, 2026

Detach an IAM role from a group on Vultr. Group members lose the permissions inherited from the role's policies while retaining their direct assignments.

Detaching a role from a group revokes the permissions granted through that role for all group members. Members retain any permissions assigned through other roles, direct policy attachments, or other groups.

This guide explains how to detach a role from a group using the Vultr Console and the Vultr API.

  • Vultr Console
  • Vultr API

  1. Log in to the Vultr Console.

  2. Click the organization name in the top navigation bar.

  3. Click Manage Organization.

  4. Click the Groups tab.

  5. Click the name of the group from which you want to detach the role.

  6. In the Roles section, locate the role and click the Remove icon next to it.

    The role is detached and all group members lose the permissions granted through it.

  1. Send a GET request to the List Roles endpoint to retrieve all roles in your organization.

    console 
    $ curl "https://api.vultr.com/v2/roles" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

    Note the id of the role you want to detach from a group.

  2. Send a GET request to the List Groups with Role endpoint to retrieve all groups assigned to the role. Replace {role-id} with the id of the role. Note the group_id of the group you want to detach.

    console 
    $ curl "https://api.vultr.com/v2/roles/{role-id}/groups" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

  3. Send a DELETE request to the Detach Role from Group endpoint to detach the role. Replace {role-id} with the role id and {group-id} with the group id.

    console 
    $ curl "https://api.vultr.com/v2/roles/{role-id}/groups/{group-id}" \
    -X DELETE \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

    A successful detachment returns an HTTP 204 No Content response with no response body.

Comments