Organization Settings
Table of Contents
1. Use Cases
Quick links: Standardize timezone, units, and currency for the whole organization | Enforce two-step verification login across the organization | Allow only company Google accounts for Google sign-in
Case 1: Standardize timezone, units, and currency for the whole organization
Situation: You have just taken over this warehouse's back office and noticed that report times don't match actual operation times, the currency has to be reset every time you create a new merchant, and product length/width/height/weight units have no consistent standard. You want to set the organization-wide baseline first so that all later operations follow it.
Use this feature: Go to Timezone, System Language, Default Currency to set organization-level defaults, and use Unit Settings to unify length, weight, and volume units. These settings apply across the entire organization.
Result: Scheduling and reports are calculated in the timezone you set, the default currency is filled in automatically when creating a new merchant, and product dimensions and weights are shown in one consistent set of units across the organization.
Case 2: Enforce two-step verification login across the organization
Situation: Company security policy requires everyone to pass two-step verification at login. You need to apply this rule to all warehouse users (and, depending on plan, merchants too) at once, rather than notifying each person individually to turn it on themselves.
Use this feature: Go to Two-Step Verification Policy and enable the forced two-step verification for the relevant role. Once enabled, users who haven't set it up yet are guided to complete the setup on their next login.
Result: The rule takes effect across the organization immediately and login security is leveled up, without you having to track who has enabled it and who hasn't one by one.
Case 3: Allow only company Google accounts for Google sign-in
Situation: Your company manages staff accounts in Google Workspace. Now that warehouse staff sign in with Google, you do not want anyone using a personal Gmail account, and you want staff who leave — and are suspended in Google — to lose Google sign-in to the warehouse system.
Use this feature: In Google Sign-in, switch to company domains only, ask staff to link their company account in their profile, and track progress with the count under the section.
Result: Only Google Workspace accounts in your company domains can sign in with Google; once a staff member's Google account is suspended, it can no longer be used to sign in with Google.
2. Feature Overview
Organization Settings is the page for the organization's shared baseline. The timezone, language, default currency, and units of measure set here become the defaults for organization-wide scheduling, reports, notifications, and new merchant creation; the two-step verification policy decides whether two-step verification is enforced at login. Every setting is configured once and applied across the whole organization — this is the warehouse supervisor's entry point for setting organization-level standards.

