Skip to content

Overview

Site Settings is where administrators manage organisation-wide defaults: who can do what, which lists and templates apply to each application, and how the platform behaves for internal teams, suppliers, and portal users. Changes here ripple across orders, styles, shipping, compliance, and other modules, so it helps to know which area owns a setting before you adjust it.

Site Settings Overview

Quick Check - Before You Start
  • Confirm you have Site Settings access (typically Administration permissions in Roles & Permissions).
  • Identify which modules you are about to change (Company, Order, Style, Portal, and so on) and who will be affected.
  • Plan a short communication or rollout note if the change alters defaults, supplier visibility, or compliance behaviour.

The headings below summarise what each part of Site Settings controls. Open the linked overview or general settings page for step-by-step field documentation.

Company

Company settings define the organisation record itself—identity, tax, currency, and shared master data—as well as who can access which features. This is the usual place to start for branding, staff and supplier directories, communication templates, export profiles, and Roles & Permissions that gate every other module.

  • General Settings: Company name, address, contact details, branding (logo and favicon), and related defaults.
  • Tax and Currency: Tax rules and monetary context used across the platform.
  • Master data: Buyers, customers, suppliers, cost centres, tags, terms, and similar lists that other applications reference.

Order

Order settings shape how development orders are created, shared, and processed: departments, milestones, packs, forms, QA tests, and compliance-related activities. Defaults and mandatory rules configured here affect new orders and what appears on order screens and imports.

Style

Style settings control the product-development vocabulary your teams use: brands, seasons, colours, size scales, specification templates, and market-specific behaviour. Consistent lists here reduce rework and keep styles, costings, and portal views aligned.

Portal

Portal settings control what customers and suppliers see when they sign in, such as: pricing visibility, critical path views, and other B2B portal features.

These settings work alongside Company > Roles & Permissions and record sharing, ensuring portal users can only access what they’re allowed to.

  • General Settings: Critical path display, pricing display, and core B2B portal options.

Sales Order

Sales Order settings cover commercial orders after the development cycle: deposits, payment instructions, MOQ rules, and related sales terms. These options influence how sales orders are presented and validated for your markets.

Costing

Costing settings define how rolled-up costs, freight, import duties, and costing templates behave. They connect style and order data to the figures planners and merchandisers rely on.

Compliance and Licensing

Compliance settings drive audit types, auditors, document types, critical path hooks, and other compliance-specific lists. License (application-level) settings control licensing features and behaviour for your organisation.

Claims

Claim settings set defaults for new claims (managers, members, folders) and maintain the claim type list used when classifying work.

Shipping

Shipping settings cover origins, destinations, methods, warehouses, freight statuses, and shipment-specific custom fields—everything the Shipping application needs for consistent bookings and documents.

Planner

Planner settings define planning groups, target budgets, default automation, and how planning records are structured alongside the rest of the platform.

Component

Component settings govern component types, custom fields, and defaults for the Component application used in compliance and product breakdown contexts.

Best Practices

  1. Streamline data entry with defaults: Use Default Values and default managers or members in each module’s General Settings so common fields pre-populate. That speeds up entry and reduces inconsistent data.

  2. Standardise with templates: Maintain specification, document, and planning templates from Site Settings so teams reuse the same structures instead of recreating them on each record.

  3. Audit permissions regularly: When people change roles or leave, update Roles & Permissions and any portal or supplier access. Site Settings changes combined with sharing rules are a common reason external users see different data.

Documents and Files

Document behaviour like automatic folders on new records, export layouts, and communication templates are configured inside the applications that own those records. Use Company for export and communication templates, and each application’s General Settings (and related pages) for automatic folder rules on new items.

Troubleshooting

For platform-wide date and timezone behaviour that affects due dates and widgets, see Dates across applications.

Why can I not see or change a Site Settings area?

Your user account may lack Site Settings or module-level permissions. Some screens are also gated by licence or feature flags.

Steps to resolve:

  1. Ask an administrator to confirm your role under Site Settings > Company > Roles & Permissions.
  2. Verify the related module (for example Order, Style, Compliance) is enabled for your organisation.
  3. Sign out and back in after permission changes so updated access applies.
We changed a default or mandatory field setting—why are old records unchanged?

Many Site Settings apply to new records only. Existing styles, orders, or costings are not retroactively rewritten when you change defaults or mandatory rules.

Steps to resolve:

  1. Re-read the setting description on the relevant page to confirm whether it affects new items only.
  2. For existing records, update fields manually or use the product’s bulk or import tools where available.
  3. Document the effective date of the change for your team so data entry expectations stay aligned.
A supplier or portal user sees different data after we changed Site Settings—what should we check?

Portal and supplier visibility is controlled by a combination of Portal settings, Roles & Permissions, and record-level sharing. A change in one area can change what external users see without altering the underlying record.

Steps to resolve:

  1. Review Site Settings > Portal > General Settings for pricing and critical path visibility.
  2. Confirm the user’s portal role and any customer or supplier linkage in Company settings.
  3. Check whether the record was re-shared or whether caches or browser sessions need a refresh after the change.

More Site Settings-related pointers are collected under Troubleshooting > Site Settings.

Support

If you need assistance with Site Settings, you can:

  • Submit a support ticket.
  • Contact our technical support team via our contact page.