Setting component defaults

You can set component defaults in two ways: from a component on the canvas, or through the settings interface. This guide covers both methods.

Setting defaults from current component

The fastest way to set defaults is from a component you've already configured:

Create and configure a component with the properties you want as defaults.
Select the component on the canvas.
Click the Set as Default dropdown button in the edit panel.
Choose the scope: Organization, Project, or User.
Click to confirm.
A success message confirms the defaults are saved.

All electrical and sizing properties from the selected component become the new defaults for that scope. Future components of the same type use these values.

Example workflow:

You configure a cable with:

XHHW-2 copper conductor series
90°C termination temperature
40°C ambient temperature
Cable tray installation

You select Set as Default → Organization. Now all new cables created by anyone in your organization use XHHW-2 copper, 90°C termination, 40°C ambient, and cable tray installation.

The Set as Default dropdown appears in the edit panel when you select a component. It shows available scopes based on your permissions:

For all users:

User - Save as your personal defaults

For project editors and owners:

Project - Save as defaults for this project only

For organization admins and owners:

Organization - Save as defaults for all org members

The dropdown is disabled if you lack permissions for higher scopes. You can always set user defaults regardless of role.

Choosing scope (org, project, user)

Consider the scope's impact when setting defaults:

Set organization defaults when:

You want consistency across all company projects
The setting represents a company standard
Multiple projects will benefit from the same default
You're an organization admin defining company-wide specs

Set project defaults when:

Only this project needs the specific values
Client requirements differ from company standards
Testing alternative configurations
Project has unique environmental conditions

Set user defaults when:

The setting is your personal preference
Other users may prefer different values
You frequently create specific component types
You want quick access without affecting others

Organization defaults affect everyone in your org. Project defaults affect everyone working on that project. User defaults affect only you.

Confirming default save

After you select a scope from the dropdown:

A confirmation dialog may appear (depending on scope).
Review the scope and component type being saved.
Click Confirm to save the defaults.
A toast notification confirms success.

The defaults take effect immediately for new components. Existing components are not affected.

Viewing active defaults

To see what defaults are currently active:

Go to Settings.
Navigate to Component Defaults.
Select the scope you want to view: System, Organization, Project, or User.
Select the component type (Cable, Motor, Load, etc.).
The defaults editor shows all active defaults for that scope and component.

Fields with values from higher scopes show the value in the input field with placeholder text indicating the source.

Example:

You're viewing user defaults for cables. You see:

Conductor material: CU (from system, grayed out placeholder)
Termination temp: 90°C (your user override, normal text)
Ambient temp: 35°C (from org default, grayed out)

This shows you overrode termination temp at user level, ambient temp comes from org defaults, and conductor material uses the system default.

Resetting defaults

To remove overrides and revert to lower-tier defaults:

Reset individual field:

Open the defaults editor for the scope and component type.
Find the field you want to reset.
Click the X button next to the field.
The field clears and reverts to the next lower tier's value.

Reset all fields for scope:

Open the defaults editor.
Click Clear All button at the bottom.
Confirm the action.
All overrides for that scope and component type are removed.
Values revert to lower-tier defaults.

Example:

You set user defaults for motor power factor = 0.92. Organization defaults have 0.85. System defaults have 0.85.

If you reset your user default:

User default: (cleared)
Effective value: 0.85 (from organization)

If org admin resets organization default:

Organization default: (cleared)
Effective value: 0.85 (from system)

Setting defaults through settings interface

For more control, set defaults through the settings interface:

Go to Settings (gear icon).
Navigate to Component Defaults.
Select the scope from the dropdown: Organization, Project, or User.
Select the component type: Cable, Motor, Load, etc.
Edit individual fields as needed.
Click Save when done.

This method allows you to set defaults without creating a component first.

Common default fields by component type

Cable:

Conductor material (CU, AL)
Termination temperature (60°C, 75°C, 90°C)
Ambient temperature (°C)
Installation type (Conduit, Cable tray, Direct burial, etc.)
Cable series selection
Number of current-carrying conductors

Motor:

Power factor (0.80 - 1.00)
Efficiency (0.85 - 0.98)
Service factor
Starting method (DOL, Star-delta, VFD)

Load:

Power factor (0.80 - 1.00)
Load type (Resistive, Inductive, Capacitive)
Continuous operation flag (true/false)

Transformer:

Impedance percentage (by kVA rating)
Cooling type (Self-cooled, Forced air, etc.)
Tap changer type (No-load, On-load)
Vector group

Bus:

Bus type (Main switchboard, Feeder, Load-side)
Enclosure type (Switchboard, Panelboard, Switchgear)

Sizing Defaults:

Default Cable Series - preferred cable series for auto-sizing calculations
Switch Sizing Margin - default 15% extra current margin for auto-sized disconnect and load-break switches
Auto Parallel Sizing - enable or disable automatic parallel conductor sizing
Max Single Conductor Size - largest conductor before the engine tries parallel runs (350 to 750 kcmil)
Max Parallel Runs - upper limit on parallel conductor runs (2 to 6)

See Auto-parallel sizing for details on how these settings affect conductor sizing.

Best practices

Start with user defaults:

Experiment with your personal defaults first
Once settled on values, escalate to project or org defaults
Prevents affecting other users while learning

Document organization defaults:

Maintain a reference document explaining why specific org defaults exist
Note any code requirements or standards driving the defaults
Helps new team members understand company practices

Review defaults periodically:

Code updates may change recommended values
New materials or technologies may become available
Regional climate data may shift default ambient temperatures

Use project defaults sparingly:

Too many project-specific overrides make troubleshooting difficult
Prefer organization defaults for common scenarios
Reserve project defaults for genuinely unique requirements

Communicate changes:

Notify team when changing organization defaults
Explain why defaults changed
Give team time to adjust workflows

Permissions required

To set user defaults:

Any user (affects only yourself)

To set project defaults:

Project owner or editor role
Affects all project members

To set organization defaults:

Organization admin or owner role
Affects all organization members across all projects

Attempting to set defaults above your permission level shows an error or disables the option.

Understanding defaults - Defaults hierarchy and how merging works
Component defaults editor - Detailed editor features
User settings - Managing personal user defaults
Organization settings - Organization-wide configuration