> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/administration/company-settings.md).

# Company settings

From the Company Info tab, you can update information and preferences for all users in your organization. This includes updating your logo, terms and conditions, non-disclosure agreements, and company preferences.

Access: To access these settings, you will need to be assigned to the Admin role for your organization.

### Access company settings <a href="#accesscompanysettings" id="accesscompanysettings"></a>

You can update your company information from the Administration screen.

1. From the **menu**, select *Administration*.
2. Select the **Company settings** tab.

### Preferences <a href="#preferences" id="preferences"></a>

The Edit company preferences window allows you to update configurations for all users in your organization. [For more information, see Edit company preferences.](https://docs.fairmarkit.com/buyers/administration/company-settings/edit-company-preferences.md)

* Click **Preferences**.\
  The Edit company preferences window displays.

### Logo <a href="#logo" id="logo"></a>

Displays your current logo. To update your company logo, complete the following:

1. Click **Update logo**.\
   A file selection window displays.
2. Select your logo file. You logo file must be an image file (jpg, png, or jpeg) limited to a height of 80px.
3. Click **Open**.

### RFQ Terms and Conditions <a href="#rfqtermsandconditions" id="rfqtermsandconditions"></a>

Displays the terms and conditions for request for quote events. Last updated information, including the user name and date, displays below the text.

#### Edit terms and conditions

1. Click **Edit**.
2. Edit the text. You can enter up to 50,000 characters and use standard HTML to format and create links in your text.
3. Click **Save**.

### RFP Terms and Conditions <a href="#rfptermsandconditions" id="rfptermsandconditions"></a>

Displays the terms and conditions for request for proposal events. Last updated information, including the user name and date, displays below the text.

#### Edit terms and conditions

1. Click **Edit**.
2. Edit the text. You can enter up to 50,000 characters and use standard HTML to format and create links in your text.
3. Click **Save**.

### Non-disclosure agreement (NDA) <a href="#nondisclosureagreementnda" id="nondisclosureagreementnda"></a>

Displays the non-disclosure agreement text for request for proposal events. Last updated information, including the user name and date, displays below the text.

#### Edit non-disclosure agreement

1. Click **Edit**.
2. Edit the text. You can enter up to 50,000 characters and use standard HTML to format and create links in your text.
3. Click **Save**.


---

# 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.fairmarkit.com/buyers/administration/company-settings.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.
