> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/guides/develop/application-design/data-modeling/databases/tables/table-security.md).
# Table security
## Overview
The Table Security Editor in Servoy Developer allows for detailed management of user permissions, restricting or granting access rights to specific tables and operations within the database. Permissions are structured around user roles, such as Administrators and Operators, and can be configured to control activities like reading, inserting, updating, and deleting records.
## Get Started
To work with the Table Security Editor, you should first [connect to your database](/guides/develop/application-design/data-modeling/databases.md#connect-to-a-database) and [open the table](/guides/develop/application-design/data-modeling/databases/tables.md#open-edit-a-table) in the [Table Editor](/reference/servoy-developer/object-editors/table-editor.md), where you will manage permissions.
Table Editor - Permissions
## Configuring Permissions
1. In the Security tab of the Table Editor, permissions are listed by user roles such as Administrators, Operators and / or other user defined rols.
2. For each role, select the desired permissions:
* Read: Allows viewing of records.
* Insert: Permits adding new records.
* Update: Enables modification of existing records.
* Delete: Allows deletion of records.
* Tracking(Insert/Update/Delete): Tracks changes to records.
* Tracking(Select): Tracks access to records.
3. Check or uncheck boxes to grant or revoke these permissions for each role.
## Applying Changes
Permissions will be updated when pressing 'Save' button in the editor, affecting user access as specified.
## Reference to Managing Users
For instructions on managing user roles and adding new users, refer to the detailed guide in the [Security Editor](/reference/servoy-developer/object-editors/security-editor.md) section of the documentation.
## Remarks
{% hint style="info" %}
Permissions set in the Security Editor are crucial for maintaining data integrity and regulating access to sensitive information within the database. It is recommended to review and update these settings regularly to adapt to any changes in team roles or security requirements.
{% endhint %}
---
# 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.servoy.com/guides/develop/application-design/data-modeling/databases/tables/table-security.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.
