Skip to main content

​
Interactive Tutorial

Coming soon: Interactive Clueso video will be available here. For now, follow the step-by-step guide below.

​
Overview

The dual environment system in gu1 allows you to work with two isolated environments within the same organization:
  • Production: Real data, active clients, operational rules
  • Sandbox: Safe testing environment, isolated data, free experimentation
Advantage: Test new rules, configurations, and integrations in Sandbox before activating them in Production, without risking your real data.

​
When to Use Each Environment

Production

Day-to-day operations
  • Real client onboarding
  • Production alert analysis
  • Ongoing investigations
  • Approval/rejection decisions
  • Active integrations
  • Real-time webhooks

Sandbox

Testing and experimentation
  • Test new rules
  • Validate integrations
  • Train new analysts
  • Simulate complex scenarios
  • Adjust configurations
  • Develop custom workflows

​
Steps to Switch

1

Locate the Environment Selector

In the top-right corner of the dashboard, next to your username, you’ll see a toggle or dropdown indicating the current environment:
  • 🟢 Production (green)
  • 🟡 Sandbox (yellow/orange)
2

Click the Selector

Click the toggle or dropdown to open the environment selection menu.
3

Choose the Environment

Select the environment you want to switch to:
  • Production: To work with real data
  • Sandbox: For testing and experimentation
4

Confirm the Switch

The dashboard will automatically reload and you’ll see:
  • Visual indicator of the current environment
  • Badge in the top corner (Sandbox will have a yellow/orange badge)
  • Data corresponding to the selected environment
Important: All your actions (creating entities, rules, alerts) will occur in the currently selected environment. Always check the indicator before making critical changes.

​
Differences Between Environments

​
Isolated Data

Real client data
  • Real entities (people, companies)
  • Active alerts and investigations
  • Complete decision history
  • Integrations connected to real systems
  • Webhooks sent to production endpoints

​
Rules and Configurations

Each environment has its own rules, but you can:
  1. Create rule in Sandbox to test
  2. Validate with test data
  3. Promote to Production when ready
Rule promotion:
# Via interface
Settings > Rules > [Select rule] > Promote to Production

# Via API
POST /api/rules/{ruleId}/promote
Promotion copies the rule from Sandbox to Production but doesn’t activate it automatically. You need to manually activate it after promotion.
Integration configurations are shared, but you can:
  • Use different credentials per environment
  • Disable integrations in Sandbox
  • Configure test mode for external APIs
Example: ComplyAdvantage
  • Production: Real credentials, charged queries
  • Sandbox: Test credentials, free queries (if available)
Configure at: Settings > Integrations > [Integration] > Environment Settings
Yes, but you control the behavior:Production:
  • Webhooks always active
  • Sent to production endpoints
  • Failures generate critical alerts
Sandbox:
  • Webhooks can be globally disabled
  • Can be redirected to test endpoints
  • Failures don’t generate critical alerts
Configure at: Settings > Webhooks > Sandbox Behavior
{
  "sandbox": {
    "enabled": true,
    "redirectTo": "https://webhook-test.com/sandbox",
    "muteErrors": true
  }
}
Yes, users and teams are shared between environments:
  • Same organization members
  • Same permissions and roles
  • Same configured teams
But: Each user can work independently in each environment. For example:
  • Analyst A is in Production reviewing real alerts
  • Analyst B is in Sandbox testing a new rule
Both can work simultaneously without conflict.
Yes, you can copy data from Production to Sandbox for realistic testing:Via Interface:
  1. Go to the entity in Production
  2. Click Actions > Copy to Sandbox
  3. The entity (and optionally its relationships) will be copied
Via API:
POST /api/entities/{entityId}/copy-to-sandbox
{
  "includeRelationships": true,
  "includeDocuments": false,
  "anonymize": true
}
Privacy: When copying to Sandbox, consider anonymizing sensitive data (SSN, emails, etc.) to protect client privacy.
You cannot copy from Sandbox to Production directly (for security). You need to recreate entities manually or via API.

​
Visual Indicators

To avoid confusion, gu1 offers multiple visual indicators:

​
On the Dashboard

Environment Badge

Top-right corner
  • 🟢 PRODUCTION (green)
  • 🟡 SANDBOX (yellow/orange)

Background Color

Subtle color change
  • Production: standard background
  • Sandbox: slight yellow/orange tint in header

Favicon

Browser tab icon
  • Production: standard logo
  • Sandbox: logo with orange dot

​
In Code (For Developers)

