Complete DevAutOps Product Guide

How DevAutOps fits together

DevAutOps turns repeated cloud-operation requests into controlled tools. An administrator connects approved cloud accounts and AI providers. Builders create applications and triggers. Administrators assign access. Operators and teammates run those tools without receiving unrestricted cloud-console permissions.

1. Connect a cloud account
2. Build an app or trigger
3. Assign governed access
4. Run manually or with an AI Job
5. Monitor and audit activity

Terms used throughout the product

Administrator onboarding

This is the complete first-time setup sequence for the organization Admin account. Finish every required item in the setup banner to unlock the rest of the DevAutOps console. Invited teammates do not repeat the organization setup; they sign in with their own credentials and configure two-factor authentication only when your organization requires it.

Before you start

Collect the required credentials before signing in:

• Access to the inbox that received the DevAutOps welcome email.
• Credentials for at least one supported cloud: an Azure service principal, AWS IAM access-key pair, or GCP service-account key.
• An AI-provider API key if you want chat, form generation, document generation, beautification, and the AI App Builder. AWS Bedrock and Google Vertex AI can use a connected cloud account instead.
• SMTP credentials for one-time codes, password resets, and teammate invitations.
• A TOTP authenticator app such as Google Authenticator, Authy, or 1Password if you will enable two-factor authentication.

1. Find your welcome and license emails

After your organization is provisioned, look for one or two messages from “DevAutOps Admin Portal” <info@devautops.com>. They can arrive separately.

2. Sign in for the first time

1. Open the sign-in URL in the welcome email.
2. Enter the Organization exactly as shown in the email, then enter the Admin Email and temporary Password.
3. Select Sign In. Enter a current 6-digit authenticator code too if 2FA is already enabled.

3. Follow the setup checklist

The console displays “Welcome — finish setup to continue” and identifies the next action. Settings remains available while most of the product is locked. Complete these items in order:

1. Attach a license key.
2. Change the temporary password.
3. Connect at least one cloud account.
4. Configure an AI provider.
5. Configure SMTP.
6. Enable 2FA when required by organization policy.

4. Attach the organization license

1. Open Settings → License. This Admin-only tab initially shows License Required.
2. Paste the complete license key from the license email into the field. Remove any accidental spaces around it.
3. Select Save and wait for verification.
4. Confirm that the status changes to Active and that the expected plan and expiry date appear.

If the license later expires or is revoked, return to this screen and attach the renewed key to restore access.

5. Replace the temporary password

1. Open Settings → Account → Change Password.
2. Enter the temporary password as Current Password, then select Verify.
3. Enter a strong, unique New Password and repeat it under Confirm Password.
4. Select Save and use the new password for future sign-ins.

6. Connect at least one cloud account

Open Settings → Cloud Accounts, choose AWS, Azure, or GCP, and add one account to satisfy onboarding. You can add more connections later and mark one as the default. Give every connection a clear name such as Production or Development.

Azure connection

Create an Azure AD service principal and grant it the Reader role at subscription scope. Azure Resource Graph can return no resources—without showing an error—when this permission is missing.

AWS connection

AWS connections use a static IAM access-key pair. Scope its permissions to the services and actions your DevAutOps workflows need.

GCP connection

GCP connections use a service-account JSON key. Paste the complete JSON or upload the downloaded .json file.

7. Configure an AI provider

1. Open Settings → AI Providers.
2. Choose a provider and model. Supported choices include OpenAI, Anthropic, Google Gemini, Grok, DeepSeek, Kimi, Mistral, Groq, OpenRouter, Together AI, Perplexity, AWS Bedrock, and Google Vertex AI.
3. Paste the provider API Key, then select Save Key. If multiple providers exist, mark the preferred one Active.

8. Configure SMTP email delivery

Open Settings → Notifications → SMTP (Email). This connection enables one-time codes, password resets, and teammate invitations.

Select Save SMTP Settings, then confirm the optional test message arrives before inviting teammates.

9. Enable two-factor authentication

Open Settings → Account → Two-Factor Authentication. If your organization requires 2FA, setup is mandatory and cannot be disabled afterward. Otherwise, it is optional but recommended.

1. Select Set Up 2FA.
2. Scan the QR code with a TOTP authenticator. If scanning fails, choose “Can’t scan? Enter this key manually”.
3. Enter the current 6-digit code under Verification Code.
4. Select Verify & Enable.

Confirm onboarding is complete

