+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-1489

Password & 'screen'/change lock ability in MC

action_vote_minus_faded.png
5
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Need:
Ability to lock and password protect changes of certain areas in Multicharts to support following use cases.

Use case 1 - Protect from unauthorized access
It is more common and popular that trades run software in VPS, Virtual Private Server in the 'cloud' to get high reliability and availability, e.g. redundancy of internet.
To protect the trading platform from unauthorized people e.g. datacentre maintenance
staff, it would be of great benefit if MC can be locked and protected when it is left (like windows lock screen).

Use case 2 - Segregation of duty
MC users want to allocate their desktops and workspaces for different use, for example; different environment and different accounts, different strategies.
a) a workspace for live automatic trading of strategy using certain account and
configuration, b) a workspace for research and testing with different account
and configuration, c) etc.
The ability to 'lock' and password protect a workspace helps reducing the risk of unwanted changes by mistake. Would solve use case 1.

Use case 3 - Segregation of duty - shared environment.
Small trading teams may co-work on strategies and share MC environment running strategies over several accounts. The ability to lock and password protect trading and configuration settings on a level that protect changes by e.g. mistake that impact different accounts. E.g. could potentially be achieved by functionality addressing use case 2 or perhaps on lower level if trading can be done on other levels than charts in the future. E.g. via the scanner.

Regards,

Steps to reproduce this issue

New features

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Not Reviewed
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates