An organization is able to manage its own set of gateways. Please note that this feature might be unavailable when the organization is configured without gateway support.
That a gateway belongs to a given organization does not mean that the usage of a gateway is limited to the organization. Every node in the whole network will be able to communicate using the gateway. The organization will be responsible however for managing the gateway details (e.g. name, location) and will be able to see its statistics.
Gateway statistics are based on the aggregated values sent by the gateway / packet-forwarder. In case no statistics are visible, it could mean that the gateway is incorrectly configured.
When assigning a gateway-profile to a gateway, LoRa Server will send a configuration update to the gateway when its configuration is out-of-date. Gateway-profiles can be configured by clicking on Network servers in the navbar. Note that when a gateway-profile is assigned to a gateway, you must also configure the LoRa Gateway Bridge configuration in order to handle configuration updates.
For gateways implementing the v2 reference design which support geolocation capabilities, it is possible to configure one or multiple boards. This allows you to configure the FPGA ID and fine-timestamp AES decryption key per board.
When the fine-timestamp AES decryption key is configured, LoRa Server will automatically decrypt the fine-timestamp once it receives an uplink frame from this gateway.