When every required item is complete, the setup banner disappears and the full console unlocks. Continue with Navigation and access, invite teammates from User management, and create your first governed workflow.

Onboarding troubleshooting

Navigation, cloud context, and access

Use the left sidebar to move between product areas. On desktop, collapse it with the control beside the DevAutOps logo. On mobile, open it from the header. Account-level destinations such as Settings and Help & Guide stay at the bottom.

Select the correct cloud before working

1. Open the cloud-account switcher in the application header.
2. Select AWS, Azure, or GCP, then choose the intended account, subscription, or project.
3. Confirm the account name shown in the header before creating or editing an Intelligent App, Application, Trigger, or cloud-scoped Job.
4. Use the switcher’s management link when you need to add or update a connection.

Understand access levels

• Read access normally lets you open and use assigned resources without changing their definition.
• Write access adds create, edit, status, assignment, and delete controls where applicable.
• Resource-specific access can expose one Application, Trigger, document, or Intelligent App without exposing every resource of that type.
• Cloud-scoped access can differ by provider and connection. Access in one AWS account does not automatically grant access in Azure or GCP.
• Organization-owner actions—such as license configuration, provider credentials, and some publishing/reset actions—remain restricted even when a user can manage related resources.

Dashboard

The Dashboard is the organization’s analytics command center. Open Dashboard after signing in to review activity without visiting every feature page.

What the Dashboard shows

• Headline metrics for users, applications, triggers, documents, and other organization activity.
• Most used and recent resources so you can return to active operational tools quickly.
• Support-ticket status and recent support activity.
• Your effective access summary, which explains what the current account is allowed to see or manage.
• Compact Documentation, Asset Manager, and Secrets summaries.

Use the Dashboard

1. Check the top metrics for unexpected changes or missing activity.
2. Open a resource from the most-used or recent resource table when you need to continue work.
3. Review My Access before reporting a missing action; read-only users intentionally see fewer controls.
4. Select Refresh to reload analytics after a new resource, assignment, or support update.

Ask Cloud

The floating Ask Cloud launcher provides conversational, read-oriented answers about a connected AWS, Azure, or GCP environment. It is available throughout the dashboard when your role grants Ask Cloud access.

1. Open the floating assistant from the lower-right corner.
2. If you have multiple connections, choose the account the question is about. A single connection is selected automatically.
3. Ask a concrete question such as “How many EC2 instances are running?”, “Show my Azure storage accounts,” or “List my GCP VPC networks.”
4. Ask follow-up questions in the same conversation when you need to narrow the result.
5. Use the account selector in the assistant header to switch environments. Switching clears the visible conversation so old answers are not mistaken for data from the new account.

Intelligent Apps

Intelligent Apps use natural language to generate a governed DevOps application. Open AI Apps → Intelligent Apps when you want DevAutOps to help design the form, workflow, cloud actions, validations, output, and documentation together.

Before creating an app

• Select the target cloud account in the header.
• Confirm an AI provider is configured under Settings → AI Providers.
• Make sure your role has create access for Intelligent Apps in that cloud connection.
• Know the desired inputs, operation, safety rules, and expected output.

Create with a prompt

1. Select Create New App, then continue into the builder session.
2. Describe the task, target service, required user inputs, expected result, and any approval or validation rules.
3. Answer clarification questions rather than guessing at missing infrastructure details.
4. Review the generated application form, backend behavior, cloud requirements, and documentation.
5. Test with non-production values first. Inspect generated actions and requested permissions before enabling production use.
6. Save the app, assign access, and change its status to Active only when the result is ready for teammates.

Manage existing Intelligent Apps

Applications

Applications are reusable self-service interfaces for operational tasks. Open AI Apps → Applications to search, run, create, edit, suspend, share, publish, or remove them.

Create an Application manually

1. Select the correct cloud connection, then choose New Project.
2. Give the project a clear name and category that describe the user outcome.
3. Build the input form from fields such as text, choices, date/time, key-value input, buttons, titles, dividers, and layout blocks.
4. Configure each field’s label, placeholder, validation, default value, and required state.
5. Connect the form to the correct Trigger or backend operation and map form values into its payload.
6. Preview the form at desktop and mobile sizes. Test validation, confirmation states, failure messages, and output formatting.
7. Save the Application, keep it suspended while reviewing, then activate and assign it to its intended users or groups.

Operate the Applications list

