starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Different Default Dashboards Depending On User Groups #11748

New Issue
Closed
opened 2025-12-29 21:49:24 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:49:24 +01:00
Owner
Copy Link

Originally created by @mr1716 on GitHub (Oct 19, 2025).

NetBox version

v4.4.4

Feature type

New functionality

Proposed functionality

This would provide the optional settings to have the default dashboard layout to be different for users depending on their group membership or some other user defined feature.

Use case

Not every users will have the same need in regards to Dashboard Widget configuration and there should to be a way to have admins have a different default dashboard than users.

With so many data models and different teams having and using different views of those data models, it would be helpful for users to have a more tailored Dashboard view for their use. For example, normal users won’t care about how many users have logged in, but for admins, having that information as a default widget for the team may be really helpful.

Database changes

No response

External dependencies

No response

Originally created by @mr1716 on GitHub (Oct 19, 2025). ### NetBox version v4.4.4 ### Feature type New functionality ### Proposed functionality This would provide the optional settings to have the default dashboard layout to be different for users depending on their group membership or some other user defined feature. ### Use case Not every users will have the same need in regards to Dashboard Widget configuration and there should to be a way to have admins have a different default dashboard than users. With so many data models and different teams having and using different views of those data models, it would be helpful for users to have a more tailored Dashboard view for their use. For example, normal users won’t care about how many users have logged in, but for admins, having that information as a default widget for the team may be really helpful. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:49:24 +01:00
adam closed this issue 2025-12-29 21:49:25 +01:00
adam commented 2025-12-29 21:49:25 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Oct 23, 2025):

After conferring with other maintainers we decided not to pursue this due to the complexity involved. This could potentially be done in a plugin.

@arthanson commented on GitHub (Oct 23, 2025): After conferring with other maintainers we decided not to pursue this due to the complexity involved. This could potentially be done in a plugin.
adam commented 2025-12-29 21:49:25 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Oct 23, 2025):

@arthanson thanks for the honesty and transparency. Would’ve been a great feature to have. Hope that it’ll be something that will be supported by default down the road in the far future.

@mr1716 commented on GitHub (Oct 23, 2025): @arthanson thanks for the honesty and transparency. Would’ve been a great feature to have. Hope that it’ll be something that will be supported by default down the road in the far future.
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 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#11748
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?