search

matsuoka-edi / redmine-dmsf

Automatically exported from code.google.com/p/redmine-dmsf
0 stars 0 forks source link

Assign users and permissions to folders and documents. #27

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It would be very helpfull if you can assign users with permissions to your 
folders, so only the selected users receive the notification emails and only 
selected users could aprove or upload a new revision or delete them.

Original issue reported on code.google.com by AriE...@gmail.com on 17 May 2011 at 1:52

GoogleCodeExporter commented 9 years ago 
Rights and permissions are done Redmine way, so per project. Will consider it 
in following releases. 

May be it would be better to create separate projects and subprojects to handle 
this.

Original comment by vit.jo...@gmail.com on 17 May 2011 at 1:57

GoogleCodeExporter commented 9 years ago 
Can you add a per role configuration for each folder?
I.e. add an option to define for each folder, for each role, if they can
- See the folder
- Add a document in the folder
- Edit a document in the folder
- Delete a document in the folder

This way, I could for instance create a "accounting" folder with the invoices 
related to the project, visible only to the project manager role, while the 
"specifications folder" could be visible to the "project manager", "user" and 
"programmer" roles.

That would be very useful

Original comment by da...@aeroinsys.com on 9 Jun 2011 at 7:09

GoogleCodeExporter commented 9 years ago 
As I stated in my previous comment. For your needs it would be better to create 
specific subprojects for this. Because subprojects don't inherit members and 
rights from parent projects, your desired access control is possible (eg. 
Project A >> Subproject Accounting)

Original comment by vit.jo...@gmail.com on 9 Jun 2011 at 7:26

GoogleCodeExporter commented 9 years ago 
I know that I can do this, but it requires a lot of different subprojects for 
every project if I want to control access, for the different roles, and it is 
not convenient.

Original comment by da...@aeroinsys.com on 9 Jun 2011 at 2:53

GoogleCodeExporter commented 9 years ago 
To further comment, since the documents of a subproject are not visible at the 
parent project level, it means that if I create subproject, a role, let say the 
project manager, cannot see all the documents at a glance.
He needs to go in each sub project.
And navigating between these different subprojects is not convenient.
It would be a lot better if there was one single entry point for the project, 
but the possibility to hide/show the documents each role is allowed to see.

Original comment by da...@aeroinsys.com on 9 Jun 2011 at 2:58

GoogleCodeExporter commented 9 years ago 
the main idea for this request was this situation. As i told you in another 
request i'm certifying ISO 9001. The norm ask for a place to upload documents 
as a repository for the participants of the project could access if they have a 
doubt. this documents are related to process of quality. So the norm ask for 
these documents that they have to be versioned, they have to be aproved (this 
things the plugin its great) and they have to be distinguished between 4 
differents categories. Documents in development, current documents, defeated 
documents and waiting for aproval. The thing is that every folder (category) 
have to have different permissions as comment 2 said. i hope this comment add 
some details for my original request.

Original comment by AriE...@gmail.com on 9 Jun 2011 at 5:40

GoogleCodeExporter commented 9 years ago 
OK. Will add this feature in further releases

Original comment by vit.jo...@gmail.com on 10 Jun 2011 at 8:13

GoogleCodeExporter commented 9 years ago 
Issue 122 has been merged into this issue.

Original comment by vit.jo...@gmail.com on 21 Jul 2011 at 5:49

GoogleCodeExporter commented 9 years ago 
I agree. It would be great to be able to select a group or individuals that 
have access to a folder or file upon uploading the file/folder. Has this 
already been implemented or is it considered for a future release?

Original comment by cerup...@gmail.com on 28 Jul 2011 at 1:24

GoogleCodeExporter commented 9 years ago 
I would really love for per-document or per-folder permissions, so I could 
upload invoices for clients but not have those available to 
developers/designers on a project. I know sub-projects make this possible but 
that's kind of a pain in the neck.

Is there anywhere I could donate to a bounty for this feature? This one is 
killer for me!

Original comment by chrisvan...@gmail.com on 20 Sep 2011 at 2:47

GoogleCodeExporter commented 9 years ago 
Issue 158 has been merged into this issue.

Original comment by vit.jo...@gmail.com on 4 Oct 2011 at 7:58

GoogleCodeExporter commented 9 years ago 
Issue 181 has been merged into this issue.

Original comment by vit.jo...@gmail.com on 15 Nov 2011 at 9:32

GoogleCodeExporter commented 9 years ago 
Hi,

There's an estimated date to include this functionality?

It's really necessary.

Regards

Original comment by horaciov on 1 Dec 2011 at 7:05

GoogleCodeExporter commented 9 years ago 
How about this issue's status?

Original comment by tamdinh on 2 Aug 2012 at 7:28

GoogleCodeExporter commented 9 years ago 
Any Progress ? Really could use the feature !

Original comment by hans.mic...@gmail.com on 16 Oct 2014 at 3:01