Web Portal Guide
The Atlas Studio Web Portal at studio.atlastechlab.com extends the desktop IDE with:
- Workflow scheduling — cron-based with business calendars
- Runner fleet management — deploy agents to run workflows on your infrastructure
- Team collaboration — shared workflows, credentials, dashboards
- Compliance engine — SOC2/HIPAA/GDPR evidence
- Managed File Transfer (MFT) — scheduled file jobs with PGP/checksum
Signing In
Go to studio.atlastechlab.com/login :
- Email/password — use the credentials from your signup
- SSO — if your organization has SSO configured, click “Sign in with SSO” and enter your work email
New to Atlas Studio? Sign up at studio.atlastechlab.com/signup — free forever, no credit card.
Dashboard
After signing in, you land on the Dashboard which shows:
- Recent workflow runs — last 20 executions with status
- Active incidents — from connected ITSM systems
- Credit usage — AI credits consumed this month
- Runner status — count of online/offline runners
- Team activity — recent actions by team members
Workflow Management
Viewing workflows
Workflows → list of all workflows with:
- Status badge (Active / Paused / Draft)
- Last run time and status
- Next scheduled run
- Owner and tags
Creating a workflow
- Click New Workflow → choose: Create from scratch or Import from IDE (upload JSON)
- Use the visual workflow builder or the Workflow Agent to generate nodes
- Click Save as Draft → then Activate when ready
Scheduling a workflow
Workflows → select workflow → Scheduling tab:
# Run every weekday at 9 AM UTC
Cron: 0 9 * * 1-5
Timezone: UTC
# Enable business calendar
Calendar: US Business Days (Mon-Fri, skip US federal holidays)
# Missed run policy: Skip (don't catch up) or Run immediatelyWorkflow executions
Workflows → select workflow → Executions tab shows:
- Run history with start/end times
- Execution status (SUCCEEDED / FAILED / RUNNING / CANCELLED)
- Node-level status for each step
- Logs and output for each node
Click any execution to see detailed node output, retry a failed node, or terminate a stuck run.
Runner Management
Runners are lightweight agents deployed on your infrastructure that execute workflow nodes.
Deploying a runner
Generate a runner token
Web Portal → Runners → Deploy Runner → copy the registration token (valid 1 hour).
Deploy on your infrastructure
Docker:
docker run -d \
--name atlas-runner \
--restart unless-stopped \
-e ATLAS_RUNNER_TOKEN=your-token \
-e ATLAS_PORTAL_URL=https://studio.atlastechlab.com \
atlastechlab/studio-runner:latestKubernetes:
helm repo add atlasai https://charts.atlastechlab.com
helm install atlas-runner atlasai/studio-runner \
--set runnerToken=your-token \
--set portalUrl=https://studio.atlastechlab.comBare metal / VM:
curl -sL https://downloads.atlastechlab.com/runner/install.sh | \
ATLAS_RUNNER_TOKEN=your-token bashVerify the runner is online
Web Portal → Runners → the new runner appears with status Online.
Runner configuration
Each runner can be tagged for specific workloads:
Tags: production, us-east, kubernetesWorkflows can target runners by tag: Scheduling → Runner Tags → production, kubernetes
Credential Vault
All workflow credentials (SSH keys, passwords, API tokens) are stored in the Vault — AES-256-GCM encrypted at rest.
Adding a credential
Web Portal → Credentials → Add Credential:
| Type | Fields |
|---|---|
| SSH Key | Name, private key, passphrase (optional) |
| Username/Password | Name, username, password |
| API Token | Name, token |
| AWS | Name, access key ID, secret access key |
| TLS Certificate | Name, cert PEM, key PEM |
Using in workflows
In any workflow node that needs auth, select a credential by name:
SSH Node → Authentication → Credential: "prod-server-key"Credentials are injected at runtime — workflow definitions never contain raw secrets.
Compliance Engine (Pro/Enterprise)
Generating a compliance bundle
Web Portal → Compliance → Generate Bundle → select framework:
- SOC2 Type II
- HIPAA
- GDPR
- ISO 27001
The bundle includes:
- Automated evidence (access logs, workflow audit trails, encrypted-at-rest proof)
- Configuration exports
- User access report
Download as ZIP for your auditor.
Policy-as-code rules
Web Portal → Compliance → Policies → define rules like:
- name: "Prod workflows require approval gate"
target: workflows[tags.contains('production')]
rule: nodes.any(type='approval' && before=node_with_risk_high)
severity: errorPolicy violations block workflow activation and appear in the compliance dashboard.
Team Collaboration
Shared dashboards
Save dashboards from the Desktop IDE to the Web Portal: Dashboard Builder → Save to Portal.
Team members can view, clone, and subscribe to dashboards.
Shared runbooks
Runbooks saved to the portal are available to all team members during incidents.
Activity log
Web Portal → Team → Activity → full audit trail of:
- Login events
- Workflow create/edit/run
- Credential access
- Runner deploy/deregister