--- title: Add and change features url: /docs/add-and-change-features --- # Add and change features Everything you add to GrowLocal is a feature: a table for quote requests, a form for your website, a type of store. Adding one gives you a starting arrangement, so you don't have to build a table, a page layout or a process from nothing. Choosing it, adding it and changing it later are separate steps. If the words are new, start with [How GrowLocal works](how-growlocal-works.md). ## Choose what to add Edit your sidebar and press **Add**. You'll also see the same picker when you add something inside a feature, such as a form in your website editor, and when you change a feature's type. The picker offers searchable cards and a **See all** option. Selecting a card shows its details. Those details describe what you'd get: its labels and values, plus checks of what it needs and whether it's available to you. They aren't a live, working copy of the finished screen. Open its page in Help for the full account. For example, the [Quote requests page](/docs/features/data/presets/quote-requests-table) lists the columns and status choices before you add anything. It helps to ask three questions of anything you add: - **What does it create or change?** Some make a new table or site. Others set the type of a feature you already have. Others add a page, view, form or record to something that exists. - **What does it need?** It can depend on a connection, an add-on or a permission. The card says if something is missing. - **What does it leave out?** Quote requests creates a table. It doesn't add a website form, import customers or reply to the people who ask. The picker's **Customize** step changes the settings it offers, not what it's made from. Editing the table it creates, or an editable automation, is a separate action. ## Customize before you add If what you picked offers settings, you can set them while adding it. These are the choices it declares, along with any local connections it needs, such as which table something should use. They aren't a way to rewrite the whole arrangement. Quote requests offers one: the table name, which defaults to "Quote requests" and accepts 1–120 characters. The fields and the `new` → `quoted` → `won` or `lost` status choices come with it. You'd change them later with Data's own controls. ## Review, then add When you press **Use**, GrowLocal prepares a review of the proposed change and its effects. Check that it names the result you want. Confirming makes that change, with another check that the prepared change is still valid, and records what it was made from and which version. If what you picked belongs to a feature that's switched off, GrowLocal can turn that feature on first. That's a separate, checked step. If you then cancel the review, the feature stays on. The whole journey isn't one all-or-nothing action. Adding also isn't the same as placing something in your sidebar. What you add with **Add** lands where you pressed it, but the layout only decides where an item appears. Hiding or moving an item doesn't delete or change it. ## Open the result After adding Quote requests, what you use is a Data table, not the card you picked. Add and manage requests there. The new table starts empty: no sample requests are added. Its staff notification, which emails your team about each new request, starts paused until you choose who gets new requests and an approved sender is set up. ## Change it later Each item has one settings dialog, opened from its settings control while you're editing the sidebar. It shows only the sections you may act on: - **Appearance**: name, icon and colour. These are the same for everyone, because there's one name for the item wherever it appears. - **Type**: the current type, or "Not set up", and **Change type** (or **Choose a type**). This appears for features that come in types, and it opens the same picker, with a review of what would change. Your data is kept. - **Settings**: the item's own settings, shown only when its feature declares them, drawn with GrowLocal's standard controls. - **Team access**, and removing it from the business, where you have permission. Store keeps its type in Store's own settings, as **Store type** with **Change**. Changing it keeps your customers, orders and payments, and your saved views and settings. Each record page's layout is replaced by the new type's, and the review lists which ones. Not everything has its own settings. Don't assume a feature has a Settings section until you see one. A single **Save** writes the sections you changed, but each section is saved by its own feature. If one is refused, another may already have been saved. Check the result rather than treating Save as one all-or-nothing step. Changing a table's columns is a Data change, so it follows Data's rules. Changing an editable built-in automation changes the process for what it powers, not the card you picked from. Check its stated scope: one process may serve several tables. [Built-in automations](built-in-automations.md) explains those boundaries. ## What adding does, by kind What you pick does one of three things, and each states its own limits: | What you pick | What adding it does | |---|---| | A type of a feature you have | Sets that feature's type. Changing it later keeps your data. | | A new feature, such as Quote requests | Creates a separate one, such as a table. Each feature controls whether and how many more you can create. | | Something to add to a feature you have, such as a form or a view | Adds it to what exists, as many times as that feature allows. | Quote requests makes something new: a table in the business where you add it. It needs permission to create that table and doesn't need an outside connection. ## What removal does and doesn't promise Nothing here is "installed" or "uninstalled" in the way a phone app is. Adding something changes particular things, and removing is a separate action by whichever feature owns what was made. You can remove an item you're allowed to remove, and you'll get a review of what goes first. That ends the item's use through its own feature. It isn't a promise to reverse every effect of adding it, and it doesn't undo other things that happened along the way, such as turning a feature on. Taking something out of the sidebar only hides it; nothing is deleted, and deleting a folder moves its contents out rather than removing them. Review the stated effects before confirming removal, especially where an item has records or work already in progress. ## Related guides - [How GrowLocal works](how-growlocal-works.md) - [Quote requests](/docs/features/data/presets/quote-requests-table), a concrete example - [Built-in automations](built-in-automations.md) - [Features](/docs/features): everything you can add