Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ai-assistance/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -48,11 +48,13 @@ 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.

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:
<NarrowImage src="/images/access-llm-ask-ai-action.png" alt="AI Step" />

Alternatively, you can combine prompt text and outputs from previous steps in the **Prompt** field.
Expand Down
20 changes: 18 additions & 2 deletions getting-started/user-management.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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
Expand Down