My feedback

1 result found

1. Prevent accidental changes by locking a fiscal period

   232 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   18 comments  ·  Feature Request  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Alexey Pakseykin supported this idea  ·  Sep 19, 2016
   An error occurred while saving the comment
   Alexey Pakseykin commented  ·  Sep 19, 2016  ·  Edit…  ·  Delete…

   Mistakenly modifying entry in the past is the most common source of problem for me (if not the single one). As previously said, years of data to review drains a lot of time due to a mistake which is very easy to make.

   I don't find password protection necessary. The feature is primarily needed as protection from mistakes rather than protection from unauthorized modification. Consider the simplest implementation without password first - it will immediately save time for many users.

   Adding password should be a separate feature (because it goes far beyond - simple password will only add false sense of protection from unauthorized modifications as users have direct access to data files).

   Save Submitting...