> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/business-central/configuration/getting-started/profiles.md).

# Profiles

This will help you setup your profile to allow your instance access to Golden EDI Cloud

### Finding GEDI-Profiles

Search for and open the 'GEDI-Profiles' page

![Finding the profiles page](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LVO7c8MSQ0ieazusCSE%2F-LVbjN3FNc0eVmWHEyXA%2F-LVbkYc1qHOngJ_AO353%2FScreenshot%202019-01-04%20at%2014.31.17.png?alt=media\&token=89a80251-8038-43c8-a1ad-511e4e632b4c)

### Profiles

Here you can see all your active and inactive profiles. You can also set some settings, connect it to our cloud and more. 

![](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LVO7c8MSQ0ieazusCSE%2F-LVbjN3FNc0eVmWHEyXA%2F-LVbn6Gv57qMGxxAFwY7%2FScreenshot%202019-01-04%20at%2014.32.38.png?alt=media\&token=fad49a66-ebce-43ef-9f0d-ba7f671bb4a4)

## New Profile

To add a new profile you create a new line in the list and then set the profile name.

{% hint style="info" %}
When naming the profile it is best to name it to something related to what this specific connection is doing.
{% endhint %}

#### Golden EDI Cloud

You can connect your local profile to an external partner via our Cloud by setting the 'Connection ID' and 'API-Key' fields on the profile. 

{% hint style="info" %}
You can get the connection id and API key by logging in to the Golden EDI portal or by contacting us.
{% endhint %}

#### Notifications

You can enable email notifications to get information when something goes wrong with your connection or when something fails when receiving or sending messages. This is done by entering information in the fields 'E-mail to system administrator' and 'E-mail to GEDI administrator'

![The mail notification fields](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LVO7c8MSQ0ieazusCSE%2F-LVbjN3FNc0eVmWHEyXA%2F-LVbpDbgzmQKwBDPlnP5%2FScreenshot%202019-01-04%20at%2014.33.38.png?alt=media\&token=9d854358-0102-4e80-a72e-b0514ff2cce3)


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.goldenedi.com/business-central/configuration/getting-started/profiles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.