Settings, defaults, and operator preferences

General

The General section controls basic operator ergonomics:

• Theme: system, light, dark
• Table density: comfortable, compact
• Startup view: last opened, profiles, buckets

Use compact density if you work with large object lists daily. Use startup view deliberately so the app opens where you actually begin work.

Transfers

The Transfers section controls the runtime defaults for new jobs:

• Parallel uploads
• Parallel downloads
• Multipart threshold
• Multipart chunk size
• Retry limit
• Conflict behavior

These values matter more than most users think. The transfer queue can only be trusted if the runtime defaults match the job you are about to run.

Use conservative values first if:

• endpoint security is aggressive
• local disk is slow
• network conditions are unreliable

Sync

The Sync section controls job defaults:

• default mode
• dry run before execute
• delete remote extras

If you do not want sync to become a support problem, leave dry run enabled until your workflow is stable.

Preview

The Preview section controls whether inline preview is available and how aggressively it is allowed:

• enable image preview
• enable inline text preview
• max preview file size

If a user says preview is broken, check settings before treating it as a renderer defect.

URL / CDN

The URL / CDN section controls:

• default public base URL
• prefer public URL on copy

Use this section when you need copied URLs to align with public delivery instead of raw endpoint paths.

Cost Analysis

Current operator-facing cost controls:

• currency
• storage price per GB per month

This section tunes estimate output, not billing data.

Advanced

The Advanced section currently exposes:

• debug logging toggle
• retained activity entry count

Use retained activity count to keep enough recent operational history without letting the activity surface become noise.

Security

The Security section controls:

• vault auto-lock timeout
• lock on OS session lock

Session-lock behavior is enforced as part of the product security baseline. Treat the timeout as convenience policy, not as the full security model.

When settings take effect

Different settings apply on different timelines:

• theme and density affect the interface immediately
• transfer runtime settings affect new transfer jobs
• sync defaults affect new sync plans
• preview limits affect future preview eligibility checks

If you change a setting after a transfer is already queued, do not assume the running job has adopted the new values.

Recommended baseline setup

For a serious daily-use machine:

1. Set the correct theme and density.
2. Configure realistic upload and download parallelism.
3. Set multipart threshold and chunk size for your normal asset sizes.
4. Leave sync dry run enabled until your mirror rules are proven.
5. Set the public base URL if you publish assets through a fixed delivery path.
6. Configure vault auto-lock to match the risk of the machine.

When to reset settings

Use reset only when:

• the settings surface no longer reflects expected behavior
• you want to return to a known-safe baseline
• you are diagnosing whether a local preference is causing the issue

Do not use reset as a first-line answer to transfer or credential defects. Those usually come from runtime configuration, policy, or environment, not from theme-level preferences.