> For the complete documentation index, see [llms.txt](https://docs.in8sync.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.in8sync.com/netsuite-admin-guide/overview-1/default-workflows.md).

# Default Workflows

NetSuite-Admin-managed workflow templates used as the starting point for new Client Admin workflows: created in Dev or Sandbox, copied by Client Admins.

Default Workflows are pre-built workflow templates that NetSuite Admins manage as the starting point for new client deployments. When a Client Admin creates a new workflow for a role, they can start from one of these templates rather than building from scratch.

{% hint style="warning" %}
This section is intended for **Dev and Sandbox environments only**. Test changes to Default Workflows thoroughly before reflecting them in a production account.
{% endhint %}

## How Default Workflows differ from Client Admin Workflows

|                        | Default Workflows (NS Admin)                 | Workflows (Client Admin)             |
| ---------------------- | -------------------------------------------- | ------------------------------------ |
| **Who manages them**   | NetSuite Admin                               | Client Admin                         |
| **Purpose**            | Templates: starting points for new workflows | Live workflows assigned to users     |
| **Published to users** | No: used as a base only                      | Yes: directly control what users see |
| **Environment**        | Dev / Sandbox recommended                    | All environments                     |

Think of Default Workflows as the master copy. When a Client Admin creates a new workflow, they can copy a Default Workflow as their starting point, then customise it for their business without affecting the template.

## Accessing Default Workflows

{% stepper %}
{% step %}

### Open the NetSuite Admin view

Switch to **NetSuite Admin** in <code class="expression">space.vars.productName</code>.
{% endstep %}

{% step %}

### Click Default Workflows

**Default Workflows** is in the left sidebar.
{% endstep %}
{% endstepper %}

The page lists all available default workflow templates, grouped by entity type (Employee, Customer, etc.).

## Reading the Default Workflows list

Each row in the list shows:

| Column        | Description                                                                     |
| ------------- | ------------------------------------------------------------------------------- |
| **Role Name** | The employee or customer role this template is designed for (e.g. Cashier, B2B) |
| **Label**     | The display name of the template                                                |
| **Modules**   | Number of modules configured in this template                                   |
| **Status**    | Published or Draft                                                              |

## Creating a new Default Workflow

{% stepper %}
{% step %}

### Click + New Default Workflow

The button is at the top of the page.
{% endstep %}

{% step %}

### Pick the Entity Type

Select the entity type from the dropdown.
{% endstep %}

{% step %}

### Set the Role Name and Label

Enter the **Role Name** this template is for and a **Display Label**.
{% endstep %}

{% step %}

### Decide Publish status

Enable **Publish** to make the workflow available immediately, or leave it off to start as Draft.
{% endstep %}

{% step %}

### Click Create

Save the template. It's now ready to be used as a starting point.
{% endstep %}
{% endstepper %}

## Editing an existing Default Workflow

1. Click the workflow name to open it
2. Modify modules as needed: add, remove, reorder, or configure

Editing a Default Workflow doesn't affect any live workflows that were previously copied from it. Changes only affect new workflows created from the template going forward.

## Module types available in Default Workflows

The same module types available in the Client Admin Workflow Builder are available here:

| Module Type            | Description                                               |
| ---------------------- | --------------------------------------------------------- |
| **Dashboard**          | Landing screen: must always be in position 1              |
| **Header Navigation**  | Top bar: must always be in position 2                     |
| **Sidebar Navigation** | Left-side nav: must always be in position 3               |
| **Order Form**         | Transaction entry screen (Place Order, Pay Invoice, etc.) |
| **Catalog**            | Product catalog browse and search                         |
| **Page**               | Custom page built in the Page Builder                     |
| **Reports**            | EOD reports, analytics, or queue reports                  |

For full details on each module type, see [Module Types](/client-admin-guide/workflow-builder-overview/module-types.md).

## Publishing vs Draft status

| Status        | Meaning                                                                                                   |
| ------------- | --------------------------------------------------------------------------------------------------------- |
| **Draft**     | Template is a work in progress. Visible in the NS Admin list but not available for Client Admins to copy. |
| **Published** | Template is available as a starting point when Client Admins create new workflows.                        |

To publish: click **Publish** on the workflow row. To revert to draft: click **Set as Draft**.

## Recommended templates to maintain

At minimum, keep a Published Default Workflow for the most common roles your clients use:

* **Cashier:** standard POS employee workflow
* **Store Manager:** management and reporting workflow
* **B2B:** business buyer portal
* **B2C:** individual consumer portal

These cover the majority of deployment patterns. Additional role templates (Sales Rep, Purchasing, Vendor, etc.) can be added as your standard offering expands.

## Related Pages

<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>Cashier Workflow</strong></td><td>What the Cashier template should include.</td><td><a href="/client-admin-guide/workflow-builder-overview/workflow-examples/cashier-workflow.md">Cashier Workflow</a></td></tr><tr><td><strong>B2B &#x26; B2C Workflows</strong></td><td>Customer workflow templates.</td><td><a href="/client-admin-guide/workflow-builder-overview/workflow-examples/b2b-b2c-workflow.md">B2B &amp; B2C Workflows</a></td></tr><tr><td><strong>Module Types</strong></td><td>Available module types reference.</td><td><a href="/client-admin-guide/workflow-builder-overview/module-types.md">Module Types</a></td></tr><tr><td><strong>Creating Custom Workflows</strong></td><td>How Client Admins use these templates.</td><td><a href="/client-admin-guide/workflow-builder-overview/creating-custom-workflows.md">Creating Workflows</a></td></tr></tbody></table>