Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Company Support - locations not tied to / limited to companies #2353

Closed
RobMSP opened this issue Jul 29, 2016 · 16 comments
Closed

Multiple Company Support - locations not tied to / limited to companies #2353

RobMSP opened this issue Jul 29, 2016 · 16 comments
Labels

Comments

@RobMSP
Copy link

RobMSP commented Jul 29, 2016

Expected Behavior (or desired behavior if a feature request)

When locations are created they are not assigned to companies, without this relationship information regarding multiple companies locations is visible between companies.

When an asset is edited or created it can be assigned to any location, but locations should be tied to a company.

A user for company A should not be able to edit an asset and assign it to a location belonging to company B.

A user for company A should not be able to see locations belonging to company B.

Actual Behavior

When a user is accessing the system in 'full multiple company support' mode enabled all locations are visible, including locations that have no relationship to the company their account is associated with.

When a asset is edited all locations are visible to all users, locations cannot specify a specific company.

Please provide answers to these questions before posting your bug report:

  • Version of Snipe-IT you're running
    v3.0-67-gf31637a
  • What OS and web server you're running Snipe-IT on
    Ubuntu 14.04 lts
  • What method you used to install Snipe-IT (install.sh, manual installation, docker, etc)
    install.sh
@RobMSP
Copy link
Author

RobMSP commented Aug 24, 2016

I would be very anxious and would be willing to pay a small reward via paypal for the completion of this feature request.

Basically I need to from a Company Screen assign access to 'locations'

So User at Company A could only see locations for Company A and not any other locations.

From my perspective it would be better if the Company then Tagged Locations as valid, this way locations could be reused across two or more companies but that is not a requirement.

Locations where 'locations' information is exposed to a user:

https://snipe/hardware/create
https://snipe/hardware/_/edit
https://snipe/admin/components/create
https://snipe/admin/components/_/edit
https://snipe/admin/consumables/create
https://snipe/admin/consumables/_/edit
https://snipe/admin/accessories/create
https://snipe/admin/accessories/_/edit

My only solution is to not permit the users form company A to have any edit or create permissions.

@ConvexSERV
Copy link

+1 For this feature as well!

@schmidiij
Copy link

+1 for this feature!

1 similar comment
@KroonCo
Copy link

KroonCo commented Dec 15, 2017

+1 for this feature!

@stale
Copy link

stale bot commented Feb 13, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

@stale stale bot added the stale label Feb 13, 2018
@stale stale bot closed this as completed Feb 20, 2018
@Hsherif90
Copy link

+1 to this feature!

@Knightrain0
Copy link

+1 for this feature!

@namarie23
Copy link

+1 to this feature.

@MalteKiefer
Copy link

+1

@Omidoshegy
Copy link

+1 Please 🙏

@Saad-Samba
Copy link

+1

@khrishino
Copy link

+1 please

@catalunyati
Copy link

Absolutely, +1

@biernattmarcin
Copy link

biernattmarcin commented Aug 24, 2024

+1. Needed functionality

@dreamer2038
Copy link

+1 please

@Steve-M-C
Copy link

This would be very useful, since at present, although you can restrict a user to only being able to view/edit assets at their assigned company, they are still able to see all the locations on the system - so could accidentally assign assets to the wrong locations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests