System Settings
System Settings is the identity page for your Tagnet instance. Here you configure the instance name, check server connectivity, and customize terminology. It is a tab of the System page, next to Policies, which decide how the application behaves.
Overview
System settings are global. They apply to the entire Tagnet instance and affect all users. All settings are optional.
From the System Settings page you can:
- Configure the instance name
- See the External URL that readers and emailed links use, and test that it is reachable
- Customize terminology (rename "Inventory" and "Inventory Item" labels)
Data lifecycle is managed under Policies, not here.
Permissions
| Permission | What It Allows |
|---|---|
| View Settings | See the current system settings |
| Admin | Edit settings |
Settings Categories
Identity
| Setting | Description |
|---|---|
| Instance name | A display name for this Tagnet installation (e.g., "Acme Production"). It tells one installation from another where several exist, so it appears in the emails Tagnet sends, as the instance_name variable available to email and message templates alongside organization_name, and Tagnet AI reads it when describing the installation. It does not appear in the app's own header; the organization name from your license does. First-run setup fills it with your license's customer name. |
| External URL | The address readers, invitation links, and password-reset emails use to reach Tagnet (e.g., https://tagnet.corp.local). Read-only on this page. |
The External URL comes from the server's hosting configuration rather than from this page. When HTTPS is enabled it is derived from the certificate name and port; otherwise it is the server's name and HTTP port. The label next to the address shows which. To use a different address, for example when readers reach the server through NAT or a load balancer, set External URL on the Tagnet Admin Console's Web Server Setup page. See Web Server Setup.
Click Test connection in the Identity section's header to verify the address is reachable. Tagnet performs a DNS lookup and health endpoint check, and shows the resolved IP address and connection status.
If an External URL was saved on this page in an earlier version of Tagnet and differs from the current address, a notice shows the old value. It is no longer used; set it in the Admin Console if devices should still use it.
Terminology
| Setting | Description | Default |
|---|---|---|
| Inventory label | Plural label for inventory collections | "Inventory" |
| Inventory item label | Singular label for individual tracked items | "Inventory Item" |
Customizing these labels changes how the concepts are displayed throughout the application. For example, a manufacturing company might use "WIP" and "WIP Item", while an IT department might use "Assets" and "Asset".
Change history
The bottom of the page shows when the settings were last updated and by whom. When settings are updated through Tagnet AI or the API, that source is shown alongside the user. Every change to these settings is recorded in Change History with its before and after values; the Change history link next to the caption opens the log filtered to system settings. The link appears for users with View Audit Logs.
Editing Settings
Click Edit settings to open the edit dialog. All fields are optional.
The organization name is not set here. It comes from the license customer name and appears on the login page, the About page, and exported spreadsheets; to change it, apply an updated license from Stratum Global. See License.
Data Retention
Automated data lifecycle is configured on the Policies tab of the System page, not on this tab. Each retention policy (raw events, scan events, workflow execution, movement-rule execution, operational rollups, inventory snapshots) has its own admin-controlled retention horizon and is enforced by the Retention background job on a nightly schedule. See the Policies reference for the full set of configurable policies and their defaults.
Initial Setup
First-run setup does not ask for these settings. When the wizard creates your first site it fills them in: the instance name from your license's customer name, and the default terminology. Change any of them here whenever you like. An installation that skipped the wizard shows the defaults until the first save. The organization name comes from your license.
Best Practices
- Check the External URL after enabling HTTPS: The address updates automatically when hosting changes. Use Test connection to confirm it is reachable, then redeploy readers so they receive it.
- Customize terminology to match your domain: Users adopt the system faster when it speaks their language.
- Tune retention policies for your workload: Raw event data accumulates quickly with active readers. Visit Policies and adjust each retention horizon to balance storage with audit needs.