Column masking shows sensitive values masked to team members of the roles you choose in an account project. Set the roles to mask in the Project Configuration window. Specify the values to mask in two ways:
- Designate a sensitive column to mask its entire value.
- Register a regular expression pattern to mask only matching text.
Masking controls only the values you see; it does not encrypt data. That limit is explained in Security and where your data goes.
What's on the screen
Masking is set per role in the tab. The tab is visible only to the owner of an account project and to roles with All Permissions turned on, and only the owner changes its values.
| No. | Name | Description |
|---|---|---|
| 1 | Role tabs | Open the Manager, DBA and Member roles one at a time. The owner is not in the list and always sees the original values. |
| 2 | Sensitive Data Masking checkbox | When checked, team members of this role see sensitive columns and pattern matches masked. It cannot be checked for a role with All Permissions turned on. |
| 3 | Column Masking | Lights up with a count when sensitive columns are designated. Click the count to see the list of connections and columns. |
| 4 | Pattern Masking | Lights up with a count and the pattern names when patterns are turned on. |
| 5 | Manage Patterns… button | Opens the window for registering and editing patterns (see 'Registering a pattern' below). |
| 6 | Warning | Text describing the limits of masking. It is the same as the box below. |
- It is turned on per role, but it carries down. Masking Manager also masks DBA and Member, and masking DBA also masks Member. A checkbox turned on because of a higher role cannot be changed and is marked (automatically applied because a higher role is masked).
- A masked role gets both sensitive columns and patterns.
Choosing the roles to mask
- Open the account project with the owner's account and open the tab.
- Open the tab of the role to mask and check Sensitive Data Masking.
- Save the Project Configuration window. It applies to SQL tabs that team members of that role have open from their next run.
Designating sensitive columns
Columns can be designated only when at least one role is masked. Right-click a column and choose the Mark as sensitive menu.
Right-click a column in one of the following places.
Where Columns you can designate A table node in the ERD Character-type columns of a table that exists in the database, excluding primary and foreign keys The column grid of a table tab Same as above The column grid of a view tab Every column of the view, regardless of type or key Choose the Mark as sensitive menu (1). The designation is saved to the server immediately; there is no save button to click.
Designated columns get an orange lock icon before the column name in table tabs and view tabs.
- Example: in the demo shop, the
emailandnamecolumns of thecustomertable and theline1column of theaddresstable are good candidates.customer_idis a primary key andaddress.customer_idis a foreign key, so the menu does not appear for them. - The owner and team members of roles that are not masked can designate columns. Only the owner can undo it (the Unmark sensitive menu), because undoing makes the values visible again to masked roles.
- Tables and columns newly created in the ERD and not yet applied to the database cannot be designated.
- If a designated column later becomes a primary or foreign key, the designation is removed automatically when the owner opens that table, because rows cannot be edited or referenced through a masked key.
Registering a pattern
Patterns form one list for the whole project. They mask only the parts of string values in results that match the regular expression, so use them for phone numbers or email addresses mixed into sentences such as notes and descriptions.
In the tab, open a masked role and click the Manage Patterns… button. The Manage Masking Patterns window opens. The switches in the list turn patterns on and off.
Click the + Add Pattern button.
The buttons in the Quick start: row (on the English screen Mobile Phone (KR), Mobile Phone (US), Email and Credit Card No.; the list differs by UI language) fill in the name, regular expression and sample text. To write your own, fill in Pattern Name and Regular Expression.
Choose Masking Mode.
Mode How it masks Partial Keeps a few characters at the start and end of the match and replaces the rest with the character in Mask char. With Keep separators (- space) checked, -and spaces are keptFull Masks the whole match Template Replaces it with the text in Replacement Template. Use $1,$2to insert the regular expression's groupsEnter sample text in Preview to check the result, then click the OK button.
- Values filled in by the buttons in the Quick start: row (1) can be edited. If the regular expression (2) is invalid, the preview (4) shows Fix the regex to see the preview..
- The option fields below change with the mode (3).
- Only the owner and roles with All Permissions turned on can register and edit patterns. Patterns are saved directly in this window, separately from saving the Project Configuration window.
Where masking applies
Values are masked by the server that runs the query, before the results are sent to the screen: on the local server on the team member's device for the desktop app, and on the NeoSQL server for the web. The following is what happens for a team member of a masked role.
| Path | Masking |
|---|---|
| Result grid of the SQL editor | Sensitive columns show **** and pattern matches show the configured form. Copies stay masked, and masked cells cannot be edited (Result grid) |
| Exporting results, the Data Export... item in the explorer | Masked values are written to the file (Exporting results) |
| Native Backup | Dump tools cannot mask values, so the menu is hidden and the server (the local server on desktop, the NeoSQL server on the web) rejects the request (Data export, import and native backup) |
| Rows AI Assistant queries | Masked by role. Turning on Always mask sensitive data for the connection masks regardless of role |
Results of execute-query from an external MCP client | Same as AI Assistant. The policy is read again from the server for each run, and the query is not run if it cannot be read |
| RLS simulator | Not masked. See 'Things to keep in mind' below |
Things to keep in mind
- Masking is not a database permission. Values can come out through detours such as views or functions that return the same value, or queries that filter on the value (
WHERE email LIKE 'a%'). For values that must stay hidden, encrypt the column or split database account permissions on the database side. - The RLS simulator opened on PostgreSQL connections does not mask results. Team members of masked roles can see original values of sensitive columns through the simulator (RLS matrix and simulator).
- In the desktop app, both masking and the database connection happen on the team member's own device. Do not use it to protect values from someone who has full control over their device.
- When roles or sensitive columns change, open SQL tabs of team members apply the change from their next run. A tab that missed the change notification may keep running with the old policy until the project is opened again.
- As the If structure information cannot be read, some additional values may be masked or editing may be restricted. text below the warning says, when NeoSQL cannot work out which column of which table a query reads, it masks more or blocks editing to be safe.
Related screens
- Security and where your data goes: The difference between what masking and encryption protect.
- Sharing and members: The screen for inviting team members and assigning roles.
- Result grid: How masked values look.
- Project AI settings: The setting that always masks values sent to AI and MCP.
- Zero-knowledge encryption: Locks the credentials with a secret key.