> 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.sharedmailboxcontacts.md).

# SCA Configuration - SecContacts.SharedMailboxContacts

### SecContacts.SharedMailboxContacts

This setting defines one or more Exchange Online **shared mailboxes** as optional contact sources for SCA. Each mailbox becomes a separate, auto-enumerated data source, visible only to users who are members. Shared mailbox contacts are stored in Exchange Online, allowing a small team to **share and manage contacts collectively**. Users with full or read-only access can use these contacts in Outlook (“People”/“Contacts”) and in SCA

* Name: `SecContacts.SharedMailboxContacts`
* Value:  `[{"name":"<smc_name>", "value":"<smc_emailaddress>"}]`

The Value property is a JSON Array of name value pairs. You can add one or multiple shared mailbox email addresses here.

Replace **\<smc\_name>** with the unique name to identify the shared mailbox

* e.g. `SCM1`

Replace **\<smc\_emailaddress>** with the email address of a shared mailbox.

* e.g. `marketing@provectus-lab.de`

If the SCA user is member of the shared mailbox configured here, then contacts stored in that shared mailbox will become available in SCA.

If the SCA user is NOT member of the shared mailbox configured here, then this setting is ignored by SCA and the user will not see any contacts stored in that shared mailbox.


---

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

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

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.