Settings
This screen aims to allow configuration of users, audit, plugins, and tokens in Sinfonia.
Users
Data Table
| Column | Description |
|---|---|
| User | Name of the user with access |
| User email | |
| Profile | Admin, Dev, User |
| Logs | Log viewing permission |
| Last Login | Date/Time of last login |
| IP | User origin (IP) |
| Modified By | User who made the last modification |
| Actions | Permission to delete or edit the user |
New User
To create a new user with admin/dev profile, click + User.
Admin/Dev
To create a new user with admin or dev profile, click + User.
| Field | Description | Validation |
|---|---|---|
| User | Username. | Must be unique. |
| User email. | Must be unique and in valid format (e.g., user@domain.com). | |
| Profile | User profile. | One of the predefined values: admin, dev, user. |
User
To create a new user with user profile, click + User. Besides the User, Email and Profile fields above, this profile has per-item configurable permissions:
| Field | Description |
|---|---|
| Agents (View) | Agents that the user can view. |
| Bots (View) | Bots that can be viewed. |
| Bots (Run) | Bots that can be executed. |
| View logs | Enables viewing automation logs. |
Delete
To remove a user, click the trash icon in the Delete column.
Tip
A confirmation modal will be requested.
Audit
Refers to monitoring actions performed in the system, such as creation, update, and deletion of bots, agents, users, among others.
| Column | Description |
|---|---|
| User | User who performed the operation. |
| Bot | The bot that underwent the operation. |
| Origin | The IP origin. |
| IP | Which entity was changed. |
| Event | The operation event (create, update, read). |
| Timestamp | Date/Time when the operation occurred. |
| Metadata | View changed data. |
To view metadata, click the icon in the Metadata column.
Plugins
Refers to configuring integrations with external services such as MS Teams, Telegram, Hashicorp, OpenAI, and Automation Anywhere.
Microsoft Teams
To send notifications via Teams, fill in the fields as below and click Save.
| Field | Description |
|---|---|
| URL | Webhook URL generated in Teams. Example: https://outlook.office.com/webhook/.... |
| Send Teams | Enables or disables sending notifications via Teams. |
Telegram
To receive all errors generated by bot executions on Telegram, fill in the field below and click Save.
| Field | Description | Notes |
|---|---|---|
| Chat ID | Telegram chat/bot ID to which error notifications will be sent. | All errors generated by executions are sent to that chat. |
Tip
There is no option to enable/disable sending. To stop the notifications, remove the Chat ID and click Save.
Hashicorp Vault
To synchronize the Hashicorp password vault in Sinfonia, fill in the fields as below and click Save.
| Field | Description |
|---|---|
| URL | Vault URL. Example: http://address:8200 |
| Engine | Name of the “k/v” type vault. Example: secret |
| Secret Path | Path where secrets are stored. Example: secret/data/sinfonia |
| RoleId | Identification hash. Example: f3b6c8d2-1e5a-4c3b-9f0a-1e2d3c4b5 |
| SecretId | Authentication hash. Example: a1b2c3d4-5e6f-7g8h-9i0j-1k2l3m4n5op |
| Disable | Enables or disables synchronization. |
OpenAI LLM
To use AI features, it is necessary to register your valid OpenAI key.
| Field | Description |
|---|---|
| OpenAI Key | OpenAI API key. |
Automation Anywhere
For integration with Automation Anywhere, fill in the fields as below and click Save.
| Field | Description |
|---|---|
| Control Room URL | Control Room URL. Example: https://address |
| Workspace | Workspace name. Example: private |
| User | AA user. |
| Password | AA password. |
| API Key | AA API key. |
| Allow Multiple Logins | Allows simultaneous multiple logins. |
Tokens
Refers to generating and managing authentication tokens for access to Sinfonia API and agent.
Note
For API integrations, use API type tokens.
For agent authentication, use Agent type tokens.
| Column | Description |
|---|---|
| Label | Token name |
| Type | Token type (API or Agent) |
| Token | Token value (click icon to copy to clipboard) |
| Created At | Date/Time when the token was created |
| Created By | User who created the token |
| Status | Token status (Active or Inactive) |
| Actions | Permission to delete the token |
New Token
To create a new token, click + Token.
Fill in the fields as below and click Save.
| Field | Description | Validation |
|---|---|---|
| Label | Token name. | Must be unique. |
| Type | Token type. | One of the predefined values: API or Agent. |
Delete
To remove a token, click the trash icon in the Actions column.
Tip
The number of agent tokens is controlled by the number of agents acquired in the license.