Ignore:
Timestamp:
May 11, 2007, 3:50:45 PM (14 years ago)
Author:
Martin Svensson
Message:

Fixes #526 Read "Projects and the permission system"

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/src/docbook/userdoc/project_permission.xml

    r3329 r3332  
    3636        between users while protecting all data against unauthorized
    3737        access or modification. To make this possible an elaborate
    38         permission system has been developed that allows a user to
     38        permission system has been developed that allows an user to
    3939        specify exactly the permission to give to other users and at the
    4040        same time makes it easy to handle the permissions of multiple
     
    119119            <listitem>
    120120              <para>
    121               Permission to change the permissions.
     121              Permission to change the permissions on the item.
    122122              </para>
    123123            </listitem>
     
    144144     
    145145        </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
    147156      </sect2>
    148157     
     
    170179            generic item types and is valid for all items of that type.
    171180            The role-based permissions also include a special deny permission
    172             that can prevent a user from accessing any item. In that case,
     181            that can prevents an user from accessing any item. In that case,
    173182            the permission check stops here.
    174183            </para>
     
    238247        <para>
    239248          Another aspect of the permission system is that plugins
    240           may also have permissions on their own. The default is that
     249          may also have permissions of their own. The default is that
    241250          plugins run with the same permissions as the user that invoked
    242251          the plugin has. Sometimes this can be seen as a security risk
     
    256265          The first case makes it possible to develop a plugin that allows
    257266          users to do things that they normally don't have permission to do.
    258           The seconds case is the same as not using the plugin permission system,
     267          The second case is the same as not using the plugin permission system,
    259268          except that unspecified permissions are always denied when the
    260269          plugin permission system is used.
     
    368377         
    369378          <para>
    370             Since it important to always have an active project
     379            Since it's important to always have an active project
    371380            there are several ways to make a project 
    372381            the active one.
     
    464473          <screenshot>
    465474            <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>
    467476            </mediaobject>
    468477          </screenshot>
     
    497506              <listitem>
    498507                <para>
    499                 When you select a user or group in the
     508                When you select an user or group in the
    500509                list the current permission will be checked. To change the
    501510                permissions just check the permissions you want to
     
    507516                <note>
    508517                In most cases, you should give the project members
    509                 <emphasis>use</emphasis> permission. This will allow a user
     518                <emphasis>use</emphasis> permission. This will allow an user
    510519                to use all items in the project as well as add new items to it.
    511520                If you give them write or delete permission they will be able
     
    599608            <para>
    600609              It support only a limited set of columns (name, description and
    601               owner) since theese are the only properties that are commom
     610              owner) since these are the only properties that are common
    602611              among all items.
    603612            </para>
Note: See TracChangeset for help on using the changeset viewer.