Quick jump: Basic Information | Unit Settings | Two-Step Verification Policy | Editing Settings | Google Sign-in
2.1 Basic Information
The upper part of the page shows the organization's shared baseline; most fields can be adjusted after entering edit mode.
| Field | How to fill in | Notes |
|---|---|---|
| Workspace | Generated by the system; cannot be edited here | Shows the organization's identifier code; click to copy |
| Timezone | Select the organization's timezone from the list | Used for time calculations in scheduling and reports |
| System Language | Select the organization's default language from the list | Used for notification emails and system notifications; merchants can override individually |
| Default Currency | Select a currency from the list | Filled in automatically when creating a new merchant |
| Plan | Set by the system; cannot be edited manually | Shows the current plan (Standard / Advanced / Pro / Enterprise) |
2.2 Unit Settings
Unify the units used to present product dimensions and weight across the organization, with three separate choices:
| Field | How to fill in |
|---|---|
| Length Unit | Choose Centimeters (CM) or Inches (IN) |
| Weight Unit | Choose Kilograms (KG) or Pounds (LB) |
| Volume Unit | Choose Cubic Meters (CBM), Sai (材, 27,000 cm³), or Cubic Feet (ft³); newly created organizations default to ft³ |
The length and weight units apply to the dimension and weight fields of products and consumables: new, edit, detail and list screens mark the current unit in the field title or next to the input, and the product import template and exports made without an export template use the same units; exports made with an export template always write these fields in centimeters and kilograms (when a template is created, the default header of these columns carries "(CM)" / "(KG)"; templates created earlier may have headers with no unit, see the FAQ). Inches and pounds are always shown and entered with up to 2 decimal places. Everything is stored in centimeters and kilograms, and shipping rate tiers and billing details keep using centimeters and kilograms regardless of these two settings.
2.3 Two-Step Verification Policy
Decides whether two-step verification (TOTP) is enforced at login. After enabling the policy for a role, all users of that role must use two-step verification at login; users who haven't set it up are guided to complete the setup after logging in.
| Field | How to fill in | Notes |
|---|---|---|
| Require warehouse users to enable two-step verification | Toggle the switch to enable or disable | When enabled, all warehouse users must use two-step verification at login |
| Require merchants to enable two-step verification | Toggle the switch to enable or disable | When enabled, all merchants must use two-step verification at login; this option does not appear on the Standard plan, and can be set on every other plan |
When viewing the status, an enabled policy shows the "Required" tag, and a disabled one shows the "Optional" tag.
2.4 Editing Settings
The page is in view mode by default. Click Edit in the top-right corner to enter edit mode, then submit to save after adjusting, or cancel to discard changes. After a successful save, the page shows a success message and returns to view mode.
Adjustments apply to the entire organization immediately, with no additional review or activation step.
2.5 Google Sign-in
Limits which Google accounts warehouse staff can use with “Sign in with Google”. This section has its own “Save” and is not affected by the edit mode above; an upgrade hint appears when this feature is unavailable.
You can edit and save only after the existing settings load successfully. If loading fails, click “Retry”; retrying does not clear your saved domain restrictions.
| Option | Description |
|---|---|
| Any Google account | Default. Anyone who linked a Google account can sign in with Google, including personal Gmail |
| Only company accounts in these domains | Accepts only company Google Workspace accounts whose email domain exactly matches the list; type a full domain and press Enter, up to 20 |
- Domains must match exactly: acme.com does not include mail.acme.com, so add each one you need; wildcards and gmail.com are not accepted.
- This setting only limits Google sign-in; password and passkey sign-in are not affected.
- Saving takes effect immediately: staff already signed in with a Google account that does not match are blocked on their next action and need to sign in another way. Live notifications briefly reconnect; staff whose Google sign-in no longer meets the policy stop receiving notifications.
- If you are currently signed in with a Google account the new list would reject, saving is refused so you are not locked out.
- Once domains are limited, staff can link only Google accounts on the list. Accounts linked earlier that do not match are not removed, but cannot be used to sign in; staff need to unlink them before linking a company account.
- The count under the section shows how many staff linked a matching Google account, so you can judge when to ask everyone to switch to company accounts.
- Requires permission to edit organization settings; every change is recorded in the audit log.
For how staff link a Google account, see Sign-in and account security.
3. FAQ
3.1 FAQ
▪ Why can't I see the Edit button?
Editing requires write permission for organization settings. If you only have view permission, the page is shown in view mode without the edit button. If you can't see this button, please contact your administrator to confirm your permissions.
▪ Why is there no "Require merchants to enable two-step verification" option?
Requiring merchants to enable two-step verification is available on every plan other than Standard. If your organization is on the Standard plan, this option will not appear; the warehouse-side two-step verification policy, however, is not restricted by plan and can always be set.
▪ After changing System Language, will all merchants' languages change too?
System Language is the organization's default language, used for notification emails and system notifications. Merchants can override it individually in their own settings, and once overridden they are not affected by the organization default.
▪ If I change Default Currency, will the currency of already-created merchants change too?
No. Default Currency is only filled in automatically as a default when creating a new merchant; the currency of existing merchants is not affected.
▪ Why can't Workspace and Plan be edited?
These two are set by the system and cannot be edited manually on this page. Workspace is the organization's identifier code and Plan is the current subscription plan; both are view-only.
▪ What is the difference between Sai and ft³?
They use different bases: Sai is the Taiwanese sai (材), where 1 sai = 30 × 30 × 30 cm (length × width × height ÷ 27,000); ft³ is 1 cubic foot (length × width × height ÷ 28,316.85). The same item comes out at about 0.95 times the Sai figure when shown in ft³. Organizations previously set to "Sai" were switched to Sai automatically, so their numbers are unchanged; export templates that had the old Sai total-volume column now use "Total Volume (Sai)".
▪ Does changing Volume Unit or Weight Unit affect existing rate cards and shipping rules?
No. Rate cards and sales channel volume rules each record their own unit; these two settings only decide which unit is pre-filled when one is newly created:
- Rate cards: volume- or weight-based storage prices are charged in the rate card's own "Pricing unit". After the organization unit changes, existing rate cards keep billing in their original unit; to switch units, create a new rate card version — see Merchant Details & Settings.
- Shipping switch rules: each volume rule's threshold is compared in the unit selected on that rule, so nothing needs to be re-entered — see Shipping Switch Rules.
- 新竹物流(HCT) shipping accounts billed "By Volume" are always calculated in Sai, regardless of these settings.
▪ If I change Length Unit or Weight Unit, are the dimensions and weights of existing products and consumables changed?
No. Data is always stored in centimeters and kilograms; changing the unit only changes how values are shown on screen and in files. Inches and pounds are rounded to 2 decimal places on screen, though — for example 10 cm is shown as 3.94 in. Saving without touching a field writes back the original 10 cm; only typing a new value into the field replaces it with the converted new value.
▪ After switching to inches or pounds, do I need to re-create my existing Export Templates?
Yes, but not because of the exported units. An export made with an export template is not affected by Length Unit or Weight Unit: dimensions and weight are always written in centimeters and kilograms, so the exported values never turn into inches or pounds. The reason to re-create is the headers: in templates created earlier, the dimension and weight column headers may not state a unit. When such an exported file is edited and imported back as products, the system finds no unit in the header and reads the values in the organization unit (inches or pounds) — for example 10 cm is read as 10 in and stored as 25.4 cm, with no error. Before you switch to inches or pounds, go to Export Templates and create the templates again (new templates label the dimension and weight headers "(CM)" / "(KG)"), then export with the new ones. If you can't re-create them yet, you can also rewrite those column headers to include the unit before importing — see Import Products.
▪ After enabling forced two-step verification, are users blocked immediately?
They are not blocked right away. Users who haven't set up two-step verification are guided to complete the setup after their next login, rather than being locked out directly.
▪ After limiting Google domains, can staff who left still sign in with a password?
Yes. The Google domain list only limits Google sign-in; to fully remove access, deactivate the person in Operators.
3.2 Notices
⚠️ Important Reminders
- Enabling a two-step verification policy applies to all users of that role. Make sure your whole team can comply before enabling it.
- Units of measure and currency are organization-level shared baselines; adjusting them affects the presentation across the whole organization and the default for new merchants — not just a single warehouse or a single merchant.
- Re-create your export templates before switching to inches or pounds. If the dimension or weight headers of an older template state no unit, importing its exported file back reads the values as inches or pounds, so they come out too large with no error.
💡 Tip: Timezone directly affects the time calculations for scheduling and reports. Before setting it, confirm it matches the location where the warehouse actually operates.
4. Related Features
| Feature | Description | Link |
|---|---|---|
| Operators | Manage warehouse user accounts and permissions | Go |
| Holidays | Set the organization's holidays and business days | Go |
| Accessible IPs | Set the IP ranges allowed to log in | Go |
| Sign-in and account security | Staff link their own Google account | Go |
| Warehouse Broadcasts | Publish warehouse announcements to operators | Go |