Skip to content

Guide for requesters

  1. In Slack, run /actagate → select a catalog item → complete the form → submit
  2. You receive a confirmation DM, and an approval card is sent to each approver
  3. Follow progress in DM notifications or under “My requests” on the Web

You can also start on the Web from a “Quick request” tile on Home or from the “New request” screen.

Using the request screen (propose → review → submit)

Section titled “Using the request screen (propose → review → submit)”

“New request” /requests/new has three steps.

  1. Propose — Describe what you want in the search box at the top and the closest catalog item is proposed with its form opened. You can also pick a catalog item directly.
  2. Review — As you fill in the form, the execution plan that approvers will see (changes, cost, approval route, and plan hash) updates on the right in real time, so you can confirm exactly what will run.
  3. Submit — Select “Submit this request” to create the request and send approval cards to the approvers.

When you need both a Google account and shared-drive permission, select multiple catalog items on the “New request” screen and submit them as one request. Approval routes are merged automatically: the same approver acts only once, while independent approvers receive cards in parallel. This minimizes the time spent waiting for approvals.

Start here when you are stuck. Describe what you want in the AI intake at the top of Home, in your own words. For example, “A new employee joining next month needs drive access” returns a suitable catalog item and proposed form values such as the person’s name and permission level.

Start without waiting for approval (declaration)

Section titled “Start without waiting for approval (declaration)”

For a low-risk activity, run /actagate declare details to declare that you are proceeding. Your manager is notified, and the declaration is confirmed automatically unless they stop it within 24 hours (silence means consent). Confirmation and veto are both recorded, preventing later disputes.

When a manager or reviewer says “OK” in chat, simply add the :actagate: reaction to that message. The ledger records who approved what and when. If a formal request later becomes necessary, open “Stamps” on the Web and promote the record into a request.

“My requests” /requests lists only the requests you submitted, and nobody else’s. It is split into three segments.

  • In progress — Waiting for approval or execution
  • Returned / needs action — Returned or withdrawn items; fix them with “Edit and resubmit”
  • Completed — Requests that were approved or rejected

Each row shows progress (received → approved → executed → done) and a one-line status.

Opening a single request shows its progress (which steps are approved and who currently holds it) and what happens next (automatic execution or a runbook, the notice date, and the revocation date). Approvers and administrators also see an “Open in workspace” link.

The reason arrives by DM. Correct the request and submit it again.

When an approver returns a request, you receive a DM containing the reason. Select “Edit and resubmit” to open a form prefilled with the original values. For a bundled request, values for every catalog item in the bundle are carried forward, so there is nothing to type again.

If you need to make a correction while your own request is still pending, select Withdraw on the request details page. You can then resubmit from the same prefilled form.

The original request is never edited after a return or withdrawal. Resubmission creates a new request and a new plan, linked in both directions in the UI. The original plan and audit record remain unchanged.

“What you have” /mine lists the items issued to you after approval (accounts, permissions, SaaS subscriptions…). Items with an expiration come first, and each row shows the monthly cost, the expiration (days remaining and notice date), and a link to the request that justified it. Use the segments to switch to revoked items. Revocation is an administrator task, so it does not appear here.