> ## 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.
# System Operations Settings
> System Operations settings control day-to-day operator tools: printing, sidebar module visibility, tags, developer access, and data exports. Use these settings to keep workstations printing correctly, simplify navigation, label records, and handle sensitive export or integration workflows safely.
This overview explains how Printing, Modules, Tags, Developers, and Data Export fit together. Use the
dedicated guides when you are actively configuring printers, hiding sidebar
modules, creating actionable tags, managing developer access, or exporting entity data.
Configure PrintNode health, default printers, auto-print, filters, and failed jobs.
Hide or show major sidebar modules without changing user permissions.
Manage system and custom labels, scopes, and actionable tag behavior.
Manage API keys, webhooks, request logs, analytics, collection downloads, docs links, and SDK entry points.
Request CSV or JSON exports for compliance, business intelligence, migration, or portability work.
## Open System Operations Settings
1. Open **Settings**.
2. Choose **Entity Settings**.
3. Open the **System** group.
4. Use **Printing**, **Modules**, **Tags**, **Developers**, or **Data Export**.
## Printing
Printing settings connect Arcus workflows to the printers available through
PrintNode. Labels, packing slips, merged document packets, category-filtered
package views, and print job history all depend on these settings.
* **Connection status**: confirms whether Arcus can reach the PrintNode connector and discover printers.
* **Default Label Printer**: used for shipping labels, usually a 4x6 thermal printer.
* **Default Document Printer**: used for packing slips, PDFs, and merged packets.
* **Auto-print on fulfill**: sends the label and packing slip automatically when a package is fulfilled.
* **Printer Category Filters**: limits a workstation view to packages that contain matching product categories.
* **Recent Print Jobs**: helps investigate failed, blocked, queued, or submitted print attempts.
**Offline printers do not stop the shipment by themselves**
If a printer is offline, Arcus can block or record the print job while the shipping
or fulfillment action continues. Always review the job history before reprinting so
the team does not create duplicate labels or miss paperwork.
## Modules
Modules decide which major sections appear in the sidebar for the organization.
This is useful when a team does not use a module and wants a cleaner navigation
surface.
**Modules are not security controls**
Hiding a module removes it from the sidebar, but permissions still decide what users
can view or change. Use User Management and roles for access control.
* **Orders**: sales orders, invoices, and order management.
* **Inventory**: inventory, warehouse, bins, serials, and stock tools.
* **Fulfillment**: packing, shipping labels, and fulfillment queues.
* **Accounting**: GL, AP, AR, journal entries, and reports.
* **Shipping**: rate shopping, labels, tracking, and shipment tools.
* **Returns**: customer RMAs and vendor returns.
**At least one module must stay enabled**
Arcus prevents saving an empty module list. Core items such as Dashboard, Accounts,
Products, Purchasing, Support, Organization, and Settings can still appear outside
this module list.
## Tags
Tags label orders, accounts, products, returns, and packages. Some tags are purely
informational. Actionable tags can change workflow behavior, such as blocking
fulfillment or blocking new orders.
* **System tags**: seeded by Arcus, protected from deletion, and often tied to known workflow behavior.
* **Custom tags**: created by your team for local process, review, routing, or reporting needs.
* **Applies to**: limits where a tag can be attached, such as orders, accounts, products, returns, or packages.
* **Actionable**: marks a tag as more than informational when a supported workflow reads it.
* **Active**: hides a tag from future use without removing it from every historical record.
**Use specific tag names**
A tag named "Needs review" is easy to overuse. Names like "Hold for billing",
"Call before shipping", or "Do not ship until address confirmed" are easier
for operators to act on.
## Developers and Data Export
Developers and Data Export are System settings because they affect integration,
portability, and compliance workflows for the active entity.
* **Developers** is available to entity owners and admins. Use Test mode before Live, use narrow scopes, and revoke keys or webhooks when a vendor, script, or project ends.
* **Data Export** creates CSV or JSON files for selected entity data. Exports can include customer, vendor, product, order, invoice, accounting, inventory, and activity history, so treat downloads as sensitive files.
* **Audit Log** should be part of the review loop after developer access changes or sensitive data exports.
**Exported files and integration secrets leave the normal app boundary**
Store exported files, API keys, webhook signing secrets, and environment files only in
approved locations. Delete temporary copies after the business purpose is complete.
## Recommended Setup Order
1. Connect PrintNode in Integrations before configuring printers.
2. Confirm each workstation sees the correct label and document printers.
3. Turn on auto-print only after a pack-and-ship test succeeds.
4. Use category filters only when printer stations handle different product groups.
5. Review modules with managers before hiding navigation sections.
6. Create tags for real decisions, not every small note.
7. Test actionable tags on a sandbox record before relying on them in production.
8. Use Test mode before issuing Live API keys or webhooks from Developers settings.
9. Decide who is allowed to request Data Export files and where those files must be stored.
## Common Blocks
* **No printers appear**: confirm the PrintNode connector is connected and the PrintNode client is running on the host computer.
* **Labels print on the wrong device**: check the default label printer and the workstation printer selection.
* **Auto-print did not happen**: confirm auto-print is enabled, the package was fulfilled, and the printer job history does not show a blocked job.
* **A team member cannot see a module**: check module visibility first, then check the user's role and permissions.
* **A tag is not available on a record**: confirm the tag scope includes that record type and the tag is active.
* **A tag blocks work unexpectedly**: review whether the tag is actionable, then remove it from the record or adjust the tag catalog.
* **Developers tab is missing**: confirm the user is an owner or admin and API access is enabled for the entity.
* **Data Export is disabled**: confirm an entity is selected and your role allows export work.
* **Export file is missing rows**: confirm the export type, date range, format, and selected export settings.
## Related Articles
Configure Shippo, carrier defaults, shipping rules, freight routing, PackPilot, scanners, and PrintNode printing.
Connect Stripe, marketplaces, shipping, email, and other services.
Invite users, manage entity access, roles, permissions, location restrictions, PINs, and MFA reset workflows.
Create customer and vendor accounts with terms, addresses, and preferences.
Operate the station view for picking, packing, and shipping.
Configure PrintNode connection checks, defaults, printer filters, failed jobs, and safe reprints.
Hide or show major sidebar sections while keeping permissions separate.
Manage system tags, custom tags, scopes, and actionable blocking behavior.
Manage entity API keys, webhooks, logs, analytics, collection downloads, and docs links.
Request and protect CSV or JSON exports from the active entity.
Understand the admin surfaces, settings groups, and workflow impact areas.