> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/customer-data/iys-permissions.md).
# İYS permissions
**İleti Yönetim Sistemi (İYS)** is Türkiye's central consent registry for commercial electronic messages such as SMS and Email.
Netmera can exchange consent data with İYS. The integration mode determines which system is the authoritative source for consent and how consent data moves between Netmera and İYS.
### Choose an integration mode
Choose the mode based on where your organization's consent records are managed.
| | İYS sync mode | İYS integrator mode |
| ------------------------------------- | ------------------------------------------------------- | -------------------------------------------------------------- |
| **Use when** | İYS already contains the authoritative consent records. | Netmera collects and manages consent before sending it to İYS. |
| **Consent source** | İYS | Netmera |
| **Netmera → İYS** | Update consent for existing İYS records | Create and update consent records |
| **İYS → Netmera** | Pull consent from İYS | — |
| **Create new consent records in İYS** | No | Yes |
#### Use İYS sync mode
If your organization already manages consent in İYS and Netmera needs to use those records.
With **İYS sync mode**:
* Netmera can **pull** consent records from İYS.
* Netmera can **update** consent in İYS for existing İYS users.
* Netmera cannot create new consent records in İYS.
**Example:**\
A user has already provided consent and the consent record exists in İYS. Netmera retrieves that consent information and uses it when managing the user's communication permissions.
#### Use İYS integrator mode
If your organization collects consent through Netmera-connected channels such as a website, mobile application, or call center and needs to transfer those consent records to İYS.
With **İYS integrator mode**:
* Netmera can **create** consent records in İYS.
* Netmera can **update** consent records in İYS.
* Netmera acts as the consent-management system for the integration flow.
**Example:**\
A user provides SMS consent through an application. Netmera receives the consent and sends the corresponding record to İYS.
{% hint style="info" %}
Both modes use the same operational screen for bulk changes: [Contact Upload](/netmera-user-guide/targeting/contact-upload.md).
{% endhint %}
### Quickstart
This Quickstart covers the basic integration flow. For mode-specific requirements, see [İYS sync mode](/netmera-user-guide/customer-data/iys-permissions/iys-sync-mode.md) or [İYS integrator mode](/netmera-user-guide/customer-data/iys-permissions/iys-integrator-mode.md).
#### Step 1: Get your İYS credentials
In the İYS portal, find your Brand Code and İYS Code.
#### Step 2: Install and configure the integration
1. In the Netmera Dashboard, select Integrations.
2. Under Data Security, select İleti Yönetim Sistemi.
3. Select Install.
4. Enter your Brand Code and İYS Code.
5. Enable İYS Integrator only when you use Integrator Mode.
#### Step 3: Authorize Netmera in the İYS portal
1. In the İYS portal, open İş Ortaklığı (Partnerships).
2. Select Netmera.
3. Enable the required email, SMS, and call permissions.
4. For Integrator Mode, enable the integrator permission and Mutabakat Yönetimi.
#### Step 4: Validate consent flow with Contact Upload
Open Targeting → Contact Upload. Then select one action:
* Pull Consents from İYS: Refresh Netmera with consent records from İYS.
* Push Consents to İYS: Send consent records from your file to İYS.
{% hint style="warning" %}
If email and SMS have different consent statuses, upload them in separate files.
{% endhint %}
### Choose an integration mode
This choice sets the “source of truth” for consent.
---
# 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://user.netmera.com/netmera-user-guide/customer-data/iys-permissions.md?ask=&goal=
```
`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.