Present more visual cues in the GUI for options that are only available when logged in

[jennaj]

Two common use cases that trip users up. The issue could be considered one project, or two distinct "papercuts" -- but putting them together since if addressed, the "cues" decided upon should be consistent with each other.

1. Options are completely missing from listings when not logged in. Causes confusion. Might be better to include them, but have the text be faded out. A hover-over popup stating "Register or Log in to use this function", ideally with a link to the login/register form. Example in this Q&A: https://help.galaxyproject.org/t/extract-workflow-from-history-option-is-invisible/4599

2. Tools that require a login to execute have a "submit" button that appears as if active, and is usable. The job will then later fail, with an error message about the need to login, but that isn't always understood. Consider fading out the submit button for this case, and add in a similar hover-popup message "Register or Log in to use this tool", also ideally with a link to login/register form.

If a link to register/login is added in -- please make sure the user doesn't lose their work! Going to that form from the masthead preserves the current work -- this should do the same.

[mvdbeek]

2. Tools that require a login to execute have a "submit" button that appears as if active, and is usable. The job will then later fail, with an error message about the need to login, but that isn't always understood. Consider fading out the submit button for this case, and add in a similar hover-popup message "Register or Log in to use this tool", also ideally with a link to login/register form.

That is usually implemented within the tools command section or within the dynamic job rules, I don't think this is possible for existing tools. Galaxy itself doesn't have a notion of which tools require login. Can you create a separate issue for this ? It should be possible to define a better mechanism for requiring login on the side of the Galaxy administrator which could then indeed prevent submission.

[hexylena]

from an EU support thread recently.

your screenshot shows that you're not logged in!
FTP space is associated with specific accounts, of course.