Support multiple Owners per object #709

New Issue

MrUnknownDE · 2026-04-05T17:16:13+02:00

MrUnknownDE commented

2026-04-05 17:16:13 +02:00

Originally created by @loubladi on 12/18/2025

NetBox version

v4.5.0-beta1

Feature type

Data model extension

Proposed functionality

NetBox v4.5.0 allows assigning only a single Owner to an object via the owner field.

This proposal extends the Ownership model to allow multiple Owners to be associated with a single object, enabling a many-to-many relationship between Owners and objects.

Use case

In our NetBox deployment, permissions are enforced at the department level. Each department must be prevented from modifying servers owned or maintained by other departments, as several automation workflows depend on this separation and unintended changes could cause service disruption.

At the same time, there are valid scenarios where a single server is owned and/or maintained by multiple departments. Examples include shared infrastructure, handover periods, or split operational responsibilities.

Currently, we model this using department-specific tags, which are then referenced in permission rules. While this approach allows assigning permissions to multiple departments, it is a workaround rather than a proper ownership model.

Native support for multiple Owners per object would eliminate the need to overload tags for access control, while still allowing permissions to be granted to any number of departments in a consistent and structured way.

Database changes

No response

External dependencies

No response

*Originally created by @loubladi on 12/18/2025* ### NetBox version v4.5.0-beta1 ### Feature type Data model extension ### Proposed functionality NetBox v4.5.0 allows assigning only a single Owner to an object via the owner field. This proposal extends the Ownership model to allow multiple Owners to be associated with a single object, enabling a many-to-many relationship between Owners and objects. ### Use case In our NetBox deployment, permissions are enforced at the department level. Each department must be prevented from modifying servers owned or maintained by other departments, as several automation workflows depend on this separation and unintended changes could cause service disruption. At the same time, there are valid scenarios where a single server is owned and/or maintained by multiple departments. Examples include shared infrastructure, handover periods, or split operational responsibilities. Currently, we model this using department-specific tags, which are then referenced in permission rules. While this approach allows assigning permissions to multiple departments, it is a workaround rather than a proper ownership model. Native support for multiple Owners per object would eliminate the need to overload tags for access control, while still allowing permissions to be granted to any number of departments in a consistent and structured way. ### Database changes _No response_ ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-05 17:16:13 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#709