Standardize Your Device Information: Best Practices for Endpoint Naming
Introduction
A consistent device-naming convention helps administrators identify a device’s location, purpose, orientation, and sequence without opening every device record. Appspace does not require the convention in this guide; organizations should adapt it to their own operational standards.
Key Benefits
This article provides the following benefits:
- Faster troubleshooting: Locate the correct device quickly from reports, alerts, and support requests.
- Scalable organization: Add devices across locations without creating ambiguous names.
- Clear ownership: Use recognizable location and function terms that match the organization’s hierarchy.
What This Guide Covers
This guide covers the following topics:
- Choosing naming components
- Building a no-space naming pattern
- Using examples
- Applying names during or after registration
- Maintaining the convention
Prerequisites
Before you begin, confirm the following requirements:
- Administrative access: You need a Platform license and an Account Owner or Location Admin role for the target device.
- Location hierarchy: Create consistent location names and abbreviations.
- Device inventory: Identify each display’s location, use case, orientation, and sequence.
- Approved convention: Document the allowed abbreviations and separators before renaming a large device estate.
Choose Naming Components
Recommended Elements
- Location: City, campus, building, or site abbreviation.
- Floor or area: Floor number, lobby, cafeteria, reception, or department.
- Function: Menu board, welcome display, wayfinding, room panel, kiosk, or general signage.
- Orientation: Landscape, portrait, or another required display characteristic.
- Sequence: A two-digit or other consistent number when several similar devices exist.
| Recommendation: Include only information that helps administrators distinguish and support the device. Avoid names that become excessively long. |
Build the Convention
Use a Consistent Separator
A hyphen-separated pattern is easy to scan and avoids spaces that can create inconsistent exports or integration behavior.
Recommended pattern: location-building-floor-area-function-orientation-sequence
| Example | Interpretation |
| houston-mainstreet-01-lobby-menuboard-portrait-01 | Houston, Main Street building, first floor lobby, portrait menu board, device 01 |
| nyc-midtown-12-reception-welcome-landscape-02 | New York City, Midtown, twelfth-floor reception, landscape welcome screen, device 02 |
| london-hq-03-east-wayfinding-landscape-01 | London headquarters, third floor east area, landscape wayfinding device 01 |
| No spaces: The examples intentionally use no spaces. Choose one separator and apply it consistently. |
Apply the Name
During Registration
1. Capture the device registration code.
2. Open the Appspace device-registration workflow.
3. Enter the approved device name.
4. Assign the correct location and settings.
5. Complete registration.
After Registration
1. Open Devices.
2. Search for the current device name or identifier.
3. Open the device details.
4. Edit the name.
5. Confirm the location, tags, and device group still match the naming components.
6. Save the change.
Maintain the Convention
Governance Checklist
- Document abbreviations: Publish an approved list for countries, cities, buildings, floors, areas, and functions.
- Reserve sequence numbers: Avoid reusing a number while an old device record remains active.
- Rename after moves: Update the name and location when a device moves.
- Review reports: Look for duplicates, missing components, and inconsistent separators.
- Keep hardware data elsewhere: Do not overload the device name with serial numbers or sensitive information when dedicated fields exist.