Restricting Access to Records

About access rules
Access rules, in conjunction with Endeca's Access Control System, allow you to control which records a user can access.
Working with multiple access rules
Having two rules in a single Access Rules component is equivalent to having two Access Rules components, each with a single rule.
Creating the Endeca.ACL.Allow.Read property
In order to use access rules, you must create an Endeca.ACL.Allow.Read property and enable it for record filtering. You only need one instance of this property per project, even if you have multiple access rules that use it.
Creating an access rule
Allow a group to access records matching a value specified in the access rule.
Running a baseline update for access rules
After modifying rules, send new instance configuration to Endeca Workbench and run a baseline update.
Configuring the Web application to use access rules
You can use access rules with the Endeca Standard Application, or with your own custom application.
Crawling source data
The Endeca Information Access Platform supports file system and Web crawlers that gather data from source documents and allow you to write out Endeca records based on the source documents.
About implementing partial updates
Pipelines that implement partial updates must incorporate an update adapter.
Working with external taxonomies
You may build all or part of a logical hierarchy for your data set outside of Developer Studio and then transform that logical hierarchy into Endeca dimensions and dimension values for use in search and Guided Navigation.
About the Agraph
The Agraph enables scalable search and navigation by partitioning a very large data set into multiple Dgraphs running in parallel.