> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/admin-portal/settings/gateway-settings.md).

# Gateway Settings

***

## Overview

Every gateway starts the same way: log in to your tenant as a community administrator, go to **Settings > Gateway Settings**, click **Add new gateway**, give it a name, and choose the channel type. Your new gateway appears on the **Gateway Settings** page once created.

### Email gateway

Send emails through your email provider. Choose **Email** as the channel type, then complete the **Email Provider Settings**:

* **Provider** — select your service provider
* **Protocol** — select the outgoing email protocol
* **Outgoing Mail Server Hostname** — your outgoing mail server hostname
* **From email address** — the sender address your users will see
* **Outgoing Mail Server Port** — your outgoing mail server port
* **Authentication** — select an authentication option
* **Username** — your outgoing email account username
* **Password** — your outgoing email account password

Click **Create**.

### SMS gateway

Send text messages through your SMS provider. Choose **SMS** as the channel type, then complete the **SMS Provider Settings**:

* **Provider** — select your SMS provider
* **Username** — your SMS provider username
* **Password** — your SMS provider password
* **Service URL** — your SMS provider service URL
* **Sender Name** — the name or number shown as the SMS sender

Click **Create**.

{% hint style="info" %}
**Supported SMS providers:** Twilio, Infobip, and Karix.
{% endhint %}

{% hint style="info" %}
**Tip:** The **Sender Name** field accepts alphanumeric values. Using your company name as the sender can help your messages be perceived as genuine by your users.
{% endhint %}

### SMS & Voice gateway

Send text messages and place voice calls through your SMS & Voice provider. Choose **SMS & Voice** as the channel type, then complete the **SMS & Voice Provider Settings**:

* **Provider** — select your provider
* **Username** — your provider username
* **Password** — your provider password
* **Service URL** — your provider service URL
* **Sender Name** — the name or number shown as the sender or caller
* **Timeout Value** — enter a value of 10000 or higher; the request fails once this value is reached

Click **Create**.

{% hint style="info" %}
**Supported SMS & Voice providers:** Twilio.
{% endhint %}

{% hint style="info" %}
**Tip:** The **Sender Name** field accepts alphanumeric values. Using your company name as the sender or caller can help your messages be perceived as genuine by your users.
{% endhint %}

### Delete a gateway

1. Go to **Settings > Gateway Settings**.
2. Find the gateway and click the **trash icon** under **Actions**, to the right of the gateway name.
3. Click **Delete** when prompted.


---

# 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.1kosmos.com/authentication/admin-portal/settings/gateway-settings.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.