> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/administration/users-and-roles/users-and-roles-management/column-security-policies.md).
# Column Security Policies
The Column Security Policies list masking policies applicable to data objects, detailing which users or groups can access data without masking. OvalEdge supports various masking policies, including masking alphanumeric characters, masking all characters, showing the last 4 characters, showing the first 4 characters, and showing blanks.
* Policy: Displays the Policy Name.
* Policy Scheme: Displays the Name of the masking Scheme applied to the Policy. **Example:** Mask Alphanumeric Characters with xxxxxx, Mask All Characters with xxxxxx, etc.
* Allowed Roles: Displays the Roles allowed to view the unmasked data. When creating a masking policy, adding more roles authorized to view the data is possible.
* Users: Displays the Users allowed to view the unmasked data. When creating a masking policy, it is possible to add more Users who are authorized to view the data.
* Created Date: Displays the date when the masking policy was created.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ovaledge.com/release8.3/administration/users-and-roles/users-and-roles-management/column-security-policies.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
