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

Admin permissions not granting "Reports" view #6536

Closed
andrefecto opened this issue Dec 21, 2018 · 2 comments
Closed

Admin permissions not granting "Reports" view #6536

andrefecto opened this issue Dec 21, 2018 · 2 comments
Labels

Comments

@andrefecto
Copy link

andrefecto commented Dec 21, 2018

Please confirm you have done the following before posting your bug report:

Describe the bug
Granting the Admin permission level does not grant "Reports: View" permissions.

To Reproduce
Steps to reproduce the behavior:

  1. Create a test group and grant ONLY the "Admin" radio button.
  2. Log in with an account in this test group and try to view the "History" tab on any asset, it will should show nothing.
  3. Go back to the group permissions and explicitly grant the "Report: View" permissions.
  4. Log back in with the user and you should be able to see entries in the "History" tab of an asset.

Expected behavior
Expected is: Granting Admin level permissions gives everything except for the Super-Admin control panel.

Screenshots
Screenshot of the permissions needed to see anything in the "History" tab:
Screenshot of permissions needed to see Reports

Server (please complete the following information):

  • Snipe-IT Version: 4.6.4
  • OS: Windows Server 2012 R2
  • Web Server: IIS
  • PHP Version: 7.2.9

Error Messages

  • There are no error messages, just unable to see anything in the "History" tab without "Reports: View" permission.

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.

@stale
Copy link

stale bot commented Feb 19, 2019

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!

@stale stale bot added the stale label Feb 19, 2019
@stale
Copy link

stale bot commented Feb 26, 2019

This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.

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

1 participant