Redmine

+1

+1

An simple solution would fit our needs so just internal/public per page would be enough. Where all logged in users can see "internal" pages. Of course it would even be better to integrate it into the existing Rights system.

+1

I second Bernhard: A checkbox to set the page "public" or "private" would be sufficient. However, "private" pages should only be visible if a user is both logged in and member of the project the wiki is hooked to. Furthermore, wiki links from public to private pages should display an access denied info.

+1

+1

+1

I think that use case proposed by Jimi Jones is the really useful one, moinmoin wiki has that kind of ACL and is very powerful and flexible, probably to avoid the gui part (that could be complex and hard to build a simple and usable one) in a first stage use the magic first line #ACL.

Is this posible that could be implemented like a plugin?, My knowledge of ruby on rails is zero, but maybe somebody at my work aims to develop a plugin.

+1
We have meeting minutes that we would like to keep confidential, but lots of other useful stuff on the Wiki, that is interesting for 'external' users. Please implement!

+1

How do we go about getting this feature started?

+1

SPAM

+1

+1 This would be extremely helpful for having clients interacting with developers on projects while keeping some content separate from them.

+1.

+1

+1

Also might be useful to extend this feature to a wiki format tag (like < pre>) that can be inserted anywhere where wiki format is accepted (issues description, etc) making parts of an issue description private is very useful

even tagging an issue notes as private or "hidden to not registered users"

+1
We only need two different Wiki areas: Public Wiki and Private Wiki. Permissions would be set like today, in the Role edit. Instead of only the Wiki box that we have there, we'd have Public Wiki and Private Wiki.

+1

+1

public/private setting is not good enough for our needs because our company uses Redmine to communicate with our clients and there's no public users (every user has to login).
Setting a minimum role for each wiki page would be sufficient, though.
The role of the client is 'Reporter' and some wiki pages should be visible/editable only to 'Developer' and 'Manager' (i.e. members of our comapny).

Please ignore my last comment. I had just started using Redmine and expected there can be multiple wiki pages for a project...

+1

+1

+1

+1

Please, take a look at my plugin http://www.redmine.org/plugins/private_wiki

+1
Oleg Volossetski Kandaurov, thanks i'll try your plugin

+1
I want to be able to give read access for pages only to particular users or roles.

We(Catincan) are interested in financially contributing to this feature if one of the redmine developers is willing to implement it.

Why not crowdfund this feature on https://www.catincan.com ?

+1
We (Generali CZ) are also interested.
Is a copy of #1086.

+1

+ 1

+1

+1

• Public (anyone, signed in or not)
• Private (logged in only)
• Restricted (Black / White list based on existing 'groups')

+1

+1.

1. Manage Wiki View Page permission [https://github.com/stpl/manage_wiki_view_page_permission]
2. Wiki permissions [https://github.com/edtsech/redmine_wiki_permissions] [last updated 2012]

and only the first one is working with current versions of ruby/redmine :(

+1 long awaiting feature

+1

+1
unfortunately the plugins mentioned in #2636#note-40 seem to be dead and don't support redmine 4

Heiko Robert wrote:

+1
unfortunately the plugins mentioned in #2636#note-40 seem to be dead and don't support redmine 4

Well actually one of the plugin actually works with Redmine 4.1.0
https://www.redmine.org/plugins/manage_wiki_view_page_permission