Implementing the Reseller Resources Access Control Structure
The following implementation procedure restricts the base resellers’ access to product resources only, premier resellers’ access to product resources and sales resources, and alliance resellers’ access to all resources.
To implement the Reseller Resources access control structure
Construct the Reseller Resources catalog, and specify it as private, with access provided to the Base Resellers access group.
Access to the catalog is also granted to the Premier and Alliance access groups because access group access is inherited.
Associate the Base Resellers access group with the Product Resources category, and use the Cascade button.
Access is inherited by the Premier and Alliance access groups from the Base Resellers group, and access cascades from the Product Resources category to its subcategories containing data. The resulting behavior is that all the nodes in the Resellers Community have access to all the subcategories in the Product Resources category.
Associate the Premier access group with the Sales Resources category, and use the Cascade button.
Access is inherited by the Alliance access group from the Premier group, and access cascades from the Sales Resources category to its subcategories containing data. The resulting behavior is that the Premier and Alliance groups have access to all the subcategories in the Sales Resources category.
Associate the Alliance access group with the Sales Resources category, and use the Cascade button.
No group inherits access from the Alliance group. Access cascades from the Alliance Resources category to its subcategories containing data. The resulting behavior is that only the Alliance group has access to the subcategories in the Alliance Resources category.
Set the catalog to type Partner to make it visible to partners and consultants on partner applications such as Siebel Partner Portal, and to internal administrators on Siebel employee applications in the Info Center screen.
This structure meets the minimal maintenance requirement. If the status of a partner organization changes, add the partner organization to the appropriate access group and delete the partner organization from the old access group. If the status of a consultant changes, add the user to the appropriate user list, and delete the user from the old user list. Recategorized consultants and partner users are granted appropriate new access as defined by the structure.