• Use status filters, category filters, and search to find an app by name or purpose.
• The table shows project ID, name, category, users, last use, creation date, use count, and status when your access permits those columns.
• Change Active to Suspended to stop new use without deleting the configuration.
• Use Assign access to control who can open or change an app.
• Installed App Store items remain managed through their store lifecycle; use update rather than treating them as an unrelated local app.

Triggers

A Trigger is the cloud function that performs an operation for an Application or AI Job. DevAutOps supports AWS Lambda, GCP Cloud Functions, and Azure Functions through the cloud account selected in the header.

Create, deploy, and test

1. Open AI Apps → Triggers and choose New Trigger.
2. Confirm the active cloud, enter the function name and description, and choose the supported runtime and execution settings.
3. For AWS, select the appropriate execution role and any required network, layer, file-system, dead-letter, or architecture settings. GCP uses its service account path; Azure uses a managed identity.
4. Describe the operation for intelligent generation or enter/review code directly.
5. Deploy the function. DevAutOps saves the deployed function as a Trigger record.
6. In Code & Test, inspect the deployed code and JSON test payload, then select Test. Intelligent mode deploys generated fixes but never silently runs the test for you.
7. Review returned output and logs. If intelligent debugging proposes an IAM or code fix, inspect it, deploy it, and run the test again.
8. Select Complete & View Triggers when the Trigger is saved and behaving correctly.

Manage Triggers

• Recent Triggers appear first; use search and pagination for the full list.
• Use status controls to activate or suspend execution.
• Assign resource access to users or groups when the Trigger should be available beyond its creator.
• Edit a Trigger only while its owning cloud account is active.
• Delete only after removing or changing Applications and AI Jobs that invoke it.

Documentation knowledge base

The in-app Documentation area stores generated and uploaded team knowledge. It is separate from this public product guide: your organization controls its folders, documents, and access.

Organize documents

1. Open AI Apps → Documentation.
2. Select New Folder to organize material by project, service, team, environment, or runbook type.
3. Open a folder to make it the destination. Use breadcrumbs to return to parent folders.
4. Select Generate document for AI-assisted documentation, or Upload to add an existing file record.
5. Open a document to read it. Users with write access can edit, download, delete, or manage its access.

Search and access

• Search spans folders and documents. Select a result to jump directly to it.
• Folder navigation controls organization; document assignment controls who can read or change an individual item.
• Read-only users see the knowledge they were granted without upload, generation, or edit actions.
• Use descriptive titles and include the service, environment, owner, prerequisites, rollback, and verification steps in operational runbooks.

App Store

The App Store is the shared automation catalog for reviewed Applications and AI Jobs. Use it to install reusable workflows instead of rebuilding common operations.

Browse and install

1. Open App Store and choose the Applications or Jobs catalog.
2. Filter by cloud, category, item type, installed state, available updates, or items published by your organization.
3. Open a listing to read its description, version, inputs, cloud requirements, documentation, and publisher information.
4. Select install, review the destination cloud/account and required configuration, then complete the setup.
5. Inspect installed behavior before assigning users. Installed Jobs arrive paused so you can configure and review their steps before activation.

Updates and publishing

• An Update available filter identifies installed items with a newer approved version.
• Review release differences and configuration requirements before changing versions.
• Organization owners can publish an eligible local Application or Job and later submit version updates.
• The Submissions page shows everything your organization offered to the store and its review state.
• A submitted update does not replace the catalog version until review is complete.

AI Jobs

AI Jobs coordinate one or more actions on a schedule or event. Open AI Jobs to create, run, pause, edit, inspect, publish, or delete automations.

Choose how the Job starts

Add actions

• Run Trigger invokes an existing cloud Trigger with a configured payload.
• Send Notification delivers email, Slack, or both using saved notification destinations.
• Call Webhook posts a JSON payload to an external HTTPS endpoint.
• Jobs can contain multiple ordered actions. Review each step’s input and failure behavior.

Create and operate a Job

1. Choose Create with AI to describe the automation, or use the manual form for exact schedules, action payloads, and advanced settings.
2. Name the Job, select its starting event, add ordered actions, choose a platform or cloud target, and configure notification recipients.
3. Use Dry run when available to record what would happen without making the external change.
4. Save in Paused state, verify the configuration, then activate it.
5. Select Run now for an immediate execution, and open Run history to inspect succeeded, failed, skipped, running, or dry-run attempts.
6. Pause a Job before editing dependencies or investigating repeated errors. The row’s last-error message provides the quickest failure clue.

