Project settings and policies
Manage project views, modules and data validation rules.
Last updated:
General settings
Project settings contains Project name, Description and Default coordinate system. The coordinate system is suggested during import and export. Project-specific local coordinate system provides Core system and Matrix (JSON) for local coordinates with a known transformation. Do not guess unknown transformation values; follow coordinate checks in Importing data.
- Open Project settings.
- Edit the name, description and coordinate system if needed.
- Select Save.
- Move the map to the desired opening position, then select Save current view under Initial view.
Use Remove to clear the saved opening view. Without one, the project opens to show all features.
Modules
Core and Shared site are always enabled. Addresses and buildings and Fiber can be enabled or disabled per project within the organisation's entitlement. Managing project modules requires the relevant administrative permission; available choices depend on project role and organisation scope.
- Open Modules in Project settings.
- Select which organisation-enabled modules to use in this project.
- Select Apply modules and confirm.
Disabling a module does not delete its records. Relevant tools and data are hidden and reappear when it is enabled again. An authorised administrator can inspect records through Show data from disabled modules (read-only) in Layers. This does not grant editing permission. Related records in a disabled module may block actions such as deleting or moving a shared site feature.
See Electrical infrastructure (Coming soon) for that module's availability.
Fiber project policies
Project policies in Fiber strand assignment includes these checks:
| Rule | What is checked |
|---|---|
| Unpositioned splice at a node with trays | Whether a splice position is recorded at a node containing trays. |
| ODF face → endpoint type | Whether the connection endpoint suits the ODF face. |
| Circuit purpose compatibility | Compatibility of the technical circuit purpose with assignment and endpoint information. |
| Circuit path is disconnected | Broken connections on a saved circuit path. |
| Circuit path deviation | Differences between the saved path and current connections. |
| Backup path cable diversity | Cables shared by primary and backup paths. |
| WDM channel compatibility | Compatibility of WDM channel choices along the path. |
| Underground cable without a route | Missing route relationship for an underground cable. |
Rules default to Closed. Information reports findings; Warning permits saving and reports the issue; Rejection blocks violations not covered by the baseline or a valid exception.
- As an authorised administrator, select Edit rules in Fiber strand assignment.
- Set New level under Project policies.
- For Rejection, choose Baseline mode. Baseline existing violations exempts current violations; Clean (empty baseline) requires no non-exempt violations to remain.
- Enter Reason and select Add levels to draft.
- Inspect the impact with Preview, then select Approve.
Use Validation report to inspect topology and other policy violations. Scan again evaluates current records; Download CSV downloads the report. Evaluate disabled rules as well also shows potential findings for disabled rules. Exceptions allows a reason and optional expiry date for specific records. An exception does not repair a physical connection; it defines an exemption in rule evaluation.
Other policy settings
Violation policy in Fiber strand assignment assesses assignment classes across connections. See Fiber assignment and reservation.
Change on the Policy row in Capacity opens Capacity policy, Partial coverage ratio (0–1) and Calculation purpose. This affects building targets and port calculations; it is separate from fiber validation rule levels. See Quantities and network occupancy.
Project workflows
Depending on your permissions, the base project's Project panel offers Members, Designs, Work packages, Field packages and Data sources. The relevant pages explain membership and area permissions, design approval, work packages, offline field work and reimporting.
