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

Administration > Workspace is visible for usual users #27081

Closed
krenuser opened this issue Oct 16, 2022 · 12 comments · Fixed by #27188
Closed

Administration > Workspace is visible for usual users #27081

krenuser opened this issue Oct 16, 2022 · 12 comments · Fixed by #27188
Labels
contrib: good first issue Issues that you can solve to start contributing :) hacktoberfest type: bug ui/ux

Comments

@krenuser
Copy link

krenuser commented Oct 16, 2022

Description:

Administration > Workspace menu item is visible and available for usual users, though contents of this page are not loading:

image

Steps to reproduce:

  1. Login as usual user on RC 5.2.0
  2. Open Administration > Workspace menu item

Expected behavior:

Neither Administration, nor Administration > Workspace item should not be visible to usual users.

Actual behavior:

Menu item is visible for usual users, contents of opened page aren't loading.

Server Setup Information:

  • Version of Rocket.Chat Server: 5.2.0
  • Operating System: Linux Ubuntu 20.04
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v14.19.3
  • MongoDB Version: 5.0.13 / wiredTiger

Client Setup Information

  • Desktop App or Browser Version: Desktop 3.8.12 / Browser
  • Operating System: Windows 10

Additional context

none

Relevant logs:

No relevant logs neither in DevTools, nor on server side.

@dudanogueira
Copy link
Contributor

Hi! I was not able to reproduce this issue =\

Can you get the infos from the user you created? When you edit a user, you can get that json from the network tab in browser developer tools, like so:

image

@IKrendelev
Copy link

image
Found out that this behavior was caused by "Omnichannel settings" menu availability, due to livechat-manager role that user actually has. This item makes [ ⁞ ] ("Administration") button visible along with "Workspace" item (that shouldn't be visible).

@dudanogueira
Copy link
Contributor

Yep, that's true.

That's a good first issue for our #hacktoberfest :)

@dudanogueira dudanogueira added bug ui/ux contrib: good first issue Issues that you can solve to start contributing :) hacktoberfest labels Oct 17, 2022
@nishant23122000
Copy link
Contributor

@krenuser are you working on it?

@krenuser
Copy link
Author

krenuser commented Oct 18, 2022

@krenuser are you working on it?

No, I haven't set up fully functional dev environment for that yet (I have a bit different dev specialization).
Maybe, some of my future bug reports...

@nishant23122000
Copy link
Contributor

ok, can I work on that?

@krenuser
Copy link
Author

krenuser commented Oct 18, 2022

ok, can I work on that?

Don't have any objections.

@mani-rsg
Copy link
Contributor

Hi @nishant23122000 , is this issue being worked on? if not I could work on it, please confirm

@ankar84
Copy link

ankar84 commented Oct 24, 2022

image Found out that this behavior was caused by "Omnichannel settings" menu availability, due to livechat-manager role that user actually has. This item makes [ ⁞ ] ("Administration") button visible along with "Workspace" item (that shouldn't be visible).

Regular user with only user role don't have any administrations menu.
Guess that menu comes from bot or one of livechat roles, which is bug definitely.

@tassoevan tassoevan added type: bug and removed bug labels Oct 26, 2022
@rksingh2001
Copy link

Can I take up this issue?

@Barrylimarti
Copy link

Hey @dudanogueira, the livechat manager role should offer the omnichannel option in the administration menu and not the workspace option right? Doing this is failing the unit test cases created for the AdministrationModelList as the test cases are searching for workspace option always and thus, I think the test case needs to be modified in order to solve this issue.

@dudanogueira
Copy link
Contributor

hi @Barrylimarti! you are right!.

However, before that, there are failing tests that I am not sure it is related:
https://github.com/RocketChat/Rocket.Chat/actions/runs/3393376349/jobs/5640641602#step:42:6

I have pinged our good friend @filipemarins that can help us here :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contrib: good first issue Issues that you can solve to start contributing :) hacktoberfest type: bug ui/ux
Projects
None yet
9 participants