Product Ideas Portal

Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.

The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.

Want to stay anonymous? No problem, you can still share your ideas with us. You can also create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.

To learn more about how an idea becomes a feature, check out this infographic.


41 Vote

Invited User to a Command Shell session can collaborate with initial User

As an Internal Admin I'd like to invite another internal or external User to my existing Command Shell session so we see the same in- and output on the screen in order to be able to collaborate.

Today, every invited User to a Command Shell session gets his own distinct Command Shell which is not the goal of users who are inviting other User to sessions - they want to collaborate within an SSH session as they can within a RDP session. The behaviour needs to be consistent through all session types.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 19 2017
  • Planned
Secure Remote Access / Privileged Remote Access
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 Nov, 2017 06:21pm

    We need this ability as well. We just moved away from a different solution to BOMGAR, and now discovered this limitation upon implementation. This is inconvenient.

    ×

    Attachments Open full size

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    13 Nov, 2017 02:03pm

    We also want this

    ×

    Attachments Open full size

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    19 Oct, 2017 02:10pm

    forgot to say that is important to ERS as well.

    ×

    Attachments Open full size

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    19 Oct, 2017 01:17pm

    The current behavior where each member of the session gets their own shell is inconsistent with the behavior of all other screen sharing session types. While shell jump is technically not screen sharing, the user experience expectation is that sharing a session would share the existing shell(s). 

    ×

    Attachments Open full size

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    19 Oct, 2017 09:27am

    Today we have a list of customers and prospects who want this:


    ×

    Attachments Open full size

Related ideas