> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/getting-started/interacting-with-nodes-in-the-designer-viewer/nodes-toolbox.md).

# Nodes Toolbox

## Default View

The button bar at the top of the logicnet Viewer is called the *Nodes Toolbox.* It arranges node buttons together in logical groupings and displays button options based on the framework type on which you base your project. The Nodes Toolbox contains buttons that all relate to creating steps in your logicnet.

## Framework-specific Toolbox

Depending on the framework selected for your project, there will be some differences in the Nodes Toolbox choices.

* Standard for all frameworks are the first six buttons for testing the logicnet, copy, paste, and delete after selecting a node in the design, and undo/redo, which goes back or forward one step over your editing.
* The list of orange form parts, including radiolist, checklist, has some framework-dependent changes, but mostly stays the same.
  * See the [Form Node Parts](/release-9/platform-documentation/form-node-parts.md) section for detailed explanations and examples of each form part.
* Report parts (not shown) choices appear when you are using the LogicNets Assessment Framework. See [Report-Item Form Part](/release-9/platform-documentation/form-node-parts/report-item-form-part.md) to see what is possible with this most commonly used part.
* The process parts and routing buttons remain standard across all framework choices.
  * The [Process Node Parts](/release-9/platform-documentation/process-node-parts.md) section describes each possible process step, while the routers and call-parts mentioned below are explained in the [Process Nodes](/release-9/platform-documentation/process-nodes.md) section.
* Call-parts is a standard menu, but the choices for it vary substantially, with the LogicNets Starter App Framework having the most options.
* The yellow *form* button is restricted to a couple of frameworks only.
* With most frameworks there are "Special" nodes listed under a final button (not shown here).

## Advanced Configuration

Aside from the default settings by framework listed above, use [Designer Profiles](/release-9/platform-documentation/system-administration/system-settings/designer-profiles.md) to further customize which nodes are displayed in the toolbox. This is useful for specific applications or user roles that only require a subset of functionality.

Customize and place tailored nodes in the toolbox with client-specific preset parameters; for example, a radiolist with *Yes* and *No* options preset. Talk to your LogicNets Project Manager for more information on this and see the [Customized Frameworks](/release-9/design-considerations-and-frameworks/frameworks/general-framework-information/customized-frameworks.md) article.


---

# 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://community-test.logicnets.com/release-9/getting-started/interacting-with-nodes-in-the-designer-viewer/nodes-toolbox.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.