Revision [1487]
Last edited on 2009-05-13 19:51:20 by PhilDaintreeAdditions:
$PageSecurity = CUSTOMER_MAINTENANCE;
DEFINE CUSTOMER_MAINTENANCE 5
DEFINE CUSTOMER_INQUIRIES 3
DEFINE ORDER_ENTRY 1
DEFINE CUSTOMER_MAINTENANCE 5
DEFINE CUSTOMER_INQUIRIES 3
DEFINE ORDER_ENTRY 1
Deletions:
DEFINE SelectSupplier.php 5
DEFINE SelectCustomer.php 3
DEFINE SelectOrderItems.php 1
Revision [1486]
Edited on 2009-05-13 19:49:38 by PhilDaintreeAdditions:
There is also a list of files/scripts/pages and the corresponding tokens they use in the develoment section of this wiki.
Tim had a nice idea to improve the flexibility of this system is to create an include of the $PageSecurity variables for each page - in every script
%%(php) include ("includes/PageSecurityDefinitions.php");
$PageSecurity = PAGENAME; //Where PAGENAME is the name of the script eg SelectSupplier.php
...
%%
then under includes/PageSecurityDefinitions.php
%%(php) DEFINE SelectSupplier.php 5
DEFINE SelectCustomer.php 3
DEFINE SelectOrderItems.php 1
....
%%
This script would then provide one place that permissions and roles could be more tightly defined using the existing system
Tim had a nice idea to improve the flexibility of this system is to create an include of the $PageSecurity variables for each page - in every script
%%(php) include ("includes/PageSecurityDefinitions.php");
$PageSecurity = PAGENAME; //Where PAGENAME is the name of the script eg SelectSupplier.php
...
%%
then under includes/PageSecurityDefinitions.php
%%(php) DEFINE SelectSupplier.php 5
DEFINE SelectCustomer.php 3
DEFINE SelectOrderItems.php 1
....
%%
This script would then provide one place that permissions and roles could be more tightly defined using the existing system
Deletions:
Revision [954]
Edited on 2007-12-01 18:07:43 by PhilDaintreeAdditions:
As explained [[http://www.weberp.org/weberp/doc/Manual/ManualContents.php?ViewTopic=SecuritySchema elsewhere in the manual]] security "tokens" are used to control the access to each file (also called script or page) within webERP. These "tokens" can be seen in Setup > Role Permissions then editing one of the roles. See the [[FilesScriptsPagesAndTokensList list of tokens with their number and explanation]]. Each token is either part of the role you selected to edit or it is not but is available to be part of that role if you choose it to be.
Deletions:
Revision [953]
Edited on 2007-12-01 18:06:32 by PhilDaintreeAdditions:
As explained [[http://www.weberp.org/weberp/doc/Manual/ManualContents.php?ViewTopic=SecuritySchema elsewhere in the manual]] security tokensare used to control the access to each file (also called script or page) within webERP. These tokens can be seen in Setup > Role Permissions then editing one of the roles. A [[FilesScriptsPagesAndTokensList list of tokens with their number and explanation]]. Each token is either part of the role you selected to edit or it is not but is available to be part of that role if you choose it to be.
Deletions:
Revision [952]
Edited on 2007-12-01 18:04:44 by PhilDaintreeAdditions:
As explained [[http://www.weberp.org/weberp/doc/Manual/ManualContents.php?ViewTopic=SecuritySchema elsewhere in the manual]] security tokensare used to control the access to each file (also called script or page) within webERP. These tokens can be seen in Setup > Role Permissions then editing one of the roles. A list of tokens with their number and explanation will be shown. Each token is either part of the role you selected to edit or it is not but is available to be part of that role if you choose it to be.
Deletions:
Revision [296]
Edited on 2007-10-05 12:07:57 by PhilDaintreeDeletions:
%%
