From 0c7ff3a4c0bb31fee9f523de97ff2b3b47a82f8c Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Wed, 4 Feb 2026 13:26:00 +0000 Subject: [PATCH 1/3] getting-started: update user-management.mdx Password validation logic now explicitly allows square brackets and defines the exact set of accepted special characters. Add a concise 'Password requirements' section so users can create valid admin and user passwords when deploying or using the sign-up API. --- getting-started/user-management.mdx | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/getting-started/user-management.mdx b/getting-started/user-management.mdx index b7c7685f..c3456403 100644 --- a/getting-started/user-management.mdx +++ b/getting-started/user-management.mdx @@ -10,13 +10,29 @@ When you deploy OpenOps for the first time, it creates an admin user account. Th The admin user account created this way has exactly one distinction: it can be used to create other user accounts. +## Password requirements + +When creating a user (including the initial admin user), use a password that: + +* Is 8 to 64 characters long +* Contains at least one lowercase letter +* Contains at least one uppercase letter +* Contains at least one number +* Contains at least one special character + +OpenOps accepts alphanumeric characters and the following special characters: + +```text +! @ # $ % ^ & * ( ) _ + - = [ ] { } ; ' : " \ | , . < > / ? +``` + ## Creating new user accounts OpenOps doesn't currently provide a UI for creating user accounts; instead, you can do it with two API calls. The first API call is to sign in the admin user: -``` +```http POST http://your-openops-installation/api/v1/authentication/sign-in Content-Type: application/json @@ -28,7 +44,7 @@ Content-Type: application/json This call will return a JSON object that contains a property called `token`. Copy the value of this property and use it in the authorization header in the next call. This next call actually creates a new user account. Before making the call, in the body, don't forget to specify actual values for the four properties that are left empty in the sample below: -``` +```http POST http://your-openops-installation/api/v1/authentication/sign-up Authorization: Bearer your-admin-token Content-Type: application/json From 041c5e4578ad48701625672909f4d78c00f15519 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Wed, 4 Feb 2026 13:28:29 +0000 Subject: [PATCH 2/3] ai-assistance: update overview.mdx AI chat server-side message handling tracks tool-error events and marks tool outputs as errors. Add a single sentence so users understand how tool failures appear in the AI assistant chat. --- ai-assistance/overview.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ai-assistance/overview.mdx b/ai-assistance/overview.mdx index 014c576f..f67c15b4 100644 --- a/ai-assistance/overview.mdx +++ b/ai-assistance/overview.mdx @@ -48,6 +48,8 @@ It can also work with Amazon MCP servers, namely AWS Cost Explorer MCP Server, A When available, the AI assistant includes reasoning in its replies, showing which tools (such as MCP servers) it used, displaying the raw data retrieved from those tools, and outlining next steps in plain language. +If a tool call fails, OpenOps marks the tool output as an error and displays the error text in the chat. + ### AI Step action The **AI Step** action lets you run AI prompts in a separate step in your workflow, using outputs of its previous steps as context. From 744112207f45f1e257f5aff90ed09c119de1be9c Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Wed, 4 Feb 2026 13:29:36 +0000 Subject: [PATCH 3/3] ai-assistance: update overview.mdx Fix internal link formatting to use an absolute doc-root path as required by the style guide. --- ai-assistance/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ai-assistance/overview.mdx b/ai-assistance/overview.mdx index f67c15b4..4059c89d 100644 --- a/ai-assistance/overview.mdx +++ b/ai-assistance/overview.mdx @@ -54,7 +54,7 @@ If a tool call fails, OpenOps marks the tool output as an error and displays the The **AI Step** action lets you run AI prompts in a separate step in your workflow, using outputs of its previous steps as context. -You add **AI Step** as you would [add any other action](workflow-management/building-workflows#adding-more-actions). You then specify a prompt in the **Prompt** field and any relevant outputs of previous steps in the **Additional input** section: +You add **AI Step** as you would [add any other action](/workflow-management/building-workflows#adding-more-actions). You then specify a prompt in the **Prompt** field and any relevant outputs of previous steps in the **Additional input** section: Alternatively, you can combine prompt text and outputs from previous steps in the **Prompt** field.