Presets

Simplifying Configuration Management.

What are Presets?​

Presets are reusable configuration templates that allow you to save and apply common settings across multiple areas of your e-commerce platform. Think of presets as "saved settings profiles" that can be quickly applied instead of manually configuring the same settings repeatedly.

How Presets Help You​

Presets save time and ensure consistency by allowing you to:

• Create a configuration once and reuse it multiple times
• Apply the same settings to multiple entities with just a few clicks
• Update all linked configurations by changing just the preset
• Maintain consistency across your store's configuration

Where Presets Can Be Used​

• Buyer Permissions
• Sharing Settings
• Live Stock
• Live Availability
• Supplier Punchouts

When managing access for your buyers, presets allow you to:

• Create standard permission profiles (like "Basic User," "Department Manager," etc.) based on users, user groups or custom fields sent to us from your procurement or ERP system.
• Apply consistent permission sets to multiple users or groups
• Update permissions for many users at once by modifying the preset
• Ensure new users receive standardized access appropriate to their role based on business logic external to Axiom.

Benefits of Using Presets​

• Time Savings: Configure once, apply many times
• Consistency: Ensure uniform settings across your platform
• Simplified Management: Update multiple configurations by changing one preset
• Reduced Errors: Minimize mistakes from manual configuration
• Easier Onboarding: Quickly apply standard settings to new entities

By leveraging presets effectively, you can streamline your administrative workflows and maintain a more consistent experience.

How presets are applied​

This guide explains, in plain language, when a preset will affect a user and their content. It focuses on the practical rules you can rely on when configuring presets.

What is a preset?​

• Preset: A saved configuration that can modify behavior or visibility for targeted users. Presets live within a store and can be attached to content, features, or rules.
• Active only: Only presets marked as enabled are considered.

The two places presets can come from​

• Attached to the thing you’re viewing: The system looks for presets linked to the item (for example, a piece of content or a rule). If any attached preset applies to the user, its effects take place.
• Targeting built into the item itself: Some items have their own targeting (the same kind of user/group/location/custom-field criteria) without needing a separate preset. If that built‑in targeting applies, the effect also takes place.

If either layer matches, the user will see the effect.

Who can a preset target?​

• Everyone: Apply to all users.
• Specific people: Apply to named users.
• User groups: Apply to anyone in one or more user groups.
• Location areas: Apply to users inside or outside saved geographic areas.

These “who” checks are treated as alternatives: being a named user, being in a targeted group, or being within a targeted area can each make you eligible.

Custom fields as additional context​

You can also scope presets to session “custom fields” (for example, values like Cost Center, Plant, Department).

• When custom fields are considered: Only when the session actually provides custom fields. If no custom fields are sent, presets won’t filter by them at all.
• How matching works:
  • The preset matches if it contains every name/value pair the session sent.
  • It’s fine if the preset lists extra pairs the session didn’t send.
  • Presets that don’t specify any custom fields also match when custom fields are present.
• Case handling: The keys for the pairs are flexible. You can send Name/Value as name/value, NAME/VALUE, or mixed case.

In other words, custom fields act as an optional context filter: if they’re present, the preset must be compatible; if they’re not present, the preset won’t be blocked by custom-field rules.

Putting it together (AND vs OR)​

• Within “who” targeting (named users, groups, location), any of them can qualify you. Think of this as OR.
• Custom fields are combined with the “who” check. If custom fields are present, they must also match for the preset to apply. Think of this as AND with the optional custom-field filter.

So the overall flow is:

1. Does the user qualify by identity, group membership, or location? If yes → continue.
2. Did the session send custom fields? If yes → the preset must also be compatible with those custom fields. If no → skip this check.
3. If steps 1 and 2 pass, the preset applies.

Store scope and enablement​

• Store‑scoped: Presets are tied to a specific store. Only presets from the current store are considered.
• Enabled: Presets must be turned on to have any effect.

Practical examples​

• Group only: A preset targets user group “Buyers”. Any user in “Buyers” sees it. No custom fields are required.
• Group + custom fields: A preset targets “Buyers” and includes custom fields such as CostCenter=1001. If the session sends CostCenter=1001, the preset applies to any user in “Buyers”. If the session sends CostCenter=2002, it doesn’t apply. If the session sends no custom fields, the preset still applies to “Buyers”.
• Location area: A preset includes a geographic area. Any user in that area qualifies, even if they aren’t in the named group or list of users.
• User‑level override: A preset lists a specific user. That user qualifies regardless of group membership.

Frequently asked questions​

• If I set both a user group and a custom field, do both need to match?

  • Yes. The user must qualify by identity/group/location AND the custom fields (if present) must be compatible.

• What happens if the session doesn’t include custom fields?

  • Custom fields are ignored. Eligibility is decided solely by user/group/location.

• Do custom field keys have to be lowercase?

  • No. The system accepts Name/Value in different cases (name/value, NAME/VALUE, etc.).

• Do I need to send every custom field a preset lists?

  • No. A preset will match if it contains all the pairs you sent. It can have additional pairs beyond what the session provided.

• Can an item apply without any preset?

  • Yes. Items can have built‑in targeting. If that targeting matches, you’ll see the effect even without an attached preset.