space.vars.productName. Each location can have registers assigned to it and can be enabled or disabled independently.
## Accessing Locations
{% stepper %}
{% step %}
### Open the NetSuite Admin view
Switch to **NetSuite Admin** in space.vars.productName.
{% endstep %}
{% step %}
### Select the subsidiary
Use the subsidiary switcher at the top right.
{% endstep %}
{% step %}
### Open Configurations
Click **Configurations** in the left sidebar, then scroll to the **Locations** section at the bottom of the page.
{% endstep %}
{% endstepper %}
## Cross-Subsidiary Inventory Viewing
At the top of the Locations section is the **Enable Cross-Subsidiary Inventory Viewing** toggle.
| Setting | Effect |
| ------------ | -------------------------------------------------------------------------- |
| **Enabled** | Users can see stock levels from other subsidiaries when browsing inventory |
| **Disabled** | Users only see stock for their own subsidiary |
Use the **Select Locations to View** dropdown to choose which locations from other subsidiaries are included when cross-subsidiary viewing is turned on.
## Locations table
The table lists all NetSuite locations associated with this subsidiary.
| Column | Description |
| ------------- | ------------------------------------------------------------- |
| **Name** | The location name from NetSuite |
| **Registers** | The number of registers assigned to this location |
| **Enabled** | Toggle to make this location visible and active in the portal |
| **Actions** | Edit the location's register and settings |
## Enabling or disabling a location
Toggle the **Enabled** switch next to a location name. Disabled locations are hidden from users and can't be selected in workflows or at checkout.
## Editing a location
Click the edit icon (pencil) in the **Actions** column to open the location settings modal.
### Location settings
| Field | Description |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Location Name** | The display name for this location |
| **Default Catalog** | When a catalog is set, it overrides the subsidiary catalog for this location |
| **Default Customer** | When set, this customer is used as the default for location-based customer selection |
| **Payment Processing Profile** | When set, this payment processing profile is used for transactions at this location |
| **Load Location** | When enabled, this location is forced to load by setting a session variable with key `location` and this location's ID as the value |
### Location branding
| Field | Description |
| --------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Logo** | If no logo is set, the application shows the space.vars.productName logo by default |
| **Theme** | If no theme is selected, the application shows the space.vars.productName theme by default |
### Registers
Each register assigned to this location is listed with the following details:
| Column | Description |
| --------------------- | -------------------------------------- |
| **Register Name** | The name of the register |
| **Assigned Employee** | The employee assigned to this register |
Each register can have one or more **Terminals** configured:
| Field | Description |
| -------- | --------------------------- |
| **Name** | The terminal's display name |
| **TSN** | The terminal serial number |
**POS Assignment v2:** For more granular control over which locations and registers each employee can access, and to set their login behavior (manual selection, auto-select, or auto-lock to a register), see the **POS Assignment** section of your subsidiary setup. That interface lets you define access rules at the employee level across multiple locations.
### Session Variables
Define variables specific to this location. These variables can override subsidiary-level session variables for transactions and workflows at this location.
## Common pattern: employees who work across locations
If your staff move between locations (a roaming supervisor, a rep who covers several stores), don't rely on one location being loaded automatically for everyone. Instead, have your Client Admin add the **Location** component to an early page in their workflow so they can pick their working location for the session, and use [Session Variables](/netsuite-admin-guide/overview-1/session-variables.md) to carry that choice through the rest of the portal.
## Tips
* **One register account per physical terminal.** Rather than a login per employee, most organizations set up one generic register account per terminal (e.g. *Register 1*, *Register 2*) and rely on cashier PINs (see [Managing PIN Codes](/netsuite-admin-guide/overview-3/pin-codes.md)) to identify who's actually running each sale.
* Only enabled locations appear in the portal when users select a location or register at login.
* If a location has no registers assigned, it can't be used at a POS terminal.
* **POS Assignment v2 access rules:** If you need employees to have access to specific locations and registers (and control their login flow), this is now configured in a dedicated section rather than per-location here. You define which employees can work at which locations, and how they select or lock into a register.
* Cross-Subsidiary Inventory Viewing is useful for businesses where stock is shared across multiple subsidiaries or warehouses.
## Related Pages
| Configurations Overview | All sections on the Configurations page. | Configurations |
| Session Variables | Setting a default location via session variables. | Subsidiary Session Variables |
| Card Present Payments | Subsidiary-level payment profile (location overrides apply on top). | Card Present Payments |
| POS Assignment | Define which locations and registers each employee can access, and set login behavior (manual, auto-select, or auto-lock). | POS Assignment |