Assets and My Assets

Asset Management tracks hardware inventory, software licenses, employee assignments, and procurement requests. Users with read-only asset access see My Assets; asset managers see the organization-wide inventory.

Add inventory

1. Open Assets and select Add asset.
2. For hardware, record the name, category, brand, model, condition, location, stock, low-stock threshold, purchase data, warranty, description, notes, and any custom fields. DevAutOps generates a unique ID for each physical unit.
3. For software, record its type, vendor, website/login URL, license type, seat count, expiry/renewal dates, monthly or annual cost, optional encrypted keys, description, notes, and custom fields.
4. Save and confirm the totals in the Hardware or Software tab.

View and maintain details

• Select the eye action on any Hardware or Software row to view complete details, inventory/license counts, physical unit IDs, dates, costs, custom fields, notes, and record metadata.
• Software details report whether API and license keys are configured without revealing their values.
• Use Edit to correct metadata, add physical stock, add license seats, change thresholds, or archive an unused asset.
• Print hardware unit tags when physical devices need scannable or human-readable labels.

Assign, return, and request

1. Select Assign asset or the assignment action on a row.
2. Choose hardware or software, select the exact hardware unit when applicable, choose the employee, enter an expected return date, and add notes.
3. Use the Assignments tab to mark hardware Returned, Broken, or Repairing. Returning restores inventory availability; active units cannot be assigned twice.
4. Employees use My Assets to see assigned items, dates, status, and notes, or to submit an asset request.
5. Managers review Requests, change the review/procurement state, approve or reject, and hand over approved inventory.

Secrets Manager

Secrets Manager stores credentials as Secret, API Key, OAuth Token, or Password records. Access is account-wide and then narrowed by ownership and sharing rules.

Create and view a secret

1. Open Secrets and choose Create secret.
2. Select the type, enter a recognizable name and description, then provide the secret value and any supported metadata.
3. Save. Values remain concealed in the inventory list.
4. Use View / Edit to reveal the value only when authorized, copy it when required, or update its record.

Share and control lifecycle

• Use Manage sharing to grant intended users or groups access without distributing the raw value through chat or email.
• Create a one-time link only for a deliberate external handoff. Treat the link as sensitive, set the shortest practical lifetime, and verify the recipient separately.
• Suspend a secret to stop normal use while preserving its record; reactivate after review.
• Review the secret’s action log when investigating who viewed or changed it.
• Delete only after replacing every application, Job, integration, or person that depends on it.

Import and export

Uptime Monitor

Uptime Monitor performs scheduled checks and alerts once per incident rather than once per failed check. It supports HTTPS endpoints, keyword checks, TCP ports, TLS certificates, and domain registrations.

Create the right check

1. Open Uptime Monitor, expand New monitor, and choose the check type.
2. Enter the target and interval. For expiry monitors, set warning and critical days remaining.
3. For an HTTP monitor, configure request method, expected status, optional encrypted headers/body, and keyword requirements as needed.
4. Select alert email recipients and Slack channels from saved destinations, or add a monitor-specific email address.
5. Create the monitor and wait for its first check. Use Refresh when you need the latest state immediately.

Read monitor results

• Up is healthy, Warning is approaching an expiry threshold, Down is failing, and Paused is not checking.
• The Fleet Health panel summarizes state counts and 24-hour endpoint performance.
• Open a monitor to see latency/connect time, uptime, average and p95 response, check history, failure reasons, expiry trend, and incidents.
• One incident groups an entire sustained outage. Recovery closes it; repeated failed checks do not create repeated incidents.
• Pause planned maintenance to prevent misleading failures, then resume afterward.

AI Monitor

AI Monitor shows organization-wide AI calls, estimated spend, token activity, feature usage, models, and users. It measures DevAutOps usage records; it does not replace the AI provider’s invoice.

1. Open AI Monitor.
2. Choose a 7-day, 30-day, or 90-day window.
3. Review headline call, token, and cost totals.
4. Use feature, user, and model filters to isolate the source of a change.
5. Compare Spend by feature, Spend by model, and Calls by user before changing provider configuration or team policy.

Audit Logs

Audit Logs provide a chronological record of important changes. The page is read-only and appears only to users with the dedicated audit-log permission.

