> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/developer-tools/automator/automator-version-3.1.md).

# Automator Version 3.1

### Overview

Version 3.1 incorporated several new features:

* Team User Approvals
* All settings can be configured as environment variables
* Support for simplified [Azure Container App](/sso-connect-cloud/jp/device-approvals/automator/azure-container-app.md) deployment
* Support for simplified [AWS ECS Service](/sso-connect-cloud/jp/device-approvals/automator/aws-elastic-container-service.md) deployment
* HSTS is enabled for improved HTTPS security
* IP address filtering for device approval and team approval
* Optional rate limiting for all APIs
* Optional filtering by email domain

### Team User approvals

Version 3.x introduced Team User approvals. This means that users who are provisioned through SCIM and added to teams can be immediately processed by the Automator service (instead of waiting for the admin to login to the console).

To activate this new feature:

* Update your Automator container to the latest version
* Use the `automator edit` command in Keeper Commander to instruct the service to perform device approvals and also perform Team User approvals:

Example:

```
automator edit --skill=team_for_user --skill=device "My Automator"
automator setup "My Automator"
automator init "My Automator"
automator enable "My Automator"
```

{% hint style="info" %}
Team approvals are coming in version 3.2. This current version only performs team user assignments.
{% endhint %}

### All settings can be configured as environment variables

This makes configuration easier when installing Automator in Azure Containers or other Docker-like containers where access to the settings file is difficult.

In Docker, Azure Containers, or other environments that use the `docker-compose.yml` file, you can set environment variables in the docker compose file, for example:

```
services:
  automator:
    container_name: "az-autodock"
    environment:
      - AUTOMATOR_PORT=8090
      - AUTOMATOR_HOST=10.0.0.4
      - DISABLE_SNI_CHECK=true
```

After editing the `docker-compose.yml` file, you will need to rebuild the container if the environment variables have changed. Just restarting the container will not incorporate the changes.

### Advanced Features

[See this page](/sso-connect-cloud/jp/device-approvals/automator/advanced-settings.md) for all of the new and advanced features / settings for the Automator service.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/jp/developer-tools/automator/automator-version-3.1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.