Mercurial > p > roundup > code

comparison doc/customizing.txt @ 935:2abb6b2697b6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc updates
author Richard Jones <richard@users.sourceforge.net>
date Thu, 15 Aug 2002 00:39:51 +0000
parents 299f4890427d
children f89b8d32291b
comparison
equal deleted inserted replaced
934:fdcf16b444a9 935:2abb6b2697b6
1 =================== 1 ===================
2 Customising Roundup 2 Customising Roundup
3 =================== 3 ===================
4 4
5 :Version: $Revision: 1.14 $ 5 :Version: $Revision: 1.15 $
6 6
7 .. contents:: 7 .. contents::
8 8
9 9
10 What You Can Do 10 What You Can Do
11 --------------- 11 ---------------
12 12
13 Customisation of Roundup can take one of four forms: 13 Customisation of Roundup can take one of five forms:
14 14
15 1. `instance configuration`_ file changes 15 1. `instance configuration`_ file changes
16 2. database, or `instance schema`_ changes 16 2. database, or `instance schema`_ changes
17 3. "definition" class `database content`_ changes 17 3. "definition" class `database content`_ changes
18 4. behavioural changes, through detectors_ 18 4. behavioural changes, through detectors_
19 5. `access controls`_
19 20
20 The third case is special because it takes two distinctly different forms 21 The third case is special because it takes two distinctly different forms
21 depending upon whether the instance has been initialised or not. The other two 22 depending upon whether the instance has been initialised or not. The other two
22 may be done at any time, before or after instance initialisation. Yes, this 23 may be done at any time, before or after instance initialisation. Yes, this
23 includes adding or removing properties from classes. 24 includes adding or removing properties from classes.
911 <td><display call="list('files')"></td> 912 <td><display call="list('files')"></td>
912 </tr> 913 </tr>
913 </property> 914 </property>
914 915
915 916
916 Security 917 Access Controls
917 -------- 918 ---------------
918 919
919 A set of Permissions are built in to the security module by default: 920 A set of Permissions are built in to the security module by default:
920 921
921 - Edit (everything) 922 - Edit (everything)
922 - View (everything) 923 - View (everything)
923 924
924 The default interfaces define: 925 The default interfaces define:
925 926
926 - Web Registration 927 - Web Registration
928 - Web Access
927 - Email Registration 929 - Email Registration
930 - Email Access
928 931
929 These are hooked into the default Roles: 932 These are hooked into the default Roles:
930 933
931 - Admin (Edit everything, View everything) 934 - Admin (Edit everything, View everything)
932 - User () 935 - User (Web Access, Email Access)
933 - Anonymous (Web Registration, Email Registration) 936 - Anonymous (Web Registration, Email Registration)
934 937
935 And finally, the "admin" user gets the "Admin" Role, and the "anonymous" user 938 And finally, the "admin" user gets the "Admin" Role, and the "anonymous" user
936 gets the "Anonymous" assigned when the database is initialised on installation. 939 gets the "Anonymous" assigned when the database is initialised on installation.
937 The two default schemas then define: 940 The two default schemas then define:
949 952
950 You may alter the configuration variables to change the Role that new web or 953 You may alter the configuration variables to change the Role that new web or
951 email users get, for example to not give them access to the web interface if 954 email users get, for example to not give them access to the web interface if
952 they register through email. 955 they register through email.
953 956
957 You may use the ``roundup-admin`` "``security``" command to display the
958 current Role and Permission configuration in your instance.
959
954 960
955 ----------------- 961 -----------------
956 962
957 Back to `Table of Contents`_ 963 Back to `Table of Contents`_
958 964
Roundup Issue Tracker: http://roundup-tracker.org/