Account Name
- Any label for your reference, e.g.
Production.
Admin Onboarding Guide
Take a brand-new DevAutOps organization from the welcome email to a fully unlocked console. Follow each setup step in order, then use the in-app tour to learn the day-to-day workflow.
Last updated 4 September 2026 For your organization's Admin
What you'll need
Gather these before you begin so you're not switching tabs mid-setup:
- Access to the email inbox that received your DevAutOps welcome email.
- Credentials for at least one cloud provider you want DevAutOps to manage: an Azure service principal, an AWS IAM access key pair, or a GCP service account key — see Step 6 for exactly what's needed for each.
- An API key from an AI provider (OpenAI, Anthropic, or similar), if you want AI-assisted features like chat, form generation, and document generation available from day one.
- SMTP credentials for the mailbox you want DevAutOps sending from — this powers one-time codes, password resets, and teammate invites, so it's worth setting up during onboarding rather than later.
- An authenticator app on your phone (Google Authenticator, Authy, 1Password, or similar) if you plan to enable two-factor authentication.
Who this guide is for: only the account that receives the welcome email — your organization's Admin — completes this checklist. Teammates your Admin invites afterward sign in with their own credentials and, at most, are asked to set up two-factor authentication if your organization requires it. If you're a teammate, you can stop after Step 2.
Check your inbox
Once DevAutOps provisions your organization, you'll receive one or two emails from "DevAutOps Admin Portal" <info@devautops.com>. They can arrive together or separately — don't worry if the second one takes a little longer.
- Welcome email — subject line "Your DevAutOps account for [Your Organization] is ready." Contains your sign-in URL, organization name, email address, and a temporary password.
- License key email — subject line "Your DevAutOps license key for [Your
Organization]." Contains your license key, formatted like
DA-XXXX-XXXXXXXXXXXXXXXXXXXXXXXX. You'll use this in Step 4.
Save the temporary password before you close this email. It's shown only once and only here. You'll use it to sign in in the next step, then you'll be asked to replace it with a password of your own in Step 5.
Screenshot placeholder
The welcome email, with sign-in URL, organization, email, and temporary password
visible.
Screenshot placeholder
The license key email, with the key visible.
Sign in for the first time
- Open the sign-in URL from your welcome email.
- Enter your Organization name exactly as it appears in the email, your Email address, and the temporary Password from the same email.
- Select Sign In.
Copy the temporary password exactly — no trailing spaces. SMTP isn't configured yet at this point (that's Step 8), so the "Forgot password" email-reset flow won't be able to send you a code until then. If the temporary password stops working before you've changed it, contact your DevAutOps representative to have it reissued rather than using "Forgot password."
If two-factor authentication is already enabled on your account, you'll also be asked for a 6-digit code from your authenticator app before you're signed in — this won't apply on a brand-new account until you complete Step 9.
Screenshot placeholder
The sign-in screen, showing Organization, Email, and Password fields.
Meet your setup checklist
As soon as you sign in, a banner titled "Welcome — finish setup to continue" appears at the top of the console. It always tells you which step to do next, and the rest of the app unlocks only once every step below is checked off.
Every step below lives under Settings, reachable from the console's main navigation — that's the one part of the app open to you before the checklist is complete.
Screenshot placeholder
The "Welcome — finish setup to continue" banner at the top of the console.
Attach your license key
- Go to Settings → License.
- You'll see a License Required badge and the message "This organization has no license key attached. Enter one below to unlock the app."
- Paste the license key from your license key email (
DA-XXXX-XXXXXXXXXXXXXXXXXXXXXXXX) into the field. - Select Save.
Once verified, the badge turns to Active, and you'll see your plan name and expiry date. A confirmation reading "License verified — plan: [Plan Name]" appears briefly.
This tab is only visible to the Admin account. If your license later expires or is revoked, this same screen is where you'll paste a renewed key to restore access — the badge and message update to reflect the current status.
Screenshot placeholder
Settings → License, before a key is entered.
Screenshot placeholder
Settings → License, after the key is verified — Active badge, plan and
expiry.
Change your password
- Go to Settings → Account and find Change Password.
- Enter your Current Password — the temporary one from your welcome email — and select Verify.
- Enter a New Password and repeat it under Confirm Password.
- Select Save.
Choose something strong and unique — DevAutOps sign-in is organization + email + password only, with no single sign-on, so this password is the sole key to your Admin account (alongside two-factor authentication, once you enable it in Step 9).
Screenshot placeholder
Settings → Account → Change Password.
Connect a cloud account
Go to Settings → Cloud Accounts and choose the provider tab for AWS, Azure, or GCP. You only need to connect one account to satisfy this step — add more later, and mark any one of them "default," from the same screen.
Screenshot placeholder
Settings → Cloud Accounts, showing the AWS / Azure / GCP provider tabs.
Azure
Azure connections use an Azure AD service principal — there's no OAuth consent screen, you create the app registration in Azure and paste its credentials here.
The service principal needs the Reader role at subscription scope. Azure Resource Graph doesn't raise an error on missing permissions — it silently returns no results — so a permissions problem here won't surface as a visible error. If resources don't show up after connecting, this is the first thing to check.
| Field | What to enter |
|---|---|
| Account Name | Any label for your reference, e.g. Production. |
| Tenant ID | Your Azure AD tenant ID. |
| Client ID (App ID) | The service principal's application (client) ID. |
| Client Secret | A client secret generated for that app registration. |
| Subscription ID | The Azure subscription the service principal has Reader access to. |
| Region | Where Functions deployed under this account are provisioned, e.g. eastus. Must support
Flex Consumption for your subscription — checked automatically when you save. |
Tenant ID
- Your Azure AD tenant ID.
Client ID (App ID)
- The service principal's application (client) ID.
Client Secret
- A client secret generated for that app registration.
Subscription ID
- The Azure subscription the service principal has Reader access to.
Region
- Where Functions deployed under this account are provisioned, e.g.
eastus. Must support Flex Consumption for your subscription.
Screenshot placeholder
The "Add Azure Account" form, fields filled in (secret redacted).
AWS
AWS connections use a static IAM access key pair.
| Field | What to enter |
|---|---|
| Account Name | Any label for your reference, e.g. Production. |
| Access Key ID | e.g. AKIAIOSFODNN7EXAMPLE. |
| Secret Access Key | The matching secret key for that access key. |
| Default Region | Chosen from a dropdown, e.g. us-east-1. |
Account Name
- Any label for your reference, e.g.
Production.
Access Key ID
- e.g.
AKIAIOSFODNN7EXAMPLE.
Secret Access Key
- The matching secret key for that access key.
Default Region
- Chosen from a dropdown, e.g.
us-east-1.
Screenshot placeholder
The "Add AWS Account" form, fields filled in (secret redacted).
GCP
GCP connections use a service account key in JSON format — paste it directly or upload the key file.
| Field | What to enter |
|---|---|
| Account Name | Any label for your reference, e.g. Production. |
| Service Account Key (JSON) | Paste the full key JSON, or use "Upload key file" to select the downloaded .json file.
|
| Default Region | Chosen from a dropdown, e.g. us-central1. |
| Billing Export Table (optional) | The BigQuery table from Billing → Billing export, e.g.
my-project.billing_export.gcp_billing_export_v1_XXXXXX. Leave blank if you haven't set up
billing export — GCP has no ad-hoc cost API, so this is the only way DevAutOps can answer cost
questions for this account. |
Account Name
- Any label for your reference, e.g.
Production.
Service Account Key (JSON)
- Paste the full key JSON, or use "Upload key file" to select the downloaded
.jsonfile.
Default Region
- Chosen from a dropdown, e.g.
us-central1.
Billing Export Table (optional)
- The BigQuery table from Billing → Billing export. Leave blank if you haven't set that up.
Screenshot placeholder
The "Add GCP Account" form, fields filled in (key redacted).
Configure an AI provider
Go to Settings → AI Providers. This key powers chat, form generation, document generation, beautification, and the AI App Builder inside DevAutOps. If you configure more than one provider, mark the one you want used by default as Active.
- Choose a Provider from the dropdown — OpenAI, Anthropic (Claude), Google Gemini, Grok, DeepSeek, Kimi, Mistral, Groq, OpenRouter, Together AI, and Perplexity are all supported, alongside AWS Bedrock and Google Vertex AI.
- Choose a Model for that provider.
- Paste your API Key.
- Select Save Key.
Already connected AWS or GCP in Step 6? Choosing AWS Bedrock or
Google Vertex AI here skips the API key entirely — DevAutOps uses the cloud account you
already connected. Just make sure that account has model access (bedrock:InvokeModel for
Bedrock, or the roles/aiplatform.user role for Vertex AI).
Screenshot placeholder
Settings → AI Providers, with Provider, Model, and API Key fields.
Configure SMTP (email delivery)
Go to Settings → Notifications and find SMTP (Email) at the top. Without this configured, one-time codes, password resets, and teammate invites won't be able to send.
| Field | What to enter |
|---|---|
| Host | Your SMTP server, e.g. smtp.gmail.com. |
| Port | Defaults to 587. |
| Use SSL (port 465) | Check this if your provider requires implicit TLS on port 465 instead. |
| Username | Your SMTP account username. |
| Password | Your SMTP account password. |
| Send test email to (optional) | An address to receive a test message. Saving with this filled in both saves your settings and sends the test email in one step — there's no separate "test connection" button. |
Host
- Your SMTP server, e.g.
smtp.gmail.com.
Port
- Defaults to
587.
Use SSL (port 465)
- Check this if your provider requires implicit TLS on port 465 instead.
Username / Password
- Your SMTP account credentials.
Send test email to (optional)
- Saving with this filled in both saves your settings and sends a test email in one step.
Select Save SMTP Settings once the fields are filled in.
Screenshot placeholder
Settings → Notifications → SMTP (Email), fields filled in.
Enable two-factor authentication
Go to Settings → Account and find Two-Factor Authentication, just below Change Password. If your organization requires 2FA, this step is mandatory and, once enabled, cannot be turned off. Otherwise it's optional but recommended.
- Select Set Up 2FA.
- Scan the QR code with an authenticator app (Google Authenticator or any TOTP app). No app handy, or scanning not working? Use "Can't scan? Enter this key manually" to type the secret in directly instead.
- Enter the current 6-digit code from your authenticator app into Verification Code.
- Select Verify & Enable.
Screenshot placeholder
QR code to scan, with the "enter key manually" fallback visible.
Screenshot placeholder
The 6-digit Verification Code field and "Verify & Enable" button.
You're done
Once every step is checked off, the setup banner disappears and the full DevAutOps console unlocks. From here, you can invite teammates and start exploring the product — see the in-app product tour for a walkthrough of day-to-day features, which this guide doesn't cover.
Screenshot placeholder
The dashboard with the onboarding banner gone — setup complete.
Troubleshooting & FAQ
I never received a welcome email
Check spam and promotions folders first. If it's still not there, contact your DevAutOps representative to
have it resent — it always comes from info@devautops.com.
I got one email but not the other
The welcome email and license key email are sent independently and can arrive at different times. If it's been a while and you're still missing one, contact your DevAutOps representative.
My temporary password stopped working before I could change it
Since SMTP isn't configured until Step 8, the email-based "Forgot password" flow can't send you a reset code yet on a brand-new account. Contact your DevAutOps representative to have a new temporary password issued.
I connected Azure, but I don't see any resources
Double-check that the service principal has been granted the Reader role at subscription scope. Azure Resource Graph returns an empty result rather than an error when permissions are missing, so this is easy to miss.
Which region should I pick for my cloud account?
Pick the region closest to where you deploy today. You can connect additional accounts in other regions later from the same Cloud Accounts screen.
I'm a teammate, not the Admin — do I need to do all of this?
No. Sign in with the credentials your Admin gives you. The only thing you may be asked to do is set up two-factor authentication, if your organization requires it — you won't see the license, cloud account, AI provider, or SMTP steps at all.
Getting help
If you get stuck anywhere in this guide, reach out to your DevAutOps representative or support@devautops.com.