Changes between Version 74 and Version 75 of SimpleMultiProjectPlugin

Timestamp:

Jul 28, 2020, 12:20:35 PM (4 years ago)

Author:

Cinc-th

Comment:

Added description of new permission system including current feature set.

SimpleMultiProjectPlugin

@@ -154 +154 @@
  1. Set project restrictions if necessary. See the following section '''Project Restrictions''' for info.
 == Project restrictions
+=== Current trunk and releases 0.7.2+
+A new permission system is currently developed and the first implementation landed with [17810]. See ticket #13850 used for tracking the effort.
+
+To activate project restrictions add the following permission policy:
+{{{#!ini
+[trac]
+permission_policies = SmpPermissionPolicy, ... any other ...
+}}}
+Make sure the new policy is the first in the list of available policies.
+
+Project permissions are assigned using the Trac permission admin panel. Each project has a unique ID which is not changing over the lifetime of  a project, even if you change the project name.
+
+To give a user access to a project you have to give the permission '''Project_<id>_MEMBER''' where ''<id>'' is the unique project id.
+
+The following restrictions are currently in place:
+ * Ticket filtering. Users only see tickets belonging to projects they're a member of. Tickets of projects without restrictions are alway shown.
+ 
+ This works for ticket pages and when doing custom queriers. 
+
+=== Legacy versions < 0.7.2
 With plugin versions 0.4-0.7.1 we support project-wise restriction of resources to a subset of users (#11367). Switch on the plugin component ''ProjectTicketsPolicy'' to activate it, and add the following to your `trac.ini` file:
  {{{#!ini
@@ -163 +183 @@
     - {{{ !, bob, anonymous, group2 }}} to exclude from the project.
 
-=== Note
-Current trunk doesn't support restrictions yet. A new permission system is currently developed. See ticket #13850.
 == Configuration