Changeset 3332
- Timestamp:
- May 11, 2007, 3:50:45 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/src/docbook/userdoc/project_permission.xml
r3329 r3332 36 36 between users while protecting all data against unauthorized 37 37 access or modification. To make this possible an elaborate 38 permission system has been developed that allows a user to38 permission system has been developed that allows an user to 39 39 specify exactly the permission to give to other users and at the 40 40 same time makes it easy to handle the permissions of multiple … … 119 119 <listitem> 120 120 <para> 121 Permission to change the permissions .121 Permission to change the permissions on the item. 122 122 </para> 123 123 </listitem> … … 144 144 145 145 </variablelist> 146 146 <note> 147 An user's permissions need to be reloaded for the permissions that have been 148 changed should take effect. This is done either manually with the menu choice 149 <menuchoice> 150 <guimenu>File</guimenu> 151 <guimenuitem>Reload permissions</guimenuitem> 152 </menuchoice> 153 or automatically next time the user logs in to BASE. 154 </note> 155 147 156 </sect2> 148 157 … … 170 179 generic item types and is valid for all items of that type. 171 180 The role-based permissions also include a special deny permission 172 that can prevent auser from accessing any item. In that case,181 that can prevents an user from accessing any item. In that case, 173 182 the permission check stops here. 174 183 </para> … … 238 247 <para> 239 248 Another aspect of the permission system is that plugins 240 may also have permissions o ntheir own. The default is that249 may also have permissions of their own. The default is that 241 250 plugins run with the same permissions as the user that invoked 242 251 the plugin has. Sometimes this can be seen as a security risk … … 256 265 The first case makes it possible to develop a plugin that allows 257 266 users to do things that they normally don't have permission to do. 258 The second scase is the same as not using the plugin permission system,267 The second case is the same as not using the plugin permission system, 259 268 except that unspecified permissions are always denied when the 260 269 plugin permission system is used. … … 368 377 369 378 <para> 370 Since it important to always have an active project379 Since it's important to always have an active project 371 380 there are several ways to make a project 372 381 the active one. … … 464 473 <screenshot> 465 474 <mediaobject> 466 <imageobject><imagedata fileref="figures/project_members.png" format="PNG" /></imageobject>475 <imageobject><imagedata contentwidth="10cm" width="10cm" fileref="figures/project_members.png" format="PNG" /></imageobject> 467 476 </mediaobject> 468 477 </screenshot> … … 497 506 <listitem> 498 507 <para> 499 When you select a user or group in the508 When you select an user or group in the 500 509 list the current permission will be checked. To change the 501 510 permissions just check the permissions you want to … … 507 516 <note> 508 517 In most cases, you should give the project members 509 <emphasis>use</emphasis> permission. This will allow a user518 <emphasis>use</emphasis> permission. This will allow an user 510 519 to use all items in the project as well as add new items to it. 511 520 If you give them write or delete permission they will be able … … 599 608 <para> 600 609 It support only a limited set of columns (name, description and 601 owner) since the ese are the only properties that are commom610 owner) since these are the only properties that are common 602 611 among all items. 603 612 </para>
Note: See TracChangeset
for help on using the changeset viewer.
