The access control features discussed so far can be considered standard methods to provide usable sets of views and data to end users. However, implementation teams are often confronted with the requirement to filter data based on criteria other than the user's current position. For example, there might be the need to display data of celebrities only to selected employees.
Another requirement could be that experienced users should be able to use a large and complex form applet for data entry whereas new hires should start with a simpler version of the applet.
To support these requirements, Siebel CRM includes the personalization engine, which acts as an additional filter layer on views, applets, and records to provide a personalized user experience. The following diagram depicts the various filter mechanisms that limit the user's access to data, views, and applets:
As we can see from the diagram, the Siebel Personalization layer allows us to declare...