Snipe-it: [Feature Request] Departmentalise asset permissions/access

[kekkers23]

• Snipe-IT Version 4.7.4 (In process of upgrading to latest)
• OS: Ubuntu 18.04
• Web Server: Apache2
• PHP Version 7.2.19

Is your feature request related to a problem? Please describe.
We have several thousand assets which need to be managed both locally and globally. For example 10 locations across the world. With Full Multiple Companies Support we are able to lock down assets to each company (or department in our case) however some people need access to more than one companies' assets, these people should not have Super Admin however which is the only current way of allowing this without multiple accounts.

For example, if we had to move an asset to another region, or to an event or for simply managing stock globally this is not possible and severely limits our process flow to the point of this being a blocker in our application.

Describe the solution you'd like
Allow a person to be assigned to multiple companies at a time or given access to manage multiple companies assets granularly e.g. Person A can manage Companies A/B/C whereas Person B can manage Companies D/C.

Describe alternatives you've considered
Allow admins to have intercompany access
Allow a checkbox where a user can be given access to all companies, not as granular but would suffice in the medium term
Allow departments to be assigned to assets and manage access this way

Additional context
We are moving a lot of legacy systems into SnipeIT where this limitation would seriously hinder our deployment and manageability. Right now we are still deploying this solution however we will need to give certain people Super Admin in order to manage this and create fewer companies with more locations, this does mean that if an asset is checked out to a trade show, for example, it relies on trust that it is checked back to the correct location, whereas with companies there is no room for error in that regard.

[CubicrootXYZ]

Would appreciate that too

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[kekkers23]

Still an ongoing request, this functionality is fundamental in order to deploy this in production and to make proper use of permissions.

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[viclou]

+1 FD12848

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[kekkers23]

Still relevant and a blocker in global deployment.

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[kekkers23]

Still relevant and a blocker in global deployment.

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[kekkers23]

Update: Running latest v4.9.0, same request exists.

[kekkers23]

@snipe Apologies for the ping, any thoughts on this, it seems that this request is fairly common on a number of feature requests?

[netman63]

Would love to hear back regarding any options for this as well. We're a school district but have very similar situations in which we have multiple locations assigned to multiple people but we can't figure a way to give proper access to users without something like this implemented.

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[kekkers23]

Update: Running latest, same request exists.

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[kekkers23]

@snipe Any comments on this, would love to have this on the v5 release.

[pierinz]

+1
The "Company"/"Department" fields should be on Models and Categories too.

[viclou]

+1 FD 16382

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[kekkers23]

Still relevant ++

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!