Team and Access Control

The Members page in the Organization group of the Stacktape Console controls who can use your organization and what they reach. Invite people, choose their role, projects and AWS accounts, require two-factor sign-in, give CI an organization key that does not belong to a person, and see what stops working before you remove someone.

Overview

The page has up to four parts:

  • Two-factor sign-in (Owners and Admins): whether members who sign in with a password must also use an authenticator app.
  • People: everyone who has joined, with their role, what a Developer or Viewer reaches, two-factor status, when they were last active and when they joined. Search by name or email, filter by role, or show only members without two-factor or inactive for 30 days or more.
  • Invitations: invitations that have not been accepted yet, who sent them, and when they expire.
  • Organization keys (Owners and Admins): API keys that belong to the organization, for CI.

Click a member's name to open their page. Owners and Admins can open anyone's page; Developers and Viewers can open their own.

Roles

RoleCan doReaches
OwnerEverything, including deleting the organization, billing and appointing other OwnersEvery project and every connected AWS account
AdminEverything except deleting the organization and setting up single sign-onEvery project and every connected AWS account
DeveloperDeploy, delete non-production stages, manage secrets and parametersOnly the projects and AWS accounts chosen for them
ViewerRead projects, deployments, logs, incidents and membersOnly the projects and AWS accounts chosen for them

Project and AWS account access

A Developer or Viewer has two lists, set when you invite them and changed with Edit access:

  • Projects decide which projects they see in the Console and which projects the CLI lets them deploy.
  • AWS accounts decide where Stacktape gives them AWS access: CLI credentials for deploys, scripts and stack commands, deployments started from the Console, and the Console pages that read AWS directly (logs, metrics, secrets, parameters, debug sessions, redeploys and rollbacks, Investigate and Fix with AI).

AWS access always covers the whole account. A Developer given the account production for the project shop can, with the credentials the CLI receives, also reach other projects' stacks in production. Give a person an account only if they may act in all of it. Agencies with one AWS account per client get a clean boundary by giving each person only their clients' accounts.

A Developer with no AWS accounts can still see their projects in the Console, but the CLI refuses to deploy, and the pages that read AWS say that their access does not include the account. Owners and Admins always reach every account.

Inviting members

  1. Open Members and click Invite members.
  2. Enter one or more email addresses, separated by commas or new lines (up to 20 at once).
  3. Choose a role. For a Developer or Viewer, choose their projects and AWS accounts.
  4. Click Send invitations.

Someone who already has a Stacktape account becomes a member at once. Anyone else gets an email and appears under Invitations until they sign up. An address that is already a member, or that could not be invited, stays in the field with the reason, so the rest are not lost.

An invitation works for 14 days after its email last went out. Resend invitation sends it again and starts the 14 days again; an expired invitation can be resent the same way. Copy invite link copies the sign-up link to share another way; it only works for the invited address. Cancel invitation stops the link from working.

Personal organizations have exactly one member. To work with others, create a team organization; team organizations have no member limit.

With single sign-on, people from your company's email domains can also join without an invitation, by signing in through your identity provider or being added by your directory.

Organization keys for CI

A personal API key acts as the person who created it and stops working when they leave the organization. CI that uses one breaks when that person is removed. An organization key belongs to the organization instead:

  1. In Organization keys, click New organization key.
  2. Name it after where it runs, for example github-actions.
  3. Choose Developer with the projects and AWS accounts the pipeline deploys, or Admin for everything.
  4. Copy the key from the next dialog; it is shown only once. Store it as the STACKTAPE_API_KEY secret of your CI.

The list shows who created each key and when it was last used. Revoking a key stops every pipeline that uses it at once. Organization keys cannot create organizations or connect AI subscriptions, which belong to people.

Requiring two-factor sign-in

Owners and Admins can require two-factor sign-in with Require in the Two-factor sign-in row. The confirmation lists the members who sign in with a password only. After that, those members see only a screen that sends them to Account Settings to add an authenticator app or a passkey; the rest of the organization opens again once they sign in with it. Signing in with Google, GitHub, a passkey or single sign-on counts as two-factor. API keys, including the CLI and CI, keep working.

You need two-factor sign-in on your own account before you can require it.

Removing a member

Open the member's row menu, or their page, and choose Remove. The dialog lists what stops working with them:

  • their personal API keys, with when each was last used,
  • their own AI subscriptions for incident runs,
  • their Slack link.

If one of their keys was used in the last 7 days, the dialog says so, because CI may depend on it, and offers to create an organization key first. Stacks they deployed keep running, their deployments stay in the history, and organization keys keep working, including ones they created.

Revoke API keys in the row menu revokes a member's personal keys without removing them.

Last active

The Last active column shows the most recent of three times, listed separately when you hover it and on the member's page:

  • Console: their last visit, recorded at most once an hour.
  • CLI: the last request with one of their personal API keys.
  • Last deploy: the last deploy they started.

Troubleshooting

"Your access does not include the AWS account"

The member is a Developer or Viewer and the account is not in their AWS accounts. An Owner or Admin adds it with Edit access on the Members page. The CLI shows the same reason, and stacktape lists only the accounts the member can use.

The CLI stopped deploying for a Developer after an upgrade

Developers and Viewers reach only the AWS accounts chosen for them. When this was introduced, each of them was given the accounts their projects had deployed to; an account their projects never used must be added with Edit access.

Invite members is disabled

Either your role cannot invite (only Owners and Admins can), or this is a personal organization.

An invitation shows Expired

Its 14 days passed. Choose Resend invitation; the person can sign up for 14 more days.