> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/banquet/banquet-module/masters/faq-on-masters/how-can-i-link-a-function-type-to-a-specific-market-segment.md).

# How can I link a Function Type to a specific Market Segment?

To link a Function Type to a specific Market Segment, you must configure this association within the Master settings. Based on the sources, follow these steps:

1\. Navigate to the Masters menu and click on Function Type.

2\. Click the New button to create a new entry or select an existing one to edit.

3\. Enter the Function Id and Function Name.

4\. In the same window, you will find a field for Market Segment. Select the desired segment from this dropdown to create the link.

5\. Click the Save button to finalize the association.

Important Note: Before you can link them, the Market Segment must already be created in its own Master setting **(Masters > Market Segment)** so that it appears as an option in the Function Type setup.

Once linked, whenever that specific Function Type is selected during a Venue Block or Reservation, the system can automatically associate it with the corresponding Market Segment for your Analysis reports.


---

# 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://help.rbsgo.com/banquet/banquet-module/masters/faq-on-masters/how-can-i-link-a-function-type-to-a-specific-market-segment.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.