> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Modules Settings

> Use Modules settings to choose which major workflow areas appear in the sidebar for the organization without changing user permissions.

<Note>
  Modules control navigation visibility. They are not security controls. Roles and
  permissions still decide what a user can view, create, edit, approve, or delete.
</Note>

## Open Modules Settings

1. Open **Settings**.
2. Choose **Entity Settings**.
3. Open the **System** group.
4. Choose **Modules**.

<Frame caption={"Modules settings hide or show major sidebar areas for the organization."}>
  <img src="https://mintcdn.com/arcuserp/ATYxy7SB_HGOBGqh/images/support/screenshots/settings/system-modules.png?fit=max&auto=format&n=ATYxy7SB_HGOBGqh&q=85&s=b0d2509f6a8a367790a038a4c81b49ff" alt="Modules settings page with enabled module checkboxes for Orders, Inventory, Fulfillment, Accounting, Shipping, and Returns" width="1920" height="1100" data-path="images/support/screenshots/settings/system-modules.png" />
</Frame>

## What Modules Change

Modules make the sidebar cleaner by hiding workflow areas the organization does not use.

The module list controls:

* **Orders**: sales orders, invoices, and order management.
* **Inventory**: stock tracking, warehouse bins, serial numbers, and stock tools.
* **Fulfillment**: packing, shipping labels, and fulfillment queues.
* **Accounting**: GL, AP, AR, journal entries, and reports.
* **Shipping**: rate shopping, label purchase, shipments, and tracking.
* **Returns**: customer RMAs and vendor returns.

Core areas such as Dashboard, Accounts, Products, Purchasing, Support, Organization, and Settings can still appear outside this module list.

If no explicit module preference has been saved yet, Arcus treats all optional modules
as enabled. After the first save, the saved checklist becomes the source of truth for
sidebar visibility.

## Modules vs Permissions

Modules and permissions solve different problems.

| Control            | What it does                                              | What it does not do                                       |
| ------------------ | --------------------------------------------------------- | --------------------------------------------------------- |
| Modules            | Hide or show major sidebar sections for the organization. | Prove a user is allowed to access the underlying page.    |
| Roles              | Grant a standard set of permissions for a job.            | Decide whether a whole module should appear for everyone. |
| Custom permissions | Fine-tune one user's access when a role is not exact.     | Clean up navigation for every user.                       |

<Warning>
  **Do not use Modules as access control**
  If a user should not access a workflow, update their role or custom permissions.
  Hiding a module only cleans up navigation.
</Warning>

## Change Enabled Modules

1. Review the current enabled modules.
2. Clear the checkbox for a module the organization does not use.
3. Keep at least one module enabled.
4. Save changes.
5. Have a user refresh the app or navigate again to confirm the sidebar changed.

Arcus prevents saving an empty module list. This keeps the app from hiding every optional workflow area.

Saving Modules updates the signed-in user's profile so the sidebar usually reflects the
change immediately. Other users may need to refresh, change pages, or sign out and back in
before their navigation reflects the update.

## Rollout Checklist

Before hiding a module:

* Confirm no team depends on that sidebar entry for daily work.
* Confirm related reports, settings, or workflows are not part of a current rollout.
* Tell managers which module will disappear from navigation.
* Confirm permissions separately for users who should lose access.
* Test with a non-admin user when the change is meant to simplify operator navigation.
* Confirm saved views, training materials, and support instructions do not rely on the hidden sidebar item.

## Common Blocks

* **A module is hidden but the user can still open a page by URL**: update the user's permissions.
* **A user cannot see a module that should be visible**: check Modules first, then check the user's role and permissions.
* **Save is blocked**: keep at least one module enabled.
* **The sidebar did not update immediately**: refresh the app or sign out and back in after saving.
* **Purchasing, Accounts, or Products are still visible**: those areas can appear outside the optional module list.

## Related Articles

<CardGroup cols={2}>
  <Card title="User Management" href="/support/settings/users">
    Manage roles, permissions, location access, PINs, and MFA reset workflows.
  </Card>

  <Card title="Settings Overview" href="/support/settings/overview">
    Understand how Entity Settings, Organization, and Profile settings fit together.
  </Card>

  <Card title="System Operations Settings" href="/support/settings/system-operations">
    Review the broader System settings group for printing, modules, and tags.
  </Card>

  <Card title="Audit Log and Compliance Tools" href="/support/settings/audit-compliance">
    Review security-sensitive changes and export audit details.
  </Card>
</CardGroup>