> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-general-de-yoplanning/parametrage-de-team.md). # Team settings To create a guide on setting up a team in the Yoplanning.pro application, we will detail each of the available fields in this section, following the structure and example provided. This guide aims to help users understand and correctly fill out each field when setting up their team in Yoplanning.pro. #### GENERAL **LOCATION** * **Country**: Select the country where your organization is located. Example: France. * **Location**: Detail the precise location of your organization via Google map location * **Add a location**: Allows you to add addresses (Location) if you do not yet have this address in the location list #### CONTACT * **Email Address**: The primary contact email address for your organization. This is the address that will be public and used by your customers. * **Phone Number**: The main phone number to contact your organization. Remember to include the country code for international calls. #### OWNER * **Full Name**: The name of the owner or primary manager of the organization. * **Email Address**: The email address of the owner or manager. * **Google My Business Profile ID**: [click here to see the tutorial](/en/yoplanning-academy/yoplanning-parametrage/parametrage-general-de-yoplanning/parametrage-de-team/comment-trouver-votre-identifiant-google-business-profile.md) And this information is particularly necessary for documents concerning the GDPR. (in Europe) #### SALES * **Currency**: The primary currency used for transactions. Example: EUR. * **Link to your Terms and Conditions of Sale**: URL to your terms and conditions document. Example: . {% hint style="info" %} The GTM identifier is no longer present in the team configuration; it has been moved to the booking module configuration. {% endhint %} #### BILLING * **Auto-finalization threshold**: Number of days after which an invoice is automatically finalized. Example: 7 days. * **Invoice - Footer**: Text or information to include at the bottom of each invoice, such as the general billing conditions. #### RESALE * **Account Account**: If specified, this account will be used for resale transactions. If blank, the vendor's product account will be used. * **Taxes**: If enabled, the vendor's product taxes will be applied. #### EMAILS * **Email - Footer**: Information or text to include at the bottom of each email sent. * **Facebook URL**: Link to your Facebook page. Example: . * **Instagram URL**: Link to your Instagram profile. #### PAYMENT LINK * **Send automatic reminder after**: Number of days after which a payment reminder is automatically sent. Example: 3 days. #### BANK DETAILS * **IBAN**: Your bank's international account number. * **BIC**: Your bank's identification code. This guide provides an overview of how to fill out the necessary fields for team setup in Yoplanning.pro. Make sure you provide accurate and complete information for each field to ensure effective management of your organization within the software. --- # 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.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-general-de-yoplanning/parametrage-de-team.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.