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

Extra TAG permission - Issue when user have no read access #8363

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

Originally created by @dboissat on GitHub (Jul 25, 2023).

NetBox version

v3.5.6

Python version

3.8

Steps to Reproduce

  1. Create an interface with Tags
  2. Create a User
  3. Create permissions where the user could edit an interface but without giving "Extra Tags" permissions (read, edit, delete)
  4. User edits the interface with the Tags.
  5. User saves the changes and the interface was edited.

Expected Behavior

The tags field doesn't appear in the interface of the user.
The user can't read, edit or delete them. So no change is expected on the Tags of the object.

Observed Behavior

The Tags field is visible in the edit interface but empty.
The Tags are removed from the interface/object when the user saves his changes.

Originally created by @dboissat on GitHub (Jul 25, 2023). ### NetBox version v3.5.6 ### Python version 3.8 ### Steps to Reproduce 1. Create an interface with Tags 2. Create a User 3. Create permissions where the user could edit an interface but without giving "Extra Tags" permissions (read, edit, delete) 4. User edits the interface with the Tags. 5. User saves the changes and the interface was edited. ### Expected Behavior The tags field doesn't appear in the interface of the user. The user can't read, edit or delete them. So no change is expected on the Tags of the object. ### Observed Behavior The Tags field is visible in the edit interface but empty. The Tags are removed from the interface/object when the user saves his changes.
adam closed this issue 2025-12-29 20:35:49 +01:00
adam commented 2025-12-29 20:35:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 25, 2023):

This is expected behavior. The user is editing the interface, not the tags.

@jeremystretch commented on GitHub (Jul 25, 2023): This is expected behavior. The user is editing the interface, not the tags.
adam commented 2025-12-29 20:35:50 +01:00
Author
Owner
Copy Link

@dboissat commented on GitHub (Jul 25, 2023):

So, It's expected behavior that a user could remove all Tags of an object only due because he doesn't have permission to read these Tags.

Strange behavior design.
Some of my users need to could edit the interfaces but the Tags aren't pertinent information for them. In our case, Tags are specific information for our engineering team.

So I will give my users the "read" Tags permission to avoid my users removing them when they edit objects.

@dboissat commented on GitHub (Jul 25, 2023): So, It's expected behavior that a user could remove all Tags of an object only due because he doesn't have permission to read these Tags. Strange behavior design. Some of my users need to could edit the interfaces but the Tags aren't pertinent information for them. In our case, Tags are specific information for our engineering team. So I will give my users the "read" Tags permission to avoid my users removing them when they edit objects.
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
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#8363
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?