> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/basics/use-the-new-menu-to-create-records-with-context.md). # Use the New menu to create records with context The **New** button is the fastest way to start a record from anywhere in Essential, and it is the main way to create most records. It sits in the top bar, first in the group of buttons on the right, next to your to-do list, notifications, and profile. On a phone it appears as a round **+** button in the same spot. ## What it can create Opening the menu lists **Customer**, **Property**, **Contact**, **Invoice**, **Subscription**, **Quote**, and **Job / Visit**. Customer, Property, Contact, and Job / Visit are always available. Invoice and Subscription appear only if your role can create invoices, and Quote appears only if your role can create quotes. If an option is missing, your role may not have that permission, or the related feature may not be turned on for your business. ## It carries the page you are on into the new record The New button is the same button everywhere, but what it prefills depends on the page you open it from. * **From a customer page**, the customer comes along. A new property, for example, opens with that customer already selected in its **Customer** section, so you do not have to search for the account again. * **From a property page**, that property comes along, and forms that need the customer work it out from the property. * **From a contact page**, that contact comes along where the destination form supports it. * **From a job page**, **Invoice** and **Quote** open already linked to the job, with its property filled in and the job's billable items pulled in, and **Job / Visit** opens a visit attached to that job. Starting from a list page or the Dashboard prefills nothing, which is fine: you pick the customer or property on the form itself. ## The menu only starts the record Opening a form is not the same as saving it. Review whatever was prefilled, fill in the required details, and save or send from the page the menu took you to. Nothing exists until you save. > **Where to find it:** The **New** button in the top bar, to the right of the search box (a round **+** button on a phone) ## Related guides * [First login, navigation, and support](/administration/basics/first-login-navigation-and-support.md) * [Create a customer](/customers-and-work/customers/create-a-customer.md) * [Create a property](/customers-and-work/properties/create-a-property.md) * [Creating a contact](/customers-and-work/contacts/creating-a-contact.md) * [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.md) * [Roles and permissions: how access works](/administration/basics/roles-and-permissions-how-access-works.md) --- # 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://learn.withessential.com/administration/basics/use-the-new-menu-to-create-records-with-context.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.