Learn what Identity and Access Management is on Vultr. IAM controls who can access your resources, what actions they can perform, and under what conditions.
Understand IAM roles on Vultr. Roles bundle permission policies into reusable sets that can be assigned to users and groups or assumed for temporary access.
Learn what an organization is in Vultr IAM and why it is required. Organizations serve as the top-level boundary for users, groups, roles, and resource access.
Understand how Vultr isolates resources and data between organizations. Each organization maintains separate infrastructure, billing, and access boundaries.
Learn whether a user can belong to multiple Vultr organizations simultaneously and how to switch between them using the Vultr Console or API context.
Find out if existing ACL-based access controls continue to work after Vultr IAM is enabled. ACLs remain functional alongside IAM during the transition period.
Learn whether you can convert an assignable role to an assumable role in Vultr IAM. Understand the differences between the two role types and how to switch.
Find out if Vultr-managed permission policies can be modified. Vultr-managed policies are read-only and cannot be edited, but you can create custom policies.
Learn whether manual migration from ACLs to IAM is required on Vultr. Existing ACL permissions are automatically mapped to equivalent IAM policies for you.
Learn how to add or remove users and assign or detach roles within a Vultr IAM group. Manage group membership and permissions through the Console or the API.
Learn how to view the combined effective permissions for a user in Vultr IAM. See all access granted through direct policies, group memberships, and roles.
Understand permission policies in Vultr IAM. Policies define allow and deny rules for actions on resources and can be Vultr-managed or custom-created by you.
Review the resource limits for IAM in your Vultr organization. See the maximum number of users, groups, roles, and policies allowed per organization account.
Learn which entities support policy attachment in Vultr IAM. Permission policies can be attached directly to users, groups, and roles in your organization.
Understand the access impact when a user is removed from a Vultr IAM group. The user loses inherited permissions but retains any directly assigned access.
Learn what happens to your existing ACL-based permissions when Vultr enables IAM. ACL rules are mapped to equivalent IAM policies to preserve current access.
Understand the impact of removing a user from a Vultr organization. The user loses access to organizational resources but their platform account is not deleted.
Understand IAM groups on Vultr and how permission inheritance works. Groups let users inherit roles and policies automatically through group membership assignment.
Learn about user types in Vultr IAM including normal users, service users, and the root owner. Understand how each type interacts with organizations and access.
Understand resource scoping in Vultr IAM. Resource scoping lets you grant permissions on specific resources instead of all resources within a service category.
Compare the root owner and organization admin roles in Vultr IAM. Understand the privileges, limitations, and responsibilities that distinguish each identity.
Learn the session duration limits for assumable roles in Vultr IAM. Sessions range from 15 minutes to 12 hours maximum, with a default duration of 1 hour.
Learn how long an organization invitation remains valid in Vultr IAM. Understand the expiry timeframe and what happens when an invitation link expires.
Learn which entities can hold IAM roles on Vultr. Assignable roles attach to users, service users, and groups. Assumable roles use trust-based relationships.