Consultant tier in one sentence: everyone on the team sees everything the team owner creates, and there are no Groups, no
SETTINGS team, and no per-record sharing decisions.What you get
- One team of type
ACCESS, created automatically with your subscription. - Up to three seats, including the owner.
- Automatic visibility: every Organization, Account, and Customer the owner creates is instantly visible to every team member.
- Role assumption: every member can assume any IAM role the owner has configured on a linked account.
What you don’t get (and why)
Consultant tier intentionally omits several Pro/Enterprise features to keep the experience simple:- No
SETTINGSteam. Only the subscription owner can create, edit, or delete records. - No Groups. Sharing is automatic — there is nothing to configure.
- No
OWNER/ADMINpromotions. All non-owner members are locked toMEMBER.
Before you start
You will need:- A Quiverstone account on the Consultant tier.
- The email addresses of up to two teammates you want to invite.
- (Optional) At least one AWS Organization or standalone account you want to share with the team.
Walkthrough
Sign in as the subscription owner
The person who purchased the Consultant subscription is automatically the team
OWNER. Only the OWNER can invite members or manage the workspace inventory, so start by signing in with that account.Add your AWS Organizations and Accounts
Before inviting teammates, add the AWS resources you want them to see:
- Add an Organization and configure its inventory role so member accounts are discovered automatically.
- Add any standalone Accounts that aren’t part of an Organization.
- Add Customer records if you want to track the business entities behind each Organization.
Invite your teammates
- Navigate to Teams and open the existing
ACCESSteam. - Click Invite Member and enter an email address.
- Repeat for your third seat if needed.
Verify shared visibility
Ask one of your teammates to sign in and open the Organizations, Accounts, and Customers lists. They should see every record you created in Step 2 without any further configuration.If a teammate does not see an expected record, check that:
- Their membership shows as
ACTIVEon the Teams page. - They have signed out and back in since accepting the invite.
Deploy IAM roles for role assumption (optional)
If your teammates need to jump into AWS consoles, follow the Access Roles quickstart to deploy one or more IAM roles into your target accounts. Once deployed, every team member can click Assume Role on any Account where that role is configured.
What members can and can’t do
| Action | Owner | Member |
|---|---|---|
| Create / edit / delete Organizations, Accounts, Customers | Yes | No |
| View all team inventory | Yes | Yes |
| Assume configured AWS roles | Yes | Yes |
| Invite new members (up to the 3-seat cap) | Yes | No |
| Change another member’s role | Yes | No |
| Upgrade the subscription | Yes | No |
When to upgrade to Pro
Consider upgrading to Pro when you need any of the following:- More than three seats. Consultant is hard-capped at 3.
- Multiple teams. For example, one team for internal staff and another for a contractor.
- Delegated administration. A second
ADMINwho can manage the inventory without owning the subscription. - Selective sharing. Showing different teammates different subsets of your AWS estate.
ACCESS team remains in place, and you can start creating SETTINGS teams and Groups alongside it.