• Filter by actor to separate organization-admin and app-user activity.
• Filter by action: Create, Update, or Delete.
• Filter by resource type to focus on Applications, Triggers, assets, secrets, users, roles, and other supported records.
• Use timestamp, actor, resource, and name together when correlating an operational change with an incident.
• Preserve the relevant page or record details when opening a support ticket; do not paste credential values into the ticket.

Users, groups, roles, and resource access

DevAutOps access is assembled from roles, group membership, direct assignments, account-wide capabilities, cloud-scoped service levels, and individual resource grants. Start with least privilege and add access deliberately.

Create a role

1. Open User Management → Roles and select Add Role.
2. Name the role for a job function, not a person—for example, “Platform Operator” or “Asset Viewer.”
3. Select the services the role needs and choose read or write access as appropriate.
4. For cloud-backed Applications, Intelligent Apps, Triggers, and Documentation, select the intended cloud accounts and resource scope.
5. Review the role summary, save, and test it with a non-owner user.

System roles can be edited only where the UI permits and cannot be deleted. Custom roles should be reviewed when a team’s responsibilities change.

Create a group

1. Open User Management → User Groups and select New Group.
2. Name the group for a stable team or function.
3. Assign one or more roles, then add the users who share that responsibility.
4. Save and verify the group’s role and user counts in the list.

Invite and maintain users

1. Open User Management → Users and select Invite User.
2. Enter the username and email, then assign appropriate groups and/or direct roles.
3. Require two-factor authentication for accounts that need stronger sign-in protection.
4. Send the generated credentials through the supported invitation flow. The user changes the temporary password at first sign-in when required.
5. Edit membership and roles as responsibilities change. Remove departed users promptly after transferring ownership and assignments.

Settings

Every user can manage personal account security. Organization owners also see cloud, AI, notification, platform, and license configuration.

Personal security

• Change a temporary or suspected password immediately under Settings → Account.
• Enable two-factor authentication by scanning the QR code with an authenticator app and entering a current six-digit code.
• If the administrator requires 2FA, the rest of the application remains gated until setup succeeds and the session refreshes.

Organization configuration order

1. Verify the license.
2. Connect at least one cloud account and set the intended default.
3. Configure the AI provider and model.
4. Configure SMTP before relying on email OTPs, password resets, invites, or Job/monitor alerts.
5. Add reusable notification recipients and Slack channels.
6. Configure platform integrations only when required by your deployment.

For provider credential fields and the complete first-time sequence, follow the Admin Onboarding Guide.

Subscription

The Subscription page compares plans and limits for Intelligent Apps, custom Applications, Triggers, users, cloud connections, Job runs, generated documentation, secrets, assets, monitors, audit logs, Ask Cloud, enterprise security, and support.

1. Open Subscription.
2. Toggle monthly or annual billing to compare available pricing.
3. Estimate the required users, cloud connections, automation resources, monthly Job executions, monitors, and enterprise features.
4. Select a plan or submit the callback form with your company and automation needs.
5. Use the consultation link when you need architecture, security, private-deployment, SSO/SAML, SLA, or custom-limit guidance.

Support and Help & Guide

Open a support ticket

1. Open Support and create a ticket.
2. Enter a short subject, choose the appropriate priority, and describe the observed result, expected result, exact reproduction steps, time, feature, cloud/provider, and resource ID.
3. Submit and keep the ticket number. Open the ticket detail page to read replies and continue the conversation.
4. Never include passwords, API keys, license keys, private keys, session tokens, or full secret exports.

Use Help & Guide

The in-app Help & Guide page contains expandable FAQs. App users can submit a question when an existing answer does not cover the issue; organization administrators can respond through the supported FAQ workflow.

Security and reliability practices

• Use dedicated cloud identities for DevAutOps and grant the minimum actions and scopes each workflow requires.
• Separate production and non-production cloud connections; confirm the active connection before every create, edit, deploy, or test operation.
• Test new Triggers, Applications, and Jobs against non-production resources and bounded inputs.
• Keep production Applications and Jobs suspended until review and access assignment are complete.
• Require two-factor authentication for privileged users and remove inactive accounts quickly.
• Share secrets through Secrets Manager rather than messaging tools; prefer inventory-only exports for audits.
• Use groups and job-function roles instead of accumulating one-off direct permissions.
• Monitor certificate/domain deadlines, AI spend, and audit activity regularly.
• Pause Jobs and monitors during planned maintenance when their actions or alerts would be misleading.
• Document owners, prerequisites, verification, failure handling, and rollback for every production automation.

Common troubleshooting