starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-03-13 05:45:48 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add user/group changelogs #10415

New Issue
Open
opened 2025-12-29 21:31:10 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:31:10 +01:00
Owner
Copy Link

Originally created by @mcao2 on GitHub (Oct 29, 2024).

NetBox version

v3.7.8

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

Before NetBox v3.6.0, user/group management is done using django's admin page and we have log entries for related object changes. But starting from v3.6.0 (https://github.com/netbox-community/netbox/pull/12877), NetBox now manage user/group in its Admin tab, and django admin seems completely removed in v4.0. I propose we add similar change logging feature for user/group changes so that we can better understand/audit the activities.

Use case

When there's multiple admins or users with user/group change permissions, it becomes unmanageable to ask who made that change and when that change happened. If we can have a similar Admin LogEntry in NetBox then it would greatly improve the visibility for admins.

Database changes

No response

External dependencies

No response

Originally created by @mcao2 on GitHub (Oct 29, 2024). ### NetBox version v3.7.8 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality Before NetBox v3.6.0, user/group management is done using django's admin page and we have log entries for related object changes. But starting from v3.6.0 (https://github.com/netbox-community/netbox/pull/12877), NetBox now manage user/group in its Admin tab, and django admin seems completely removed in v4.0. I propose we add similar change logging feature for user/group changes so that we can better understand/audit the activities. ### Use case When there's multiple admins or users with user/group change permissions, it becomes unmanageable to ask who made that change and when that change happened. If we can have a similar Admin LogEntry in NetBox then it would greatly improve the visibility for admins. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurecomplexity: mediumnetboxstatus: backlog labels 2025-12-29 21:31:10 +01:00
adam commented 2025-12-29 21:31:10 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Oct 30, 2024):

I think an audit log might be a better place.. That log could also include login/logout/loginattempts...

@PieterL75 commented on GitHub (Oct 30, 2024): I think an audit log might be a better place.. That log could also include login/logout/loginattempts...
adam commented 2025-12-29 21:31:11 +01:00
Author
Owner
Copy Link

@mcao2 commented on GitHub (Oct 30, 2024):

I think an audit log might be a better place.. That log could also include login/logout/loginattempts...

I completely agree, adjusted the issue title to not suggest where the changelog should exists

@mcao2 commented on GitHub (Oct 30, 2024): > I think an audit log might be a better place.. That log could also include login/logout/loginattempts... I completely agree, adjusted the issue title to not suggest where the changelog should exists
adam commented 2025-12-29 21:31:11 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Oct 31, 2024):

Another possibility might be to add the ChangeLoggingMixin to the User and Group models, which are already subclassed from AbstractUser and can support additional customizations.

A separate audit log is a good idea, but we already have pervasive change logging for many other models that we might as well extend to users.

@bctiemann commented on GitHub (Oct 31, 2024): Another possibility might be to add the `ChangeLoggingMixin` to the `User` and `Group` models, which are already subclassed from `AbstractUser` and can support additional customizations. A separate audit log is a good idea, but we already have pervasive change logging for many other models that we might as well extend to users.
adam commented 2025-12-29 21:31:11 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Nov 1, 2024):

This came up during the isp working group. The idea of a separate audit log was mentioned to track admin related changes with a bit more detail (ips used when making change) and also to be able to limit who can see the audit logs

@ITJamie commented on GitHub (Nov 1, 2024): This came up during the isp working group. The idea of a separate audit log was mentioned to track admin related changes with a bit more detail (ips used when making change) and also to be able to limit who can see the audit logs
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: medium netbox status: backlog type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10415
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?