> For the complete documentation index, see [llms.txt](https://docs.yansalabs.com/simple-data-separation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yansalabs.com/simple-data-separation/overview/key-features.md). # Key Features * **Record separation can occur on any table**, based on any field that references Company, Group, Department, Location, User, or a custom Defined Relationship * Users only see records for the **Groups/Companies/Etc** to which they belong * Record separation can be applied on a **per table basis, with different rules per table** * Record separation can be applied based on **one or multiple fields** per table * Record separation can be **selectively applied** to only certain cases (ie - only separate groups x and y, but leave z unaffected) * **Record separation can be overridden** by **admin**, based on **'owner overrides'** (ie - if the logged in user is the 'Opened by' or 'Caller'), based on a user being an **approver** for a task, or based on membership to a **'visibility group'** * Record separation can be selectively **cascaded to child tables** * **Query Caching** may be utilized to increase efficiency * **‘One-way’ or ‘Two-way’** separation can be utilized to achieve heightened levels of security * **Simple Access Requests** allow one-off, time-bound access to specific users & records * **Child tables** can selectively be hidden from parent table views to protect sensitive data * **Session caching** is used to ensure the best user experience * Customization is available to manually add additional queries to a rule ### Example uses include: * Selectively segregate Incidents so that only their assignment group can see them. * Secure sensitive HR, Legal or Finance data so that only the appropriate groups have visibility. * Segregate data amongst assignment groups while allowing overarching visibility to select groups for oversight & compliance. * Allow users to request record access on-demand in an approval-driven, auditable fashion. * Hide data from end users without alerting them to its presence. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.yansalabs.com/simple-data-separation/overview/key-features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.