> For the complete documentation index, see [llms.txt](https://docs.3q.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3q.video/user-guide-new-ui/personal-area/contract-data.md). # Contract Data
The **Contract Data** area allows account administrators to manage company, billing, and contact information for the account. {% hint style="info" %} This area is restriced to Users with the Adminsitrator role. {% endhint %} This section contains the legal and commercial information associated with the customer account. It can also be used to define important contact persons for different responsibilities, such as general users, accounting contacts, technical contacts, or external partners. From the Contract Data area, users can: * View and edit contract-related account information * Maintain company and address details * Add VAT and commercial register information * Define an email address for invoice delivery * Add important contact persons * Assign contact person roles * Store contact details such as email, phone number, and country The Contract Data area is available from the account-related settings, depending on user permissions. ### Accessing Contract Data The **Contract Data** section is available through the user avatar in the top-right corner of the platform. To open Contract Data: 1. Click your avatar in the top-right corner. 2. Open the account or contract-related menu. 3. Select **Contract Data**. The Contract Data panel opens and provides access to the **Contract Data** and **Contact Persons** tabs. *** ### Contract Data Overview The Contract Data panel contains two tabs: * **Contract Data** * **Contact Persons** The **Contract Data** tab contains company, billing, and legal information. The **Contact Persons** tab contains people who are relevant for communication, billing, support, technical operations, or external coordination. *** ### Contract Data The **Contract Data** tab contains the main account information used for contractual and billing-related purposes. Available fields may include: * Title * Legal Representative * Legal Structure * Address * VAT Identification Number * Commercial Register * Email for Invoice Delivery * Telephone Number The available fields may depend on account configuration and permissions. *** ### Title The **Title** field contains the account or company name. This name is used to identify the contract account within the platform. *** ### Legal Representative The **Legal Representative** field can be used to enter the person or entity legally representing the company. This field may be required depending on the account configuration or contractual setup. *** ### Legal Structure The **Legal Structure** field can be used to enter the company’s legal form. Examples include: * GmbH * AG * UG * Ltd. * Inc. * Association * Public institution Use the legal structure that matches the official company registration. *** ### Address The **Address** section contains the company’s postal address. It may include: * Street and house number * Additional address information * Postal code * City * Country Keep this information up to date, especially when it is used for billing, contract communication, or invoice delivery. *** ### VAT Identification Number The **VAT Identification Number** field can be used to store the company’s VAT ID. This is relevant for billing and tax-related documentation. If no VAT ID is available or required, the field may remain empty or contain a placeholder depending on the account setup. *** ### Commercial Register The **Commercial Register** field can be used to store registration information for the company. This may include the register court, register number, or equivalent commercial registration details. *** ### Email for Invoice Delivery The **Email for Invoice Delivery** field defines the email address used for invoice communication. Use a shared or monitored billing email address whenever possible, for example: * * * This helps ensure that invoices and billing-related messages reach the responsible team. *** ### Telephone Number The **Telephone Number** field can be used to store a general company or billing contact number. Depending on the interface, the country code can be selected separately from the phone number. *** ### Contact Persons The **Contact Persons** tab allows users to add important contacts for the account. If no contact person has been added yet, the page shows an empty state and offers the option to add a contact person. Contact persons can help 3Q or internal users identify who is responsible for specific topics. *** ### Adding a Contact Person To add a contact person: 1. Open **Contract Data**. 2. Select the **Contact Persons** tab. 3. Click **Add Contact Person**. 4. Select a **Role**. 5. Enter the required contact details. 6. Save the contact person. After saving, the contact person appears in the Contact Persons list. *** ### Contact Person Roles When adding a contact person, a role must be selected. Available roles may include: * **User** * **Accounting** * **Technician** * **External Partner** The role describes the person’s responsibility or relationship to the account. #### User Use the **User** role for general account users or contacts who should be associated with the account but do not have a specialized billing or technical role. #### Accounting Use the **Accounting** role for people responsible for billing, invoices, payments, or commercial communication. #### Technician Use the **Technician** role for technical contacts who may be responsible for integrations, livestream operations, platform configuration, or troubleshooting. #### External Partner Use the **External Partner** role for contacts from agencies, service providers, production partners, or other external organizations involved in the account workflow. *** ### Contact Person Details Depending on the selected role and account configuration, the following fields may be available: * First name * Last name * Email address * Telephone number * Country Required fields are marked with an asterisk. #### First Name and Last Name Enter the contact person’s first and last name. These fields help identify the person in internal and external communication. #### Email Address Enter the email address of the contact person. This field is required and should contain a valid, monitored email address. #### Telephone Number The telephone number can be added for direct contact. Depending on the interface, the country code can be selected separately. #### Country The country field can be used to define the contact person’s country or location. *** ### Managing Contact Persons Existing contact persons can be reviewed and updated in the **Contact Persons** tab. Depending on user permissions, contact persons can be added, edited, or removed. Keep contact persons up to date so that billing, support, technical, and partner communication can be routed correctly. *** ### Typical Use Cases Contract Data can be used for different account administration workflows, for example: * Maintaining billing and invoice information * Updating company address details * Adding a legal representative * Storing VAT and commercial register information * Defining an invoice delivery email address * Adding accounting contacts * Adding technical contacts for support or integration topics * Adding external partner contacts for project coordination *** ### Notes Access to Contract Data may be limited to account administrators or users with the required permissions. Changes to contract, billing, or invoice-related information may affect account communication and commercial processes. Make sure that company information, invoice email addresses, and contact persons are kept up to date. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.3q.video/user-guide-new-ui/personal-area/contract-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.