Issue 7138 - write-protection on document-level
Summary: write-protection on document-level
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: rfe_eval_ok
Depends on:
Blocks:
 
Reported: 2002-08-19 22:04 UTC by lars
Modified: 2013-02-07 22:36 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description lars 2002-08-19 22:04:09 UTC 
when a file is write-protected, objects like charts can't be selected, so they 
can't be moved or edited.

The sense behind that must have been that when a file is write-protected, it 
can't be written to and one would only want to write when one has changed sth.; 
so the change-possibilty is disabled.


But the write-protection is on the OS level, so OOo looks somewhere where "it 
shouldn't". Write-protection should be implemented on the document level. So a 
user can set a write-protected flag and it might only be passed by a password 
to be entered. That would be similar to Adobes PDF way.


The next step is to enable the user to set a document-completed flag, so when a 
user opens the document, only a "reader" part of the OOo app. opens.

See issue 7137 Seperate content creation and content viewing.


this issue is in the ring of issues concerning this matter:
issue 7137 'Seperate content creation and content viewing', issue 7138 'write-
protection on document-level', issue 6889 'pdf creation posible with OOo ?'
Comment 1 thorsten.martens 2002-08-20 09:45:53 UTC 
TM->FT: Please have a look, thanks !
Comment 2 lohmaier 2002-08-22 00:13:20 UTC 
There is an option to protect the document from changes when using the
function Edit|Changes|protect changes
You are then promted to enter a password. Other users may change the
document, the changes are logged but can be just turned off (eg not
displayed as such).
For the creator it is easy to accept or reject these changes (after
unprotecting the doument using the password)

This doesn't 'protect' the document as eg creating a pdf would, but
when you need protection in this context, why not just create a pdf
and distribute the pdf instead of the sxw?
The user might copy&paste a protected file into a new one and the
change the contents, so I don't really see a need for a protection
that doesn't allow any changes (but I'm not a developer, just an user)
Comment 3 falko.tesch 2003-10-08 13:58:21 UTC 
We need more differientiated protection of documents.
This should be part of the issue Group Working/Collaboration
Comment 4 falko.tesch 2003-10-08 13:58:42 UTC 
.
Comment 5 bettina.haberer 2010-05-21 15:05:58 UTC 
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".