Enable AI agents to securely access parameters in AI Desktop Actions
Summarize
Summary of Enable AI agents to securely access parameters in AI Desktop Actions
This feature allows AI agents to securely access sensitive and dynamic input values, such as credentials, via Desktop Action Parameter records. It ensures sensitive data is protected and dynamically supplied during agent execution, improving security and flexibility when AI agents perform desktop actions.
Show less
Only users with the snaia.admin role can create Parameter records, which store named values that AI agents reference during execution. Each distinct sensitive value requires its own Parameter record.
Parameter Record Settings
- Shared: When selected, a parameter is available to all users with a single shared Parameter Value record created by an admin. This is ideal for shared service accounts or API keys.
- Not Shared: Allows multiple users (admins or panel users) to create their own Parameter Value records under the same Parameter record, enabling users to use individual credentials. During execution, the agent retrieves the value associated with the user who triggered the action.
- Mark As Sensitive: Encrypts all associated Parameter Value records to protect sensitive data such as passwords or API keys. Values are decrypted only during execution. If not selected, values are passed as plain text.
Important: The Shared and Mark As Sensitive settings can only be changed when no Parameter Value records exist under the Parameter record.
Mapping Parameters to Desktop Action Inputs
In the AI Desktop Actions Design workspace, inputs can be configured to use parameters by selecting the Use parameter checkbox. In AI Agent Studio, when adding a desktop action tool with parameter-configured inputs, users must map each input to a corresponding Parameter record.
- All parameter-configured inputs must be mapped before saving the desktop action.
- One Parameter record can map to multiple inputs, but each input maps to only one Parameter record.
- Mapped parameter values override any direct input values specified in agent instructions or the Now Assist panel.
- If a desktop action is updated externally, the existing parameter mapping remains until the tool configuration is reopened and saved again.
- Renaming an input removes its mapping and requires remapping before saving.
Example: SSH Parameters
For SSH connector background task desktop actions, separate Parameter records must be created for each credential component, such as username and password. Only admins can create these Parameter records, while both admins and panel users can create their own Parameter Value records under each. During execution, AI agent instructions reference the Parameter record names to retrieve these values securely.
Note: Parameter record names are case sensitive and must be specified exactly in agent instructions. Instructions should clarify whether credentials are provided directly or retrieved from Parameter records.
Enable AI agents to securely access stored values, such as credentials and other input data, through Desktop Action Parameter records. Parameters protect sensitive values and provide dynamic inputs to desktop actions during agent execution.
Only users with the sn_aia.admin role can create Parameter records. Parameter records store the names of values that an AI agent accesses during desktop action execution. A separate Parameter record is required for each distinct value.
Map parameters to inputs of on-screen task desktop action
In the Design workspace of the AI Desktop Actions application, you can select the Use parameter check box for desktop action inputs that must retrieve values from the parameter records during execution.
In AI Agent Studio, when you add a desktop action tool that contains inputs configured for parameters, the Map parameters section appears in the modal. Each input configured for a
parameter is listed by step name and description, with a Parameter record drop-down.
The following rules apply to parameter mapping:
- All inputs configured for parameters must be mapped to a Parameter record before the desktop action can be saved.
- The same Parameter record can be mapped to multiple inputs.
- Each input can only be mapped to one Parameter record.
If you update a desktop action in AI Desktop Actions client application after mapping its inputs in AI Agent Studio, the agent continues to use the previous mapping until you reopen the tool configuration and save it again.
If you rename an input in the desktop action, the agent treats it as a new input and the existing mapping for that input is removed. You must remap the renamed input before the desktop action can be saved.
SSH parameter example
The following example applies to SSH connector, background task desktop actions. For on-screen task desktop actions, parameter values are supplied through the Map parameters section in AI Agent Studio and aren't referenced in agent instructions.
Only users with the sn_aia.admin role can create Parameter records for SSH desktop actions. To store both a username and a password, the AIA admin must create two separate Parameter records, one for the username (for example,
un_username_group) and one for the password (for example, un_password_group).
Users with the sn_aia.admin or now_assist_panel_user role can then create Parameter Value records under each Parameter record to store the values. Only one Parameter Value record can be created per user for each Parameter record.
AI Agent instructions during execution
The following example shows how an AI agent instruction can reference stored parameter names:
Connect to SSH server and retrieve my session info. Here are my details:- IP address: 172.27.50.123
- Port: 22
- Retrieve the user name stored in "un_username_group" and the password stored in "un_password_group" parameter records.
Verify that you use the exact names of the Parameter records. Parameter record names are case sensitive. For example, "UserName" and "username" are treated as different values.