S
seven7
The current password protection architecture seems very flat and designed for
a more personal environment rather than an office or administrative
environment where data needs to be shared with protection on a page level,
but with administrative rights available for specific people.
First Problem: Password protection needs to be able to be applied all the
way down to a page level, not just a section or folder level.
Second Problem: Because there can be many passwords in a OneNote file, there
needs to be a) A hint that can be applied to a specific protected
document/area, and, b) An administrative group that one or more people can
belong to that can use a SINGLE password to open any protected file and/or to
allow this administrator type person to search every section of OneNote
without having to unlock individual sections/folders/pages.
Example 1: Joe and Jane are IT administrators at XYZ company. They need to
search for a key document in OneNote. That document could be anywhere - they
don't know...so Joe enters his administrative password to open search access
to every area in all sections. Jane later needs to find a specific document
for a manager, but because there are 20 unique password protected sections,
she just enters her administrative password (different admin password from
Joe's) and *presto* she can search for that elusive document, and send the
link to the requestor (it's up to the requestor to know their specific
password for that section).
Example 2: Student John is taking entering notes into OneNote and plans to
share these notes with his study group, but decides that he is not going to
share several pages in this folder with his study friends. John than simply
adds a unique password to A SINGLE PAGE of this folder. Now John can be
assured that he can share this folder with his study friends without them
accessing one or more private pages.
a more personal environment rather than an office or administrative
environment where data needs to be shared with protection on a page level,
but with administrative rights available for specific people.
First Problem: Password protection needs to be able to be applied all the
way down to a page level, not just a section or folder level.
Second Problem: Because there can be many passwords in a OneNote file, there
needs to be a) A hint that can be applied to a specific protected
document/area, and, b) An administrative group that one or more people can
belong to that can use a SINGLE password to open any protected file and/or to
allow this administrator type person to search every section of OneNote
without having to unlock individual sections/folders/pages.
Example 1: Joe and Jane are IT administrators at XYZ company. They need to
search for a key document in OneNote. That document could be anywhere - they
don't know...so Joe enters his administrative password to open search access
to every area in all sections. Jane later needs to find a specific document
for a manager, but because there are 20 unique password protected sections,
she just enters her administrative password (different admin password from
Joe's) and *presto* she can search for that elusive document, and send the
link to the requestor (it's up to the requestor to know their specific
password for that section).
Example 2: Student John is taking entering notes into OneNote and plans to
share these notes with his study group, but decides that he is not going to
share several pages in this folder with his study friends. John than simply
adds a unique password to A SINGLE PAGE of this folder. Now John can be
assured that he can share this folder with his study friends without them
accessing one or more private pages.