This article provides a comprehensive guide to managing Product Libraries within the Enterprise Admin Console. Learn how to efficiently setup a centralized Product Library, understand the difference between Enterprise and Company libraries, and configure local visibility.

During the Beta, our goals are to validate core functionality in real-world workflows, surface any usability or performance issues, and gather your feedback to refine the final release.

We'll be continuously improving the interface during this phase, so some screenshots in this guide may look a little different from what you see in the product. That's expected. If you spot anything that could be better whether it's functional, visual, or how the experience feels, please tell us. Your feedback directly shapes the final product.

This guide is designed for Enterprise Admins and IT Admins who manage Product Library content and access within their organization.

The entire Beta test will take place in a relatively isolated environment. Only users running the TestFlight version of the App will experience the changes introduced in this Beta. Users on the standard App version will not be affected — their access permissions and available product libraries will remain the same as before, ensuring no impact on their daily work.

Please note that while the Beta environment is relatively isolated, but it is not a "sandbox." The Enterprise Library used in this Beta is the same one your company will continue to use after the Beta phase. All content and settings from this stage will be retained after Beta ends.

That said, you don't need to worry too much about "messing up" the Enterprise Library during testing. If necessary, you can contact ArcSite to have your Enterprise Library reset.

The Enterprise Product Library is a centralized catalog of products (and bundles) that an enterprise can share across all sub-companies. Instead of each sub-company maintaining its own isolated list, the Enterprise Library lets you manage a single source of truth while still tailoring which products and prices each sub-company or end user can use through Configurations and User Group Views.

Currently, you can operate in one of two modes at a time:

By default, each ArcSite Company will have a local library enabled. End users can only use one library at a time — either the Enterprise Library or the Sub-Company Library — but not both simultaneously. When one library is set to Enabled, the other will be automatically set to Disabled.

You can still edit a library if its disabled by clicking Manage Library.

Open the Enterprise Library by clicking Manage Library and clicking New Product

A library Configuration is a customized version of the Product Library that defines which products are available and what prices apply. It allows Enterprise Admins to tailor the shared product library to meet the needs of different teams—showing only the relevant products and applying region-specific pricing when needed.

Every Enterprise Library includes a Default Configuration that contains all products at their original (library) prices. This default is intentionally uneditable; it acts as the baseline and ensures there is always a complete, consistent fallback. Any sub-company that isn't explicitly assigned to a custom Configuration automatically uses this default.

Click Create New Configuration to add a new configuration

Click Override Price to make Configuration specific price changes

Click Assign Configuration to select a specific ArcSite Company

Where Configurations tailor the product catalog for a company, User Group Views refine what different roles actually see and use within a sub-company. A View acts as a layer of availability within the library/context you're already in. Admins can create Views to determine which items appear for specific user groups in the app, enabling role-appropriate product access without duplicating catalogs.

Access is additive: a user's effective product list is the union of all Views assigned to their group(s). Views do not alter prices or product attributes; they simply decide what's visible and usable for a given role and context. Because this mechanic applies to both Enterprise and Company Libraries, organizations can use the same mental model regardless of which mode they're operating in.

Start by opening the Company admin and go to Settings > User Groups

Click Create New User Group. User Groups could represent a business unit, geographic region, or user role.

Click Add Members to select a specific set of users.

Go to the Products tab and click Access Controls in the top right

Click Create New User Group Views, add a name, and select specific User Groups

Click Edit User Group View to change Product Library settings and availability

Simplest form. The Enterprise creates one central Product Library, and each Company inherits the full library.

Offers flexibility at the Company level. The Enterprise creates one central Product Library. The Enterprise Library is segmented and modified using Library Configurations. Assign a specific Configuration to each Company.

Properties you can edit in Configurations:

Fully managed library from top down. The Enterprise creates one central Product Library. At the local Company User Groups are managed to segment the Product Library.

Properties you can edit in User Group Views:

What's the difference between Library, Configuration, and User Group View?

When do I create a custom Configuration vs. a User Group View?
Use a Configuration for company-level differences (what's available, what's overridden). Use Views for role-level differences (who sees what).

Can a company use more than one Configuration?
No—one Configuration per company per library. Keep role differences in Views.

Why can't I edit product attributes in a Configuration?
Attributes live in the library (source of truth). Configurations only control availability and price overrides.

Can I edit the Default Configuration?
No. Default is fixed (all products, original library prices). Create a new custom Configuration when you need differences.

How do margins work with Calculated Price?
Price = Cost ÷ (1 − Margin). Set Product Margin per sub-company; if missing, the Enterprise Product Margin is used as a fallback (which may not match local intent).

Can I copy products between libraries?
Direct cross-library copy isn't supported. Use Export/Import spreadsheets to seed the Enterprise Library (or contact ArcSite for help).

Will switching modes break existing drawings?
No. Legacy items are flagged, remain editable on canvas, but can't be added anew and won't receive future library updates. Replace them with items from the enabled catalog if needed.

Can I run Enterprise and Company Libraries at the same time?
Only one can be enabled for end-user selection. Enabling one disables the other.

I see "Varies by company" for a price—what does it mean?
The item uses Calculated Price, and margins differ across sub-companies. Open the flyout to view each company's price.

Do I need to do anything with my integration mappings before enabling Enterprise Library?
Yes — contact ArcSite before enabling. When Enterprise Library is turned on, existing mappings set up at the sub-company level stop working immediately. Your data is preserved and will reactivate if you turn it off, but there will be a gap while mappings are rebuilt at the Enterprise Library level. Planning ahead with ArcSite minimizes that window.

Will my existing mappings be deleted if I enable Enterprise Library?
No. Your mapping data is preserved in the backend — it's just not read while Enterprise Library is on. If you turn Enterprise Library off, the original mappings take effect again immediately.

I enabled Enterprise Library and now my QuickBooks / i360 pushes seem to be working, but the product fields are blank — what happened?
This is a known behavior when mappings haven't been rebuilt after enabling Enterprise Library. QuickBooks and i360 don't surface an error when a product mapping is missing — the record pushes successfully but with an empty product reference. Please open a support ticket so we can rebuild the mappings. We also recommend reviewing any records pushed since you enabled Enterprise Library and correcting the empty product fields on your end.