
Identity and Access Management (IAM) in Vultr controls which users can access an organization and what actions they can perform on its resources. An organization grants access through a chain of components. Users join the organization, groups collect users with similar responsibilities, and policies attached to those groups (directly or through roles) define the specific permissions each member receives.
This guide explains how to invite a new organization member and grant them access. It covers sending the invitation, creating a group, attaching a managed policy to the group, confirming the user's acceptance, adding the user to the group, and validating the user's access. It also explains why a newly invited user can see a No Active Organization screen on first login, and how to avoid that outcome.
Before you begin, you need to:
iam.group.*, iam.policy.*, and iam.invitation.* permissions.Joining an organization does not, by itself, grant a user any permissions. If an invitation goes out with no role, group, or policy selected, the user joins the organization with no assigned access, and the Vultr Console displays a blank No Active Organization screen when they log in. To let a user view or manage resources, attach a policy to them, either directly, through a role, or through a group. Without an attached policy, the user account exists in the organization but cannot access any of its resources.
Inviting a user sends them an email invitation to join the organization. The invitation only grants organization membership. It does not, by itself, grant any permissions.
Log in to the Vultr Console.
Click the organization name in the top navigation bar.
Click Manage Organization.
Click the Users tab.
Click the Add User button.
In the Add User panel, select the Invite Type as User.
Enter the user's Email Address.
Click Review and Invite.
Review the invitation details and click Send Invitation.
The invitation is sent to the user's email address. The user appears in the Invitations section with a status of Invite Pending until they accept.
For more detail on this step, including the Vultr API method, refer to How to Invite a User to an Organization.
A group lets you assign permissions once and apply them to every member, instead of repeating the same policy and role attachments for each individual user.
Click the Groups tab in Manage Organization.
Click the + button to add a group.
Enter the Group Name and Group Description.
Click Review.
Review the details and click Add Group.
The group is created and appears in the Groups list with no members and no attached policies yet.
For more detail on this step, including the Vultr API method, refer to How to Create a Group.
Vultr provides a set of managed policies covering common access patterns, so you do not need to write a policy document from scratch for standard roles. Attaching a managed policy grants every current and future member of the group the permissions it defines.
Click the Permission Policies tab in Manage Organization.
Select a managed policy that matches the access level the user needs.
In the Attached Entities section, click the + button.
Search for and select the group you created.
Click Attach Entities.
The group appears in the Attached Entities list, and all current and future members inherit the policy's permissions.
For more detail on this step, including the Vultr API method, refer to How to Attach a Policy to a Group.
A user must hold an Active status before you can add them to a group. Confirm that the user accepted the invitation before moving on to the next step.
Click the Users tab in Manage Organization.
Locate the invited user in the list.
Verify that the status changes from Invite Pending to Active. Status updates as soon as the user accepts the invitation.
Adding the user to the group connects their organization membership to the permissions attached to the group in the earlier step.
Click the Users tab in Manage Organization.
Click the name of the now-active user.
In the Groups section, click the + icon.
In the Add to Groups panel, select the group you created.
Click Add User to Groups.
The user immediately inherits the group's permissions.
For more detail on this step, including the Vultr API method, refer to How to Add a User to a Group.
A user who accepts an organization invitation and logs in before being added to any group, and without a role or policy attached directly, has a valid membership but zero permissions. The Vultr Console responds to this state by displaying a No Active Organization screen on the organization page, with the message "We currently do not have your organization details", because the user has nowhere to navigate, even though the invitation itself succeeded.
This is the most common point of confusion in user provisioning. The user successfully joined the organization, but the lack of any assigned access makes the Console behave as if no organization is available to them. If a user reports a No Active Organization screen after accepting an invite, verify the following items.
Effective access combines every policy a user receives directly, through a role, and through group membership. Validating it confirms that the group and policy configured earlier actually reach the user, rather than relying on the individual attachment steps alone. The Vultr Console has no screen for this check, so use the Vultr API.
Send a GET request to the List Current User's Groups endpoint using an API key scoped to the newly provisioned user.
The response contains the group you added the user to. If the response is empty, recheck the group membership and the policy attachment, because an empty result on this endpoint is what produces the No Active Organization screen for that user.
You have invited a new member to your organization and given them working access through a managed policy attached to a group. The member can view and manage the resources their policy permits, without encountering a No Active Organization screen on login. For more information, refer to the Vultr IAM documentation.
0 Comments
Be the first to comment and share your perspective with the community.