Getting started

Actagate brings your organization’s “is this okay?” decisions into one place. Requests, approvals, the work that follows them, and the record of who was granted what. Because all of it sits in one place, tracing a decision later does not mean digging through chat, a spreadsheet and your mail.

What Actagate can do

What you want to do	Feature to use
Record an “OK” received in chat	Add the :actagate: reaction (stamp) to the message
Submit a formal request	Run /actagate in Slack, or open “New request” on the Web
Start before approval while giving your manager a right to stop it	/actagate declare (declaration)
Approve a request	Use the Slack DM card or the Web home screen
Review company-issued accounts, permissions, and other assets	Open “What you have” on the Web

First steps (one minute)

1. Set your manager — Run /actagate setup @your-manager in Slack. Request routes that include a “manager” step use this setting.
2. Invite the Bot to a channel — Invite the Bot in each channel where you want to use stamps. Reactions in channels the Bot has not joined cannot be recorded.
3. Add :actagate: to a colleague’s message as a quick test. When “㊞ Recorded” appears, setup is complete.

Getting started without Slack

Slack is optional. Without a connected workspace, requests, approvals, execution and the ledger all work over email and the Web.

1. Sign in — Enter your email address at /login and a sign-in link is emailed to you. The link is valid for 15 minutes and can be used once (see the FAQ “I did not receive the email” if it does not arrive).
2. Members — An administrator invites people by email from “Members” in the workspace, and sets each member’s manager on the same screen.
3. Requests and approvals — Submit requests from “New request” on the portal. Approvers are notified by email and approve on the Web home screen through the link in the message (there is no approval from within the email itself).
4. Connect Slack later — Once an administrator installs the Bot as described in the administrator guide under “Slack integration,” members whose email matches are linked to their Slack accounts automatically and notifications switch to Slack DMs. Stamps (L0) and declarations (L1) become available after that.

Navigating the Web app

The Actagate Web app has two surfaces: the portal and the workspace. Everyday requests and tracking happen entirely in the portal, while approvals and administration happen in the workspace.

The portal (for everyone)

• Home /home — Your pending approvals, quick requests, and recent activity. If you are unsure where to begin, describe the outcome you need in the AI intake, such as “I need AWS access.”
• New request /requests/new — A three-step flow: propose → review → submit. The execution plan that approvers will see appears on the right.
• My requests /requests — A list of the requests you submitted and the progress of each one.
• What you have /mine — Items issued to you after approval (accounts, permissions, SaaS…) with their monthly cost and expiration.

The workspace (only for people who approve or administer)

From the left rail you can reach Approvals (the approval queue), Requests (the whole organization’s list), Ledger, Stamps, Catalog, Members, Observability, and Settings. Enter it from “Workspace” in the upper-right of the portal.

Who can enter the workspace

Only people who meet at least one of the following can enter the workspace.

1. You are an admin or owner of the Slack workspace
2. You are set as someone’s manager
3. You are a member of an approval group
4. You have acted as an approver before (you received and handled an approval card)

Anyone who does not match any of these is sent back to Home (/home?message=workspace_unavailable) when they open a workspace URL. When you only need to approve, you can also act from the Slack DM card.