---
title: "Credentials: Edit Credentials"
slug: "edit-record-window"
updated: 2025-08-01T10:34:54Z
published: 2025-08-01T10:34:54Z
canonical: "docs.mapp.com/edit-record-window"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Credentials: Edit Credentials

### Overview

The **Edit Credentials** view allows users to update existing credential records for secure integrations with third-party systems. While the core record type and record name remain fixed, sensitive fields like usernames, passwords, and access endpoints can be updated without breaking placeholder logic. Mapp Engage always fetches the current credential values at runtime, so updates do not require manual adjustments to existing configurations.

### Navigation Path

1. *Main Navigation > User Management > Permissions > Credentials*
2. In the **Actions** column, click the **Edit** (pencil) icon

---

### General Behavior

- You can modify fields such as usernames, passwords, file paths, and endpoints.
- The **record name** cannot be edited. It defines the generated placeholder and must remain unchanged.
- Once updated, the encrypted values are applied automatically wherever the record is used.
- Placeholders in transfer functions (e.g., FTP paths) do **not** need to be manually updated after editing.

---

### Credential Placeholders

After a record is saved, Mapp Engage generates **non-editable placeholders** for each encrypted input. These placeholders follow a consistent naming pattern and are based on the value entered in the **Name** field of the credential.

> [!NOTE]
> The placeholder logic supports secure and dynamic replacement of sensitive information during executions such as imports, exports, and message triggers.

### Placeholder Naming Pattern

| **Credential Type** | **Field** | **Placeholder Pattern** | **Example** |
| --- | --- | --- | --- |
| **User Name** | User Name | `${encryption.user-<record-name>.name}` | `${encryption.test.name}` |
| **User Password** | Password | `${encryption.password-<record-name>.password}` | `${encryption.test.password}` |
| **User Account** | User Name | `${encryption.account-<record-name>.name}` | `${encryption.test.name}` |
| Password | `${encryption.account-<record-name>.password}` | `${encryption.test.password}` |
| **CMS Account** | URL | `${encryption.cms-account-<record-name>.cmsAccountURL}` | `${encryption.test.cmsAccountURL}` |
| User Name | `${encryption.cms-account-<record-name>.cmsAccountUser}` | `${encryption.test.cmsAccountUser}` |
| Password | `${encryption.cms-account-<record-name>.cmsAccountPassword}` | `${encryption.test.cmsAccountPassword}` |

> [!NOTE]
> Placeholders are read-only and cannot be manually modified in the interface.

---

## Actions Table

| **Action** | **Description** |
| --- | --- |
| **Save** | Saves all changes to the credential. Placeholders remain consistent. |
| **Cancel** | Discards changes and exits the editing mode. |

---

### Additional Information

- Changing sensitive values (like passwords or API keys) **does not require updating placeholders** in other functions.
- Always choose meaningful and unique names during credential creation, as those names define the permanent placeholder identifiers.

## Related

- [Credential Types in Mapp Engage](/credentials-options.md)