# SCA Configuration - SecContacts.CustomDatasourceNames

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

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`

{% hint style="info" %}
If you use multiple AAD groups or ABS, SMC, or D365 data sources, they will be sequentially numbered by the SCA. These dynamic IDs can also be renamed\
\
For example SCA uses 2 AAD groups you'd have AAD1 and AAD2 as dynamic IDs.
{% endhint %}

\
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`

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

{% hint style="danger" %}
The customid value property must not contain any whitespace characters.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.