> For the complete documentation index, see [llms.txt](https://docs.eventflowapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventflowapp.com/eventflow-cms/general-settings/terms-and-variables.md). # Terms and Variables The Terms and Variables page allows you to set key app settings and custom terminology. This is particularly useful if your staff and exhibitors are used to referring to something in a different way to the standard terminology in Eventflow. For example, if your exhibitors are used to tasks being referred to as deadlines then you can simply override the term tasks so it shows throughout Eventflow as deadlines. ### Team member limit From this page you can also increase your team member limit which controls the maximum number of team members your exhibitors can invite to their teams. ### Due Soon Days Due soon days allows you to override the default number of days before a task due date is considered 'due soon'. This affects the colour coding of the tasks table and dashboard, as well as when task reminder emails can be triggered. If you are trying to send a task reminder/chaser email, but the 'Chase teams' button on the tasks table is greyed out, this is because the task isn't yet 'due'. To unlock this functionality simply increase this number to 45 or 60 days. ### Currency You can also set the curreny used across Eventflow. This is important when you are using pricing fields in your custom Eventflow forms. After making changes, make sure to click "Save" to apply, or "Cancel" to discard your changes. --- # 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.eventflowapp.com/eventflow-cms/general-settings/terms-and-variables.md?ask=&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.