> For the complete documentation index, see [llms.txt](https://docs.secure-contacts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.customdatasourcenames.md).

# SCA Configuration - SecContacts.CustomDatasourceNames

### **SecContacts.CustomDatasourceNames** <a href="#seccontacts.customdatasourcenames" id="seccontacts.customdatasourcenames"></a>

This setting allows administrators to customize the IDs and display names of datasources shown in SCA. This is useful when datasource names should match internal terminology or when multiple instances of the same datasource type are configured.

Secure Contacts App has a default `id` and `name` for any datasource which is available in the App. e.g. `AAD - AzureActiveDirectory`

* default datasource id's currently available: `AAD, APC, GAL, D365, DVRS, ABS, SMC`

\
With this setting you can change `id` and `name` of any datasource which is presented to the user.

* Name: `SecContacts.CustomDatasourceNames`
* Value: `[{"defaultid":"<default id>", "customid":"<custom id>", "customname":"<custom name>"}]`

The Value property is a JSON Array of `defaultid` `customid` `customname` trio.\
You can add one or multiple custom datasource names here.

Replace **\<default id>** with the default datasource id you want to change

* e.g. `AAD`

Replace **\<custom id>** with your custom datasource id

* e.g. `CORP`

Replace **\<custom name>** with your custom datasource name

* e.g. `Corporate Directory`

### **Configuration fields**

<table><thead><tr><th width="139.00006103515625">Field</th><th width="76.99993896484375">Type</th><th width="91.66656494140625">Required</th><th>Description</th></tr></thead><tbody><tr><td><code>defaultid</code></td><td>string</td><td>Yes</td><td>The original datasource ID assigned by SCA.</td></tr><tr><td><code>customid</code></td><td>string</td><td>Yes</td><td>Custom datasource ID used internally by SCA. Must not contain whitespace characters.</td></tr><tr><td><code>customname</code></td><td>string</td><td>Yes</td><td>Display name shown to users in the SCA interface.</td></tr></tbody></table>

### Examples

**Rename a single datasource**

```json
[
  {
    "defaultid": "AAD",
    "customid": "CORP",
    "customname": "Corporate Directory"
  }
]
```

Result:\
AAD → CORP
\
AzureActiveDirectory → Corporate Directory

**Rename multiple datasources**

```json
[
  {
    "defaultid": "AAD",
    "customid": "CORP",
    "customname": "Corporate Directory"
  },
  {
    "defaultid": "SMC",
    "customid": "MKT",
    "customname": "Marketing Contacts"
  },
  {
    "defaultid": "ABS",
    "customid": "SUP",
    "customname": "Support Directory"
  }
]
```

Result:\
AAD → CORP
\
AzureActiveDirectory → Corporate Directory

SMC → MKT\
SharedMailboxContacts → Marketing Contacts

ABS → SUP\
AzureBlobStorage → Support Directory

**Rename multiple datasources of the same type**

When multiple datasources of the same type are configured, SCA automatically assigns sequential IDs. Example:  AAD1, AAD2 or ABS1, ABS2 etc.&#x20;

These dynamically assigned IDs can also be customized using this setting.

```json
[
  {
    "defaultid": "AAD1",
    "customid": "SALE",
    "customname": "Sales Contacts"
  },
  {
    "defaultid": "AAD2",
    "customid": "MKT",
    "customname": "Marketing Contacts"
  }
]
```

Result:\
AAD1 → CORP
\
AzureActiveDirectory1 → Sales Directory

AAD2 → MKT\
AzureActiveDirectory2 → Marketing Contacts

{% hint style="danger" %}
A resync as discribed [here](/archiv/app-manual/contacts-sync.md) is mandatory after you have applied changes to SecContacts.CustomDatasourceNames.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.customdatasourcenames.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.