# Key Admin Concepts

Six concepts run through every part of the Client Admin. If you understand these, the rest of the docs make sense.

{% hint style="info" %}
Keep this page open in another tab on your first day. The terms here show up everywhere.
{% endhint %}

## How it all connects

```
Users → Roles → Workflows → Modules → Pages (built with Components)
```

Read it left-to-right: a **user** is assigned a **role**. The role is linked to a **workflow**. The workflow is made of **modules**. Each module's page is built from **components**.

## The six concepts

<table data-view="cards"><thead><tr><th>Concept</th><th>One-line definition</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Workflow</strong></td><td>The complete portal experience for a group of users.</td><td><a href="/pages/0CnIlswuI3IVBo6A8Ejk">/pages/0CnIlswuI3IVBo6A8Ejk</a></td></tr><tr><td><strong>Module</strong></td><td>A single page or functional area inside a workflow.</td><td><a href="/pages/g2JG7KMppsgCgHq9QDJ3">/pages/g2JG7KMppsgCgHq9QDJ3</a></td></tr><tr><td><strong>Role</strong></td><td>A named group of users that share a workflow.</td><td><a href="/pages/90JTHrYiNFq2sGVsSqGI">/pages/90JTHrYiNFq2sGVsSqGI</a></td></tr><tr><td><strong>Page Builder</strong></td><td>The drag-and-drop editor where you design module pages.</td><td><a href="/pages/cFWHMzaWYEsdDtvHLkFK">/pages/cFWHMzaWYEsdDtvHLkFK</a></td></tr><tr><td><strong>Component</strong></td><td>A building block on a page (a button, a chart, a product list).</td><td><a href="/pages/cFWHMzaWYEsdDtvHLkFK">/pages/cFWHMzaWYEsdDtvHLkFK</a></td></tr><tr><td><strong>Catalog</strong></td><td>A collection of products available for browsing or ordering.</td><td><a href="/pages/sqKV6Gm0WqBRQeT9aFbs">/pages/sqKV6Gm0WqBRQeT9aFbs</a></td></tr></tbody></table>

## Workflows in a bit more depth

A workflow answers the question: *"When this person logs in, what do they see and what can they do?"*

* A workflow is **assigned to a role** — everyone with that role gets the same portal experience.
* A workflow is built from **modules** (one per page).
* You can clone a default workflow and customize it, or build one from scratch.

**Example:** a *Cashier* workflow might include Dashboard, POS, and EOD Reports modules. A *Store Manager* workflow might include all of those plus User Management and Reports.

![Workflow with modules](/files/sxAwP91CwX2dOOzSHrGr)

## Modules

A module has three things:

* A **name** that appears in the User Portal navigation (e.g. *Dashboard*, *Place Order*).
* A **type** that determines its behaviour (Dashboard, Order Form, Catalog, Reports, and so on).
* A **page** designed in the Page Builder.

The module's type controls which components are available when you design the page — for example, catalog-specific components only appear inside catalog modules.

## Components — the building blocks

When you open the Page Builder you'll see components grouped into categories in the left panel. The categories are:

| Category         | Examples                                                      | What they're for                                 |
| ---------------- | ------------------------------------------------------------- | ------------------------------------------------ |
| **Layout**       | Row, Column, Grid, Flex, Space, Divider                       | Structuring the page                             |
| **Content**      | Heading, Text, Card, Button, Hero, Stats                      | Static information                               |
| **Entity**       | Entity Search, Create Entity, Entity 360, Address, PIN Pad    | Working with people (employees, customers, etc.) |
| **Products**     | Product Field, Product Image, Product Locations, Add to Order | Showing and ordering products                    |
| **Transactions** | Scan Items, Transaction Search, Order Lines                   | Reading and editing transactions                 |
| **Actions**      | Submit Button, Action Button, Action Dropdown, Print          | Triggering actions and navigation                |
| **Widgets**      | BRM Queue, Report, Chart                                      | Data visualization                               |
| **Advanced**     | HTML, JavaScript, CSS, Variables                              | Custom code and dynamic values                   |

<details>

<summary>Less common categories</summary>

* **Catalog Layout** — Catalog Filter, Catalog View Select, Category Sidebar (only inside catalog modules).
* **Reports** — Queue Report, EOD Report, Register Report (specialized reporting blocks).

The components available to you depend on the module type you're editing.

</details>

## Glossary

| Term             | Meaning                                                                                           |
| ---------------- | ------------------------------------------------------------------------------------------------- |
| **Catalog**      | A collection of products or services for browsing and ordering.                                   |
| **Component**    | A page element placed on a module's page in the Page Builder.                                     |
| **Entity type**  | The classification of a user: Employee, Customer, Vendor, or Partner.                             |
| **Module**       | A single page within a workflow.                                                                  |
| **Module type**  | The functional category of a module (Dashboard, Order Form, Catalog, etc.).                       |
| **Page Builder** | The drag-and-drop editor for designing pages.                                                     |
| **PIN override** | A security feature requiring a PIN to authorize certain actions.                                  |
| **Provision**    | Granting a user access to log in to their portal.                                                 |
| **Role**         | A named set of permissions assigned to users.                                                     |
| **Subsidiary**   | A business entity in NetSuite. Most settings, catalogs, and workflows are scoped to a subsidiary. |
| **Workflow**     | The complete portal experience definition for a role.                                             |

## What to do next

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Your First Day</strong></td><td>Apply these concepts in a hands-on walkthrough.</td><td><a href="/pages/e02jN6ZhhYzbynHyiQEB">/pages/e02jN6ZhhYzbynHyiQEB</a></td></tr><tr><td><strong>Portal Overview</strong></td><td>Tour the sidebar and the top bar.</td><td><a href="/pages/AuMEqbZW0YgEz9Mj2NQL">/pages/AuMEqbZW0YgEz9Mj2NQL</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.in8sync.com/client-admin-guide/admin-app-overview/key-admin-concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.