Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.quiverstone.io/llms.txt

Use this file to discover all available pages before exploring further.

Teams are the primary unit of user organization in a Quiverstone subscription. Every team has a type (ACCESS or SETTINGS) that determines what its members can do, and every team member has a role (OWNER, ADMIN, or MEMBER) that determines how they can manage the team itself. This page explains the model, walks through creating and managing teams, and covers how invites, co-ownership, and backfill work.
Teams require a paid subscription. Free tier is a single-user workspace with no teams. See Subscriptions & Tiers for the full feature gating.

​
The two team types

Quiverstone separates users into two distinct roles by team type, so that the people who manage your AWS inventory are cleanly separated from the people who consume it.

​
ACCESS teams

ACCESS teams are for consumers — people who need to view Organizations, Accounts, and Customers, and assume AWS roles, but should not be able to modify the workspace inventory.
  • Available on: Consultant, Pro, Enterprise.
  • Members cannot create, edit, or delete Organizations, Accounts, or Customers. The CRUD controls are hidden in the UI.
  • Members can assume any AWS IAM role that has been granted to them via a Group.
  • On Consultant tier, the single ACCESS team automatically sees every resource the owner creates.
  • On Pro and Enterprise, ACCESS teams see only the resources explicitly granted to them through a Group.

​
SETTINGS teams

SETTINGS teams are for admins — the people who own and manage the workspace’s Organizations, Accounts, Customers, Roles, and Groups.
  • Available on: Pro, Enterprise. Not available on Consultant.
  • Members can create, edit, and delete Organizations, Accounts, Customers, Roles, and Groups.
  • Automatic co-ownership: when any SETTINGS member creates a resource, every other current SETTINGS member immediately becomes a co-owner with full edit and delete rights. There is no manual sharing step.
  • A SETTINGS team OWNER can manage any team in the subscription, not just their own.
  • SETTINGS members are the only people who can create and edit Groups to share resources with ACCESS teams.
Automatic co-ownership applies to SETTINGS teams only. If two SETTINGS members both work on the same Organization, either can edit or delete it at any time. Treat the SETTINGS team as a trusted circle of admins.

​
Team roles: OWNER, ADMIN, MEMBER

Within a team, each member has exactly one of three roles. Team roles control how you manage the team itself — they are independent of the team type.
RoleWho it isWhat they can do
OWNERThe subscription payer, or someone they transferred ownership toFull control of the team: edit details, invite and remove members, promote or demote members, delete the team.
ADMINA trusted lieutenantManage team membership: edit team details, invite new members, promote members up to ADMIN. Cannot delete the team or demote an OWNER.
MEMBERA regular team memberUse the resources the team grants. Cannot manage team membership.
On Consultant tier, non-owners are locked to MEMBER. The OWNER/ADMIN/MEMBER distinction only matters on Pro and Enterprise.
A team must always have at least one OWNER. Quiverstone prevents you from demoting or removing the last remaining OWNER of a team — promote someone else first.

​
Creating a team

1

Open the Teams page

Navigate to Teams in the main navigation.
2

Click Create Team

The button is only available if your tier allows additional teams. On Consultant, the button is hidden once the single allowed team exists.
3

Pick a team type

Choose ACCESS or SETTINGS. The SETTINGS option is hidden on Consultant tier.
If you are not sure, start with ACCESS. You can always create additional teams later.
4

Name the team and save

Give the team a short, descriptive name (for example, Ops, Platform Admins, Acme Contractors). You’ll use this name when referencing the team in Groups.

​
Inviting a member

1

Open the team

Click into the team from the Teams list.
2

Click Invite Member

Enter the invitee’s email address. They don’t need a Quiverstone account yet — the invite flow will create one when they accept.
3

Wait for them to accept

The invitee receives an email invitation. Their membership sits in PENDING state until they accept and sign in for the first time, at which point it becomes ACTIVE.
4

Verify backfill

When the new member’s status transitions to ACTIVE, Quiverstone automatically backfills resource visibility so they can start working immediately. See Backfill behavior below for the exact rules.

​
Backfill behavior

When a new member becomes active, Quiverstone grants them visibility into the resources they should already be able to see — no manual sharing step required.
Team typeTierWhat the new member sees on activation
ACCESSConsultantEvery Organization, Account, and Customer the team owner has ever created.
ACCESSPro / EnterpriseNothing automatic. They see only the resources referenced by Groups that include them or their team. Edit or re-save an existing Group to grant access.
SETTINGSPro / EnterpriseAutomatic co-ownership of every resource any current SETTINGS teammate owns.
Pro/Enterprise ACCESS team backfill is the one case that requires action: after adding a new member, have a SETTINGS team member confirm that any Group the new member should be part of already references them (directly or via their team).

​
Managing members

From the team detail page, a team OWNER or ADMIN can:
  • Change a member’s role — promote a MEMBER to ADMIN, or an ADMIN to OWNER (Pro/Enterprise only).
  • Remove a member — revokes the team’s grants from that user immediately. If the user is in multiple teams or Groups, their other access is unaffected.
  • Resend an invite if a PENDING invite has expired.
  • Delete the team (Pro/Enterprise only, OWNER only) — removes the team and revokes any access it was granting through Groups.

​
Transferring ownership

A team OWNER can transfer ownership to another member:
  1. Promote the target member to OWNER.
  2. Once the team has two OWNERs, demote yourself to ADMIN or MEMBER.
This two-step process is intentional: it ensures the team never has zero owners at any point. For transferring ownership of the entire subscription (billing, seats, tier management), contact support — subscription ownership transfer is a privileged operation performed out-of-band.

​
Common scenarios

“I have a small team that should all see the same AWS estate.” Consultant tier, one ACCESS team, invite everyone into it. Done. “I want to separate my admins from my operators.” Pro tier. Create a SETTINGS team for yourself and any other admins, then create one or more ACCESS teams for operators. Use Groups to share specific Organizations or Accounts with the ACCESS teams. “I want a contractor to see only one Customer’s infrastructure.” Pro or Enterprise. Create an ACCESS team for the contractor, then create a Group that includes that team and only the Organizations, Accounts, and Customer records they should see. Delete the Group when the engagement ends to revoke access. “I want a second admin who can manage the workspace alongside me.” Pro or Enterprise. Add them to your SETTINGS team. They’ll automatically co-own every record you’ve created, and every record they create will be co-owned by you.