Documentation
MODULEKEY
usage
<MODULEKEY depth="1" ID="1">
<INFO>
<ID>number</ID>
<CREATORID>contactID</CREATORID>
<OWNERID>contactID</OWNERID>
<GROUPID>groupID</GROUPID>
<MODIFIERID>contactID</MODIFIERID>
<CREATIONDATE>YYYY-MM-DD hh:mm:ss</CREATIONDATE><!-- automatically filled by Sushee -->
<MODIFICATIONDATE>YYYY-MM-DD hh:mm:ss</MODIFICATIONDATE><!-- automatically filled by Sushee -->
<MODULETOID>moduleID</MODULETOID>
<ISVIRTUAL>0</ISVIRTUAL>
<VIRTUALID />
<ISPRIVATE>{0,D}</ISPRIVATE><!-- D means you can see all elements, 0 means you can only see your own elements or the one that are public -->
<DENOMINATION>string</DENOMINATION>
<COMMENT>string</COMMENT>
<FIELDS>
<ID>{R,W,0}</ID><!-- Defines the general access to the objects : R = read-only, W = read, write, 0 = no access -->
<ACTIVITY>{W,0}</ACTIVITY><!-- defines whether the user can delete an element : W = can delete, 0 = cannot delete -->
<fieldname1>{R,W,0}</fieldname1>
<fieldname2>{R,W,0}</fieldname2>
...
</FIELDS>
<SERVICES>
<dependencies>{R,W,0}</dependencies>
<category>{R,W,0}</category>
<description translator="true/false">{R,W,0}</description><!-- translator="true" means the user can only edit the content is his own language (defined in his contact) -->
<comment>{D,R,W,0}</comment><!-- D is for the administrator, who can write comments in the name of others -->
<omnilink>{R,W,0}</omnilink>
</SERVICES>
<DEPENDENCIES>
<depName1>{R,W,0}</depName1>
<depName2>{R,W,0}</depName2>
...
</DEPENDENCIES>
</INFO>
</MODULEKEY>
A modulekey represents the access to a type of object (module) for a user. It defines which fields, which services and which dependency types the user can read/modify.
Voir aussi :
KEYRING
Secure the user profile
checkModule
check the user has access to a type of object