> 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/beginner-courses/lessons/gedi-profiles.md).

# GEDI Profiles

Update the 'GEDI Profile' with connection settings

## Introduction

A 'GEDI Profile' is the key to which processes you want to activate in the Standard App, and what exact GEDI configurations will be used. the 'GEDI Profile' is also what connect Business Central with the Golden EDI Cloud Integration Platform (CIP).&#x20;

## Extras

{% hint style="info" %}
More information on this subject can be found in our [<mark style="color:blue;">'Core Concepts</mark>](/standard-app-core-concepts/concepts/gedi-profiles.md)<mark style="color:blue;">'/'GEDI Profiles'</mark><mark style="color:red;">.</mark>&#x20;
{% endhint %}

## Edit GEDI Profiles Settings

### Instructions

In the following step by step guide we will update the profile named 'EDI' that originates from the import of 'Order-To-Cash' 'GEDI-setup' that was illustrated in the previous lesson.  &#x20;

* In Business Central search and go to 'GEDI Profiles' page view.&#x20;

  In 'GEDI Profiles' you are presented with the profiles that are currently setup in Business Central. Depending on what setups you have imported to the system the profiles will vary. There are a lot of columns in this page view but not all are relevant for each 'GEDI setup'.

![Example of GEDI Profiles originating from different 'GEDI setps'](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FpZZ6387yBCj0kVDvl948%2Fimage.png?alt=media\&token=b9dc8937-fa92-4d78-9b16-04bb128cc0fa)

* Add the Connection ID that you have received from Golden EDI into column 'GEDI Connection ID'. Most often the Connection ID consists of an abbreviation of the Business Central company name and the name of the receiving party.&#x20;

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FAtZc2JHsE3kaEsWUVF2t%2Fimage.png?alt=media\&token=dc05a8ce-5eba-438b-a198-a5f1e05523bb)

* Add the connection API Key that you have received from Golden EDI.&#x20;

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F5hbGii8YgrYXhy5MymON%2Fimage.png?alt=media\&token=a0d0c7a4-d241-4cee-bf7b-1427c37ae5ec)

{% hint style="info" %}
[<mark style="color:blue;">Contact the Golden EDI team</mark>](http://goldenedi.com/contact) to receive API Key and other connection settings needed.\
Also you need to provide Golden EDI with Webservice details.&#x20;
{% endhint %}

* Add E-mail addresses in the columns 'E-mail to System Administrator' and 'Email to GEDI Administrator'. These recipients will be notified via e-mail if there are any errors related to Golden EDI. For example; errors related to the Job Queue will be notified to the 'GEDI Administrator'.&#x20;

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FQbag7owW5Gxl7Ju36FVL%2Fimage.png?alt=media\&token=48149cc3-d966-4ec1-9210-9fff10759f71)

Now the profile itself is complete and ready for communicating with the CIP.&#x20;

## Next Step

Next step is to learn how to Import Prepacked Setups.


---

# 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/beginner-courses/lessons/gedi-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.
