--- title: Vault crypto module manager AI agent description: This ServiceNow Vault agent manages the Vault crypto module configuration and access policies. The agent handles encrypted field configurations for fields, and manages module access policies for roles. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/intelligent-experiences/vault-vault-crypto-module-manager-ai-agent.html release: australia topic_type: reference last_updated: "2026-08-14" reading_time_minutes: 2 breadcrumb: [ServiceNow Vault AI agents, ServiceNow Vault AI agents, AI agents library, AI assets, Enable AI experiences] --- # Vault crypto module manager AI agent This ServiceNow Vault agent manages the Vault crypto module configuration and access policies. The agent handles encrypted field configurations for fields, and manages module access policies for roles. ## Workflow 1. Check that the required roles \(KMF admin/cryptographic manager and security\_admin\) are available \(required\) and whether Field Encryption Enterprise is installed \(recommended\). 2. Present the four supported operations and let the user choose one: - **Encrypt a field** Collect the table and field name, validate both exist, check whether the field is already encrypted, and if not, encrypt it with the vault crypto module. - **Grant role access** Collect a role name, check if it already has access, and if not, create a module access policy for that role. - **Check encryption status** Collect a table and field name, validate both exist, and report whether the field is currently encrypted. - **List roles with access** 3. Display the outcome \(success, failure, or current status\) and end execution.
| Field | Description |
|---|---|
| Allow third party to access this AI agent | When enabled, third-party AI agents can use this agent. This value is off \(false\) by default. This setting is defined in the AI Agent configs \[sn\_aia\_agent\_config\] table on the External discoverable field. |
| Allow AI specialists to access this AI agent | When enabled, AI specialists can use this agent. This value is off \(false\) by default. When set to true, more configuration options for tools become available so that an AI specialist can map inputs and response templates to tool outputs. This setting is defined in the AI Agent configs \[sn\_aia\_agent\_config\] table on the Specialist enabled field. |
| Manage long-term memory | When enabled, all previous user interactions are used as context for the LLM. This value is off \(false\) by default. This setting is defined by the **sn\_aia.ltm.enable\_long\_term\_memory** system property. For more information, see [ServiceNow Otto AI agents reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/intelligent-experiences/na-aia-reference.md). |
| Tools | - **Scripts** Check if field is encrypted Check prerequisites Check table and field available Create module access policy for role Encrypt field with vault crypto module Get all roles with vault crypto module access |
| Allowed user roles The specific user roles that can access this AI agent. | snc\_internal |
| Data access roles The specific user identity roles that determine which data the AI agent can access and what actions it can take. | sn\_vault\_console.vault\_console\_admin, security\_admin, sn\_kmf.admin, sn\_kmf.cryptographic\_manager |
| Triggers | Optional. None defined by default. An admin can specify triggers if desired. For more information, see [Add a trigger to an AI agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/intelligent-experiences/add-trigger-aia.md). |
| Channels | Configure an assistant for Virtual Agent or ServiceNow Otto panel using [Assistant Designer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/configure-now-assist-va.md). |
| Used in agentic workflows | Field Encryption with Vault module |