Project

General

Profile

Actions

Feature #8392

closed

Grant access to particular Wiki page

Added by Kamil . over 13 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Permissions and roles
Target version:
-
Start date:
2011-05-18
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate

Description

Some of the Wiki pages (like these containing logins/passwords to the third party services or other confidental information) should not be viewed by all of the project members!

It has to be possible to grant/deny access to that particular Wiki pages.


Related issues

Is duplicate of Redmine - Feature #2636: Feature Request: Wiki ACLs (Access control for individual pages)New2009-01-31

Actions
Actions #1

Updated by Dmitry Salashnik over 13 years ago

+1

Actions #2

Updated by Aleksandra Wozniak over 13 years ago

+1

Actions #3

Updated by Andrzej Kojder over 13 years ago

+1

Actions #4

Updated by Anoop L over 13 years ago

+1

Actions #5

Updated by Adam Hepner over 13 years ago

+1

Actions #6

Updated by Jeffrey Jones over 13 years ago

Would you guys expect to be able to do something like:

Page A can only be viewed by users A B C?
Page B can only be views by users D F G and Group Z?

Or is a simple "Page protected" flag per page plus a "view protected page" permission good enough?

Actions #7

Updated by Kamil . over 13 years ago

The second option is good for the beginning because it seems to be easy to implement and it's better than nothing.
Ideal to have them both.

Actions #8

Updated by Daniel Schaarschmidt over 13 years ago

+1
The secound option should be good enough - it could be similar to the new private issues feature.

The first option sounds really good - but like Kamil I'm not sure this is as easy to implement as option 2.
IMHO it would require a complete change of the permission system to really fit in. Right now I'm not aware of any Redmine-Feature that maintains a seperate permission list per object - although under some circumstances it would be great to have that.

Actions #9

Updated by Naveen Prabhu almost 13 years ago

+1

Actions #10

Updated by Tomas Chmiel about 12 years ago

Are there any news on this feature?

Actions #11

Updated by dale woolridge about 12 years ago

there is the redmine_wiki_permissions plugin that can do this. i've recently put in a pull request so it works properly with 1.4. i haven't tried with 2.0. it shouldn't conflict with other plugins anymore.

Actions #12

Updated by Alexander Pilipenko over 10 years ago

+1
redmine_wiki_permissions plugin does not work with redmine >2.0

Actions #13

Updated by Hans Artmann over 10 years ago

Tried to install redmine_wiki_permissions in 2.5 with rails 3.2 and came as far as

  • install with _rails install
  • move the redmine_wiki_permissions folder from vendor/plugins to plugins
  • add dispatcher to Gemfile

Now I'm getting

redmine_wiki_permissions/init.rb:7:in `<top (required)>': undefined method `to_prepare' for Dispatcher:Module (NoMethodError)

on startup. I guess the dispatcher gem isn't 3.2 compatible

Any ideas? I'd really have the wiki permissions back now that my upgrade from redmine 1.0 to 2.5 has worked (basically installing rvm, doing a fresh redmine install and migrating the database).

Actions #14

Updated by Anh Le Giang almost 9 years ago

+1

Actions #15

Updated by Toshi MARUYAMA over 8 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Duplicate of #2636.

Actions #16

Updated by Toshi MARUYAMA over 8 years ago

  • Is duplicate of Feature #2636: Feature Request: Wiki ACLs (Access control for individual pages) added
Actions

Also available in: Atom PDF