> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/the-portal-explained/things-manager/connectivity/esim-connectivity-configuration.md).
# eSIM connectivity configuration
The eSIM Connectivity configuration page gives you the opportunity to manage the **profiles** on your eSIMs. You can **download** new profiles, **enable** or **disable** a profile, **remove** existing profiles, and follow all **operations** that are performed on the eSIM.
An **eSIM** (embedded SIM) can hold **multiple** profiles, of which only **one** can be enabled at a time. Profiles are managed remotely with **RSP** (Remote SIM Provisioning), based on the **SGP.32 (IoT-RSP)** standard.
{% hint style="info" %}
An eSIM can be a soldered chip inside a device, or a SIM card that contains an eSIM module. The device must support eSIM for this to work.
{% endhint %}
#### The eSIM overview
In the eSIM **overview**, you see all your eSIMs with their enabled profile and the result of the last operation.
Below is a brief description of the **columns** displayed:
{% hint style="info" %}
Use the **columns selector** to show or hide columns and change their order. You can find a detailed explanation in [Connectivity](/kpn-things/the-portal-explained/things-manager/connectivity.md).
{% endhint %}
1. **EID** This is the unique identifier of the eSIM itself, not of the profiles on it
2. **Profiles** This shows the number of profiles that are currently on the eSIM
3. **Enabled Profile (ICCID)** This is the ICCID of the profile that is currently enabled. Clicking the ICCID brings you to the connectivity details of that profile
4. **Profile** This is the name of the profile that is currently enabled
5. **Last operation** This shows the result of the most recent operation performed on the eSIM, for example **Successful (enable profile)** or **Failed (download profile by activation code)**
6. **RSP type** This shows the RSP standard and version that is used to manage the eSIM, for example SGP.32 (IoT-RSP) (v1.2)
7. **Operator** This is the operator of the enabled profile
8. **Profile type** This shows the type of the enabled profile, for example K153 or K155
#### Search by EID
Use the search field to look up the **EID** (eUICC Identifier) number of the eSIM. If you enter **part** of the number, you'll get a list of all EIDs containing **those** digits.
#### eSIM details
In the Things Portal, we can show you all eSIM **details** for an EID, such as the profiles on the eSIM, the technical properties, and the operation history.
1. Click **anywhere** on the line or the icon at the **end** of the row
In the **eSIM detail** overview, you will find all the **information** and can perform **actions**:
1. [Device Summary](#device-summary) Summary of the device linked to the enabled profile (optional)
2. [eSIM Summary](#esim-summary) Summary of the eID, the enabled profile and the last operation
3. [Profiles on this eSIM](#profiles-on-this-esim) View and manage the profiles on the eSIM (enable and remove)
4. [Add profiles to this eSIM](#add-profiles-to-this-esim) Download a new profile with an activation code
5. [Base Properties](#base-properties) View the technical properties of the eSIM
6. [Operations](#operations) Follow all operations performed on the eSIM
{% hint style="info" %}
After you perform an action, the new command is only received and executed once the device reconnects to the eSIM Manager server. This can take a while, sometimes a few hours, depending on the configured reconnection interval. While an action is pending, a blue bar is shown indicating that no new action can be performed.
{% endhint %}
#### Device Summary
In the eSIM **details** overview, you can also see the device **linked** to the ICCID of the **enabled** profile. When you click on the device properties, you are automatically redirected to **Device Details**. A more detailed explanation of how this works can be found in [IoT Devices](/kpn-things/the-portal-explained/things-manager/iot-devices.md).
{% hint style="info" %}
A device can only be linked to a **KPN** profile. When the enabled profile is a KPN profile, you still need to enter the device information **manually** in the portal. When a **non-KPN** profile is enabled, the data is handled **outside** the Things Portal and no device information can be shown.
{% endhint %}
**1. Link Device**
When no device is linked to the ICCID of the enabled connectivity, you can select a **device** here.
{% hint style="info" %}
This option is only **available** if no device is currently linked and the enabled profile is a **KPN** profile.
{% endhint %}
**2. Device properties**
When a device is **linked**, the device properties are shown here. Below is a brief description of the **fields** displayed:
1. **Label** This is the name of the device
2. **Barcode** This is the unique identifier of the device, such as a barcode or serial number
3. **Device type** This defines the type of device and determines which decoder is applied
4. **Processing** This shows whether the data is processed and delivered to an endpoint
5. **Flows** This shows which data flow the device is linked to
#### eSIM Summary
In the **eSIM Summary** overview, you see the current state of the eSIM.
Below is a brief description of the **fields** displayed:
1. **eID** This is the unique identifier of the eSIM
2. **Enabled profile** This is the name of the profile that is currently enabled
3. **Last operation** This shows the result of the most recent operation performed on the eSIM
4. **M2M** This is the ICCID of the enabled profile. Clicking the ICCID brings you to the [M2M connectivity details](/kpn-things/the-portal-explained/things-manager/connectivity/m2m-connectivity-configuration.md), where you can manage the connectivity settings of the profile
#### Profiles on this eSIM
This section shows all **profiles** that are currently downloaded to the eSIM. Only **one** profile can be enabled at a time. When you enable a different profile, the currently enabled profile is automatically **disabled**.
**1. ICCID**
This is the unique identifier of the **profile**. Clicking the ICCID brings you to the **M2M connectivity details** of that profile.
**2. Profile**
This is the **name** of the profile. A **Preloaded** tag indicates that the profile was already installed on the eSIM during **production**, instead of being downloaded later.
**3. Profile state**
This shows the **current** state of the profile. Below is an **overview** of the available states and their meaning.
| State | Description |
| -------- | ---------------------------------------------------------------------------------- |
| Enabled | the profile is active and used for connectivity; only one profile can be enabled |
| Disabled | the profile is installed on the eSIM but not in use; it can be enabled at any time |
**4. Operator**
This is the **operator** that owns the profile.
**5. Project**
This is the **project** in the Things Portal where the connectivity of the profile is managed. For a **non-KPN** profile, no project is shown, because the connectivity is managed outside the Things Portal.
**6. Remove profile**
The  icon **removes** the profile from the eSIM.
{% hint style="warning" %}
Removing a profile **deletes** it from the eSIM. To use the profile again, it must be downloaded **again** with an activation code.
{% endhint %}
**7. Enable**
This button **enables** the profile. The connectivity will switch to this profile and the currently enabled profile will be **disabled**.
**8. Sync with eSIM**
The profile information shown is based on the **last known** state in the Things Portal. Use the **Sync with eSIM** button to retrieve the **current** state of the profiles directly from the eSIM. The result of the sync appears in the [Operations](#operations) table.
{% hint style="info" %}
When you sync, the current state is retrieved from the eSIM. This can take a while, and you cannot start new actions until it completes.
{% endhint %}
#### **Add profiles to this eSIM**
This is section **4** from the eSIM details overview. In this section, you can download a **new** profile to the eSIM with an **activation code**. You receive the activation code from the **operator** that provides the profile.
**1. Activation Code**
Enter the **activation code** of the profile you want to download to the eSIM.
**2. Enable after download**
When this option is switched **on**, the profile is automatically **enabled** after the download has completed. The currently enabled profile will then be **disabled**. When this option is switched **off**, the profile is downloaded in the **Disabled** state and can be enabled later.
{% hint style="info" %}
This operation is performed automatically in two steps, so the profile may be downloaded for a brief moment before it becomes active.
{% endhint %}
**3. Download this profile to one eSIM**
This button starts the **download** of the profile to the eSIM. You can follow the progress and the result of the download in the [Operations](#operations) table.
#### Base Properties
Base Properties shows the **technical** properties of the eSIM. These properties are fixed and cannot be **changed**.
**1. Linked eIM**
This is the **eSIM IoT Remote Manager** (eIM) that manages this eSIM. The eIM is the system that sends the profile management commands to the eSIM.
**2. RSP type**
This shows the **RSP** (Remote SIM Provisioning) standard that is used to manage the eSIM, for example **SGP.32 (IoT-RSP)**, the GSMA standard for IoT devices.
**3. RSP version**
This shows the **version** of the RSP standard that the eSIM supports.
#### Operations
The Operations table shows the **history** of all operations performed on the eSIM, such as downloading, enabling and removing profiles. Use the **search** field to filter the operations.
Below is a brief description of the **columns** displayed:
**1. Last state change**
This is the **date and time** the operation last changed state. Operations are not always completed immediately, because the eSIM must be **reachable** to process a command.
**2. Operation**
This is the **type** of operation. Below is an **overview** of the operations and their meaning.
| Operation | Description |
| ----------------------------------- | ---------------------------------------------------------------------------- |
| Download profile by activation code | a new profile is downloaded to the eSIM with an activation code |
| Enable profile | a profile on the eSIM is enabled; the previously enabled profile is disabled |
| Remove profile | a profile is removed from the eSIM |
| Sync with eSIM | the current state of the profiles is retrieved directly from the eSIM |
**3. Operation state**
This shows whether the operation was completed **Successful** or has **Failed**.
**4. Profile**
This is the **profile type** the operation was performed on.
**5. ICCID**
This is the **ICCID** of the profile the operation was performed on. Clicking the ICCID brings you to the **M2M connectivity details** of that profile. For operations that are not related to a specific profile, such as **Sync with eSIM**, no ICCID is shown.
**6. Operator**
This is the **operator** for which the operation was performed.
{% hint style="info" %}
For a **new** eSIM on which no operations have been performed yet, the Operations table will show **No operations found**.
{% 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 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.kpnthings.com/kpn-things/the-portal-explained/things-manager/connectivity/esim-connectivity-configuration.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.