Getting Started as an Admin

Summary
Admins set up and manage the Stacksona Gate workspace for their team. They create agents, configure tools and rules, assign reviewers, and manage user access.
Who this article is for
Use this article if you are an Admin responsible for setting up Stacksona Gate for your team, or if you are a Reviewer who needs to understand how requests are routed and reviewed.
In this help center, Admin means the person managing your team’s Stacksona Gate workspace. Admins manage agents, tools, rules, and team access from the Admin area of the product. The in-app documentation describes the Admin area as the place where admins manage agents, tools, rules, and team access. 
What Admins manageAdmins can:

• Register AI agents that send requests to Stacksona Gate.
• Create tools that represent actions agents may perform.
• Configure rules for when actions are allowed, rejected, or sent to review.
• Assign reviewers to agent workflows.
• Manage users and roles.
• Review audit and webhook activity available in the workspace.
• Help developers connect agent workflows to Stacksona Gate.

Stacksona Gate includes tenant-scoped human access, agent API keys, task/activity logging, tools and approval rules, inbox review actions, webhook decisions, and audit exports. 
Step 1: Create an agentAgents are the AI systems or workflows that send activity and decision requests to Stacksona Gate.
To create an agent:

1. Go to Admin → Agents.
2. Create a new agent.
3. Give the agent a clear name.
4. Assign the agent to a reviewer.
5. Save the generated API key.

Important: The API key is shown only once and starts with sg_. Store it securely. If the key is lost or compromised, regenerate it from the agent settings.
Step 2: Configure how the agent receives decisionsEach agent needs a way to receive approval or rejection decisions.
In Admin → Agents, configure the agent’s decision transport:

• Polling: The agent checks Stacksona Gate at regular intervals for a decision.
• Webhook: Stacksona Gate sends the decision to your endpoint when a reviewer decides.

Use polling for the simplest setup. Use webhooks if your team has a reliable endpoint that can receive decision callbacks. The product docs describe polling and webhook transport as agent settings under Admin → Agents. 
Step 3: Register toolsTools are the actions your AI agent may ask to perform.
Examples:

• issue_refund
• send_email
• delete_record
• update_customer_plan
• deploy_change

To register a tool:

1. Go to Admin → Tools.
2. Create a tool.
3. Use the exact tool name your agent will send.
4. Choose a default action.
5. Add rules if needed.

The tool name in Stacksona Gate must exactly match the tool name used by the agent. The in-app Admin guide explains that tools are created in Admin → Tools and should use the exact names agents request. 
Step 4: Set the default action for each toolEach tool has a default action. The default action applies when no rule matches.
Available default actions are:

• Allow: Automatically approve the action.
• Review: Send the action to a human reviewer.
• Reject: Automatically deny the action.

For sensitive or high-impact actions, use Review as the safest default.
Example setup:
ToolSuggested default actionissue_refundReviewsend_emailReviewlookup_customerAllowdelete_recordReject or Reviewchange_subscriptionReview
The Admin guide lists the available default actions as allow, review, and reject. 
Step 5: Add review rulesRules let Stacksona Gate decide what happens based on request details.
For example, you can create rules such as:

• Allow refunds under $50.
• Review refunds from $50 to $500.
• Reject refunds over $500.
• Review requests where the reason contains fraud.
• Review emails sent to specific domains.

Rules usually check values in the request payload, such as:

• amount
• currency
• customer_id
• email
• reason
• risk_score

Common rule types include:

• Upper limit
• Lower limit
• Between
• Contains
• Regex

Use clear and consistent payload fields so your rules can match requests correctly.
Step 6: Assign reviewersReviewers are the people who evaluate pending requests in the inbox.
A reviewer can:

• Open the inbox.
• Review pending requests.
• Read the subject, risk level, summary, payload, timeline, and conversation log.
• Approve requests.
• Reject requests.
• Save notes without making a final decision.

The reviewer guide explains that reviewers use the inbox to evaluate requests and approve, reject, or save notes. 
Step 7: Manage users and accessGo to Admin → Users to manage team members.
Common roles are:

• Reviewer: Can view and decide requests in the inbox.
• Auditor: Can view logs and decisions without making changes.
• Admin: Can manage settings, agents, tools, and users.

Use the lowest level of access each person needs.
For example:

• Give support leads the Reviewer role.
• Give compliance users the Auditor role.
• Give workflow owners or operations leads the Admin role.

The in-app docs list Reviewer, Auditor, and Admin as the main roles under Admin → Users. 
Step 8: Help developers connect the agentAfter agents and tools are configured, give your developer:

• The Stacksona Gate base URL.
• The agent API key.
• The exact tool names to use.
• The expected payload fields for rules.
• Whether the agent should use polling or webhooks.
• Any review policy requirements.

Developers will update the agent to:

1. Log task events.
2. Request a decision before gated actions.
3. Wait if the response is pending_review.
4. Continue only if the action is allowed or approved.
5. Stop if the action is rejected.

Step 9: Test the review flowBefore using Stacksona Gate in production, run a test request.
Recommended test:

1. Create or select an agent.
2. Create a tool.
3. Set the tool default action to Review.
4. Send a test decision request from the agent.
5. Confirm the request appears in the inbox.
6. Have a reviewer approve or reject it.
7. Confirm the agent receives the decision by polling or webhook.