> 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/reference/servoy-developer/object-editors/form-editor/form-editor-security-tab.md).

# Security

## Overview

<div align="left"><figure><img src="/files/5VnXXyGr6ita0DIRJq35" alt="Form Editor - Security Tab"><figcaption><p>Form Editor - Security Tab</p></figcaption></figure></div>

The **Security** tab of the Form Editor allows developers to control element-level security on the form by configuring which user groups (permissions) can view or access specific UI elements.

This enables you to enforce fine-grained UI restrictions based on security roles directly at the form level, ensuring that only authorized users can see or interact with certain fields, buttons, or other UI elements.

## Sections

### Permissions Panel (left side)

Lists all the available permissions (security groups) configured in the solution (for example: `Administrators`, `Observers`, `Users`).\
Selecting a permission will display the security configuration for that group on the right.

### Elements Matrix (right side)

Displays all the elements on the form for the selected permission.\
Each row corresponds to a specific form element.

It contains two columns of checkboxes:

* **Viewable**: Determines if the element is visible to users in this permission group.
* **Accessible**: Determines if the element can be interacted with (editable/clickable) by this group.

### Global Buttons & Options (top right)

* **Toggle Viewable**: Quickly checks/unchecks the viewable status for all elements under the selected permission.
* **Toggle Accessible**: Quickly checks/unchecks the accessible status for all elements under the selected permission.
* **No rights unless explicitly specified**: Enabling this will ensure that unless a viewable or accessible right is explicitly set, the default is to deny.

## Using the Security Tab

<div align="left"><figure><img src="/files/gtXgrbvqAU7WAnaWqZXb" alt="Using the Security Tab"><figcaption></figcaption></figure></div>

Here’s how to configure element security on a form:

1. **Select the Permission**
   * Click on a group from the left panel (e.g., `Administrators`).
2. **Configure View and Access Rights**
   * On the right side, for each element, check or uncheck the `Viewable` and `Accessible` boxes to determine what users in this group can see and interact with.
3. **Use Global Controls for Quick Setup**
   * Use `Toggle Viewable` or `Toggle Accessible` to quickly grant or revoke these rights for all elements.
   * Check `No rights unless explicitly specified` to enforce strict permissions, requiring you to explicitly grant rights for each element.


---

# 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.servoy.com/reference/servoy-developer/object-editors/form-editor/form-editor-security-tab.md?ask=<question>&goal=<endgoal>
```

`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.
