Extended User Rights: Restrict Creation and Editing of Location Types in the Explorer
Feature Request Summary:
ConnectMaster should let administrators set, through Extended User Rights, which location types each user or role can create in the Explorer and which location types they can edit, in both the Desktop and the Web application.
Functional Area / Module:
Explorer / User Administration (Extended User Rights)
Description/Use Cases:
Today, Extended User Rights cannot control permissions per location type. A user who is allowed to create or edit locations can do so for every location type. We would like two improvements:
Restrict creation by location type: As an administrator, I want to set which location types (e.g. Site, Building, Floor, Room, Shaft, Manhole) a user or role is allowed to create in the Explorer. When the user right-clicks to create a new location, only the permitted types should be offered. This should work the same way in the Desktop and the Web application.
Restrict editing by location type: As an administrator, I want to set which location types a user or role can edit. For example, a field or attribute should be able to edit Rooms and Racks but not Sites or Buildings, which only the planning team maintains. Location types without edit permission should be shown read-only to that user. These settings should be part of the existing Extended User Rights configuration so they can be managed per user or per role/group.
Business impact of limitation or missing of the feature:
Without per-type control, we have to grant broad create/edit rights or none at all. This raises the risk of users creating locations of the wrong type or changing locations that are not theirs to maintain, which hurts data quality and consistency in the network documentation. Finer permissions would protect key infrastructure data, keep responsibilities clearly separated between teams, and cut the time spent fixing incorrect entries.
Other necessary information or resources:
If needed, we can share examples.
-
Hello Netcon,
assume Site, Building, Floor, Room are individual levels in the location system.
They can be granted already today using “Locations: extended user rights”.For different types inside the same location level your idea is very good. We support this.
0 -
Hello Björn, good morning.
Thanks for your reply. To clarify: Site, Building, Floor and Room are location types in our location system, not fixed levels of the hierarchy. So one level can hold locations of very different types.
Here’s a real example from our setup. At level 4 of the location hierarchy we have two groups:
Outside plant → Manholes, Poles, Slacks → Team A (field / outside plant)
Facilities → Buildings, Datacenters, POPs → Team B (facilities / infrastructure)
Each group is managed by a different team, but both sit at the same level of the hierarchy.
Current limitation
Responsibility can’t be defined by location types. Both types are at the same level and often under the same parent, so both groups can edit every location created in the system.
Product idea
Allow ConnectMaster to define responsibility by location type. For example:
Link a team or user group to one or more location types (e.g. Team A → Manhole, Pole, Slack).
Apply that link to permissions, so each team works mainly with its own location types.Benefits
It matches how operators are organized in practice (outside plant vs. facilities).
Fewer edits to locations outside a team’s area.
It scales easily as new location types are added.0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
2 kommentarer