Docs

Approving access requests

An access request is time-boxed permission to debug or operate one customer deployment. Every request needs approval before anyone gets access, on every platform.

Who approves depends on the deployment group. On the Slack card, your team approves for a Team group, and your customer approves for a Customer group.

Acme Approvals  APP

6 hours access request

Debug checkout errors
Requested by: dana@acme.example
Why: Checkout pods keep restarting.
Deployment: customer-1/us-east-1

Access
• Remote debugging: aws (scope: 111122223333)

Expires: Nov 8 at 6:00 PM

[ Approve for 6 hours ]  [ Deny ]

The card above is what your customer sees in the Slack Connect channel you share with them. The Approve button shows the request's window, 6 hours by default. Both group types get the same card and buttons. On a Team group, verified members of your Alien workspace decide. On a Customer group, the customer's click decides. Cards come from the Alien Slack app unless you add your own Slack app. Either app can carry an approval.

Who approves

Each deployment group has a Who approves access requests setting, either Customer or Team.

SettingWho approvesWhere
CustomerYour customerThe Slack card in the shared channel. On Kubernetes, also kubectl in their cluster.
TeamMembers of your Alien workspaceThe Slack card. A teammate other than the requester can also approve in the dashboard, the CLI, or the API.

Every group starts as Customer. Only a workspace admin changes it, on the deployment page: select Change on the Who approves access requests row and confirm. The change applies to every deployment in the group, and Alien records every change.

Team approves

An engineer on your team approves or denies on the Slack card, in either the Alien Slack app or your own. The requester can approve their own request there: a Slack click is a person clicking a card in a Slack app, which an AI agent holding their token can't do.

The person who clicks must be a member of your Alien workspace. Alien matches them by their confirmed Slack email. It refuses guests, bots, someone from another Slack workspace, and anyone with no confirmed Slack email that matches a member of your Alien workspace.

In the dashboard, the CLI, and the API, a teammate other than the requester approves. An AI agent that holds your token can't approve its own access.

Customer approves

The Slack card in the shared (Slack Connect) channel has Approve for 6 hours and Deny, and the customer's click decides. It works in either app. The card shows who asked, why, the deployment, the access and its window, and when the request expires.

Alien records who clicked and which app carried the click. It refuses bots, guests, anyone from your own Slack workspace or your Enterprise Grid org, and anyone whose Slack email belongs to a member of your Alien workspace, so your team can't approve a customer's request by mistake. A customer in another Slack organization, through Slack Connect, can approve even when Slack shows no email on their profile.

On Kubernetes Remote Operator deployments, the customer can also approve with kubectl in their cluster. See Access requests.

The dashboard, the CLI, and the API refuse to approve or deny for a Customer group. The API returns 403 with ACCESS_REQUEST_CUSTOMER_APPROVES.

Slack approval

Slack approval prevents mistakes, not deliberate cheating. You route Slack identity, and with your own Slack app you hold its signing secret. A card the customer decided reads Approved in Slack by @dana (Slack workspace), so nobody mistakes it for a verified customer identity. A card your team decided names your Slack workspace, from the Alien app's Slack install. Customers who need a guarantee that only they can approve use kubectl on Kubernetes.

Route the card

A request from alien debug --request-access, alien access-requests create, or the API posts an Access request ready card to your Monitor reports channel. Set that channel under Settings → Integrations → Slack. Without one, Alien posts no card.

The engineer routes the card:

  • Send to original thread posts the card in the thread that started the request. It appears only when the request began in a thread.
  • ...or pick a channel posts it to the channel you choose, such as the Slack Connect channel for that customer.
  • Get kubectl command posts only the command, for you to pass on another way. It appears only on Kubernetes.

The engineer's card then reads Approval request sent to <#channel>, and the card appears there.

The routing card always comes from the Alien app. The approval card it sends, with Approve and Deny, comes from your own Slack app when you connect one, on Team and Customer groups alike. Invite that app to the channel first.

After a decision

Every card for the request drops any buttons and says what happened:

  • Approved, with who approved and when access ends
  • Denied, with who denied
  • Expired without a decision
  • Revoked, with Access has ended.

An approval lasts up to 6 hours and never outlasts the time the engineer asked for. Revoking a request ends a running debug session within seconds.

Troubleshooting

You seeWhat it means
ACCESS_REQUEST_CUSTOMER_APPROVESThe customer approves this group's requests, on the Slack card or with kubectl on Kubernetes. Switch Who approves access requests to Team only if the customer agreed to let your team approve.
A Slack click on a Customer card is refusedThe person is a bot, a guest, from your own Slack workspace or your Enterprise Grid org, or has an email that belongs to a member of your Alien workspace. The customer's own people approve. A customer in another Slack organization can approve even when Slack shows no email on their profile.
This access request is <status>, so it can no longer be approved or denied.Someone already decided the request, or it expired or was revoked. Ask for a new request.
A Slack click on a Team card is refusedThe person is a guest, a bot, or someone from another Slack workspace, or has no confirmed Slack email that matches a member of your Alien workspace. Add them with the email they use in Slack, or approve in the dashboard.
This card is no longer valid. Ask for a new access request.Alien didn't post this card, or posted it before Slack approvals were recorded. Ask for a new request.
No card in SlackSet a Monitor reports channel, and invite the bot to it.
Invite @<app name> to #<channel>, then try again. Nothing was sent.Your own Slack app isn't in that channel. See Your own Slack app.

A click on a card for an expired request reports that the request has ended.

Next

On this page