# Shared, Standardised Settings – ‘Flavours’
## Flavours Overview
In order to encourage the use of standard approaches to running Tickets, Cases and Actions through your business processes, Builder’s configuration approach encourages the re-use of related attributes which are grouped together into areas which define who work goes to, when it is due, what the follow up rules are, as well as some more general settings.
For each of these areas you are encouraged to create a standard menu of options which can be mixed together as standard ‘flavours’, providing flexibility in Service delivery without the need for bespoke support of a large number of ways of doing things.
Underpinning each of these selectable flavours are more detailed settings, but you should not need to manage your configuration at such a detailed level on a day-to-day basis.
After the initial work has been done when you first set up your system to create a standard menu of different allocation options, due date options, general settings and follow up settings, you should not need to access the detailed flavour screens very frequently.
{% hint style="info" %}
Note: the creation of new bespoke Due Date methods and Allocation methods is no longer supported.
{% endhint %}
By far the most frequent interaction you will have with flavours is for Tickets and Actions.
#### **Ticket Flavours**
Add a category row, choose your three flavours from the dropdown lists:
* Who does it go to?
* When is it due?
* Follow up settings
And you’re done.
#### **Case Flavours**
Add an Action row, choose your three flavours from the dropdown lists:
* Who does it go to?
* When is it due?
* General settings
And you’re done.
---
# Agent Instructions: 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:
```
GET https://docs.enate.net/enate-help/builder/builder-2021.1/shared-standardised-settings-flavours.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.