If you’re developing custom integrations, you can detect the environment: 
// Via API
const response = await fetch('https://api.gu1.ai/me', {
  headers: { 'Authorization': `Bearer ${apiKey}` }
});
const { currentEnvironment } = await response.json();
console.log(currentEnvironment); // "production" or "sandbox"

// Via SDK
import { GueoClient } from '@gueno/sdk';
const client = new GueoClient({ apiKey });
const environment = client.getCurrentEnvironment();

​
Common Use Cases

​
1. Test New Rule

1

Switch to Sandbox

Click the selector and choose Sandbox.
2

Create the Rule

Go to Rules > Create Rule and configure the new rule.
3

Test with Data

  • Use existing test data in Sandbox
  • Or copy real entities from Production (anonymized)
4

Validate Results

Check if the rule generates expected alerts and has no false positives.
5

Promote to Production

When satisfied: Rules > [Your rule] > Promote to Production.
6

Activate in Production

Switch to Production and activate the promoted rule.

​
2. Train New Analyst

1

Create Test Data

In Sandbox, create fictional entities representing different scenarios (PEP, fraud, etc.).
2

Configure Training Rules

Activate rules that generate alerts for created scenarios.
3

Invite the Analyst

Add the new member with Viewer role initially.
4

Guide to Switch to Sandbox

Show how to switch to Sandbox and explain it’s a safe environment.
5

Monitor Progress

Let the analyst practice alert review, investigation creation, etc.
6

Promote to Production

When ready, change role to Analyst and guide to work in Production.

​
3. Validate Integration

1

Configure in Sandbox

Go to Settings > Integrations and configure the new integration with test credentials.
2

Run Tests

Create test entities and execute the integration manually.
3

Check Logs

Review logs at Settings > Integrations > [Integration] > Logs.
4

Adjust Settings

Fix errors and refine parameters until it works perfectly.
5

Update Credentials in Production

Switch to Production and update with real credentials.
6

Activate in Production

Enable the integration and monitor first uses.

​
Best Practices

Always Test First

Sandbox → ProductionNever create or modify rules directly in Production. Always test in Sandbox first to avoid negative impacts.

Check Environment

Before each important actionAlways check the badge in the top-right corner before:
  • Creating rules
  • Running integrations
  • Approving/rejecting entities
  • Exporting data

Use Realistic Data

Copy from ProductionFor more accurate testing, copy real entities from Production to Sandbox (anonymized). This ensures your rules work with real data.

Document Tests

Validation historyKeep a record of:
  • Which rules were tested
  • Which scenarios were validated
  • Results obtained
  • Adjustments made
This helps with audits and onboarding new members.

​
Limits and Quotas

Sandbox has different limits from Production to protect resources:
ResourceProductionSandbox
EntitiesUnlimited (plan)1,000
Alerts/monthUnlimited (plan)500
AI Analysis/monthPer plan50
Integrations/dayUnlimited (plan)100
Webhooks/dayUnlimited200
Exports/day103
To increase Sandbox limits, contact support@gueno.com

​
Keyboard Shortcuts

Productivity: Use shortcuts to quickly switch between environments:
  • g + e - Open environment selector
  • p - Switch to Production (when selector open)
  • s - Switch to Sandbox (when selector open)
  • ? - View all available shortcuts

​
Frequently Asked Questions

Yes! You can completely clear Sandbox without affecting Production:Settings > Sandbox > Reset SandboxThis removes:
  • All test entities
  • All alerts and investigations
  • Action history
Doesn’t remove:
  • Rules (you can choose to keep or delete)
  • Integration configurations
  • Users and teams
Included in your plan, no additional cost!
  • All plans (Starter, Professional, Enterprise) include Sandbox
  • Quota limits are lower (see table above)
  • AI analyses in Sandbox consume from your total quota
Not currently. Each organization has:
  • 1 Production environment
  • 1 Sandbox environment
If you need multiple test environments, consider:
  • Creating a separate organization
  • Using development branches (for API integrations)
  • Contacting our Enterprise team for custom solutions
No problem! Data created in Sandbox stays isolated there.If you accidentally:
  • Create entities in Sandbox: doesn’t affect Production
  • Create rules in Sandbox: doesn’t affect Production (until you promote them)
  • Run integrations: uses test credentials
Tip: Configure environment notifications at Settings > Notifications to receive a reminder when switching.

​
Next Steps

Create Rules

Learn to create and test rules in Sandbox

Configure Integrations

Set up integrations with test credentials

Environments API

Manage environments programmatically

Rule Promotion

Complete guide on promoting configurations

​
Need Help?

Last updated: January 2025