-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Supportal] Allow full visibility into #admins room chats and show in LHN #50626
Comments
Triggered auto assignment to @mallenexpensify ( |
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@mallenexpensify Huh... This is 4 days overdue. Who can take care of this? |
Looks like we're awaiting an internal engineer. Not sure what I can/should do here. |
@mallenexpensify Huh... This is 4 days overdue. Who can take care of this? |
Kinda/sorta waiting on this too |
@mallenexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too... |
They can't be seen because of this line here https://github.com/Expensify/Auth/blob/e92662e740063086376c2dc0a7a1d49bd43fc5ee/auth/command/OpenApp.cpp#L135 which seems intentional based on https://github.com/Expensify/Auth/pull/10366 and https://github.com/Expensify/Expensify/issues/380658 Is there not a privacy and security issue around showing the |
Thanks for 👀 @marcaaron
From the high level, would/should the owner of a workspace be able to see all #admin channel? I would think so. I do remember there being discussions a while back about which reports others would allowed to view. I'm guessing we wouldn't Slack employees to easily view details from our #directors channel in Slack. |
The owner of the workspace should see the admin channel because they would be an admin too.
Why did we redact it in the first place? I can't think of any reason why we need this from a support perspective. But maybe not understanding why we want this 😄 |
@stephanieelliott , why do we want employees to be able to supportal into #admin rooms? |
@mallenexpensify Huh... This is 4 days overdue. Who can take care of this? |
I don't think we intentionally redacted the #admins room, however it probably was an unintended consequence of one of those PRs to redact chats. But CAM, SRAM and Guides are all in their assigned customers #admins rooms already, I don't think there is any expectation of privacy there. The #admins room is where we send most of our account management comms. And most importantly it's where we display the workspace audit trails in ND, which we do need for troubleshooting. Opening up Supportal access allows anyone (not just the assigned Guide/AM) to view the conversation history and workspace logs. This was recently discussed as part of a pre-design here where we agreed we should make the #admins room visible in its entirety. |
This one is now just waiting on an Auth deploy. |
I'm back from OOO on Nov 14th, not assigning another BZ cuz it doesn't BZ-related actions here. Will review once back. |
@mallenexpensify, @marcaaron Eep! 4 days overdue now. Issues have feelings too... |
@mallenexpensify, @marcaaron 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
I think we can close this out now. |
Version Number:
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): [email protected]
Logs: LOGS
Expensify/Expensify Issue URL: N/A
Issue reported by: @stephanieelliott
Slack conversation: https://expensify.slack.com/archives/C07NZ8B1VTQ/p1728500635598069
Action Performed:
Expected Result:
#admins
rooms should show in LHNActual Result:
#admins
room does not show in LHNWorkaround:
None
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
MissingAdminRoom.mp4
The text was updated successfully, but these errors were encountered: