-
Notifications
You must be signed in to change notification settings - Fork 3.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
Improve feedback for a read-only user #4648
Comments
Would a different color banner with a “Read Only” mention next to the NR logo work? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, if a user has read-only access to the editor, they may not know until they hit deploy - at which point they get a message saying they need to be logged in.
Aside from the fact this message is misleading (they are logged in... they just don't have permission to deploy), it would be better to have a clearer indication earlier that they do not have write access.
We added the ability to lock flows recently. One potential option would be for a read-only user to have the flows auto-locked. The downside is this prevents them from opening edit dialogs - something we deliberately chose to allow read-only users to do.
Maybe a notification in the header would be better.
The text was updated successfully, but these errors were encountered: