> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/enterprise/configuration.md).

# Configuration

The settings for your enterprise installation can be managed at `<hostname>/enterprise/admin`.

**username:** admin\
**password:** the md5 checksum of your license

The commands below can be used to generate the checksum.

```
# mac
md5 kumu-enterprise.kli

# linux
md5sum kumu-enterprise.kli
```

{% hint style="danger" %}
Note that the above credentials are only for logging in to the Enterprise instance settings via `<hostname>/enterprise/admin`. Please see [Creating user accounts](/enterprise/creating-user-accounts.md) for information about creating admin and user accounts for the Enterprise application.
{% endhint %}

## Support

**Add a support email.** This address will be linked to any support links within the application. Set this to the email address you want to send your user's support requests to. Defaults to <enterprise@kumu.io>.

**Add a notifications email.** This address will be used for any notification emails sent by the application. Only used if outbound email is enabled.

## SMTP

In order to enable email notifications, you'll need to add an external SMTP server. No email will be sent if this is disabled. Settings include:

* Server
* Port
* Username
* Domain
* Password
* TLS
* Authentication

## Hostname

By default the app is accessible using the raw instance ip. If you would like to use a custom hostname you'll need to add the following DNS records:

```
A        kumu.example.  <instance ip>
CNAME  *.kumu.example.  kumu.example.
```

Once the DNS records are in place you can update the hostname within the `/enterprise/admin` app.

*Warning: Once the hostname is set the site can only be accessed via the custom hostname.*

## SSH access

[Add an SSH key](/enterprise/ssh-access.md) to enable access to the enterprise command-line utilities.

## SSL

By default, SSL is **not** enabled on self-hosted Kumu Enterprise instances. To add an SSL certificate and allow users to connect through HTTPS, use the `kumu-ssl-install-cert` and `kumu-ssl-install-key` [command line utilities](/enterprise/command-line-utilities.md) to upload a custom certificate and key, then use the `kumu-ssl-enable` command to finish the process.

## Geocoding

The geocoding service used for the [geo template](/guides/templates/geo.md) is not configured by default. To enable geocoding, follow the instructions in the Geocoding section of `<hostname>/enterprise/admin/settings`.

![enterprise configure geocoding](/files/1JfIpl0xDmx3VrV8NAAU)


---

# 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.kumu.io/enterprise/configuration.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.