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

# Company

The company form contains various settings that are global in Bunny.

<figure><img src="/files/SliHnrJWh2FJBhAAM9KG" alt=""><figcaption></figcaption></figure>

### Company name

The information in the top two cards will be used on quotes and invoices that are sent to customers. These values can also be referenced via the company object in workflows, for example `{company.name}` and `{company.phone}`.

### Engineering contact

The engineering contact should be someone in your organization who works with Bunny's APIs. We may use this contact to notify of future deprecation of API endpoints and other technical aspects of Bunny.

### Company actions

A number of useful actions are available from the ... menu on the company form.

#### Restore default workflows

Bunny comes with a set of predefined workflows for sending invoices, dunning etc. This action allows you to restore them to their original configuration in case you somehow messed them up.

#### Create and remove demo data

Demo data consists of a dozen different accounts with subscriptions, invoices etc that you can use to play around with and learn how Bunny works.

#### Reset account

While you are testing your setup, it can be useful to delete all or part of your data. This action allows you to delete subsets of your Bunny data so you can start testing with a clean slate. For example, you can delete all accounts, but still keep the products you have configured.

<figure><img src="/files/O4g6javEVUAi5lcKnK5d" alt="" width="375"><figcaption></figcaption></figure>


---

# 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.bunny.com/guide/tour/settings/company.md?ask=<question>&goal=<endgoal>
```

`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.