The “Advanced” tab of the rights window opens one window from a module to a department or closes one button, column or set of table rows — finer than the module level.
When you need this:
- Logistics needs deals, not system windows — open only “Deals” and “Pipelines and stages”.
- A content manager mustn't change prices — clear the column's “Edit”; the product grid replies “Editing this field is not allowed”.
- A department sees only wholesale customers — “Row filter” keeps only rows matching a condition.
- A menu item doesn't appear — the window right is missing.
Where to start: rights window → department → “Advanced” → the window's row.
What “Advanced” can do
- The window toggle opens or closes one window without touching the rest of the module.
- The “menu” section turns off a menu item separately while the window stays open; the item works only together with the right to the window.
- The monitor icon adds the window to the department's shortcut set.
- The “Who has access” section shows who actually has this window.
- The “Admin” badge marks a window that is opened to this department only deliberately.
- The “buttons” section hides individual buttons, tabs, fields and side panels.
- The “grids” and “fields” sections close a column for viewing or editing and filter rows by a condition.
- The window checkbox closes the window itself, wherever it's opened from — the menu or a button in another window.
What a window permission consists of
The second tab is for cases where the module level isn't enough: open one window from a module, hide one button, one column or part of a table's rows. On the right are all the app's windows, grouped by module.
- A window row has a toggle, the window name with its description, the “buttons”, “grids” and “menu” counters, a monitor icon and an arrow that expands the “buttons”, “grids”, “menu”, “fields” and “Who has access” sections. The last one lists active employees who have the window open in at least one department, their departments and last login.
- The “All / Open / Closed / On desktop” filter in the header works only here. The “Search window or description…” search is also visible on “Role”: typing switches you here, to the results. It also finds a window by its code from the operation log, even though the row doesn't show the code.
- On the left, under each department name, you see “Open … of … windows”.
1
Window switch2
Buttons counter3
Monitor icon4
Expand arrow5
Buttons section- The switch on the left opens or closes the whole window for the department.
- The counter shows how many of the window's buttons are open: 14 of 14.
- The monitor icon adds or removes the window's shortcut in the department's desktop set.
- The arrow expands the row to show what is inside the window.
- The buttons section lists the individual buttons inside the window; grids, menu and fields follow below it.
Everything you change here shows on “Role” right away: a module whose checkboxes no longer match a level is shown as “Custom”.
Monitor icon: a shortcut for the whole department
The monitor icon in an open window's row adds the window to the department's shortcut set or removes it. Current employees get or lose the shortcut at once, new ones get it with the department; the rest of the desktop stays. Closed windows have no icon. It's per department: one person adds their own shortcut. More: how to give a department a shortcut.
The “Admin” badge: windows opened only deliberately
Some windows change the whole account: rights, menu, API tokens, mail passwords, SQL queries to the site database, balance. By default only departments that need them for work have them. “Enable access for all subsystems”, copying rights and the module level don't grant them to others. Copying also closes those granted manually: reopen them afterwards.
For such a department, the window row shows an “Admin” badge. The toggle asks: “This is an administrative window: it gives access to account-wide settings. Open it for this department?”. After “Open window”, the buttons inside the window turn on by themselves. List of windows: administrative windows.
Five permission levels
There are five levels, and they aren't nested — each is kept in its own list and checked separately.
| Level | Where it's set | What it gives |
|---|---|---|
| Window | the toggle in the window row | open the window; the menu item turns on and off together with it |
| Menu item | the “menu” section in the window row | see the item in the menu — together with the right to the window |
| the “buttons” section in the window row | see a button, tab, field or side panel | |
| Table | the “grids” section in the window row | see the table in the window; “Row filter” |
| Table column | the “fields” section in the window row | “View” and “Edit” for a single column |
Checkboxes are read from the database every time a window opens, without being stored in the session. So changes take effect at once: the employee just closes and reopens the window or refreshes the page. The app also rereads a person's department list right after a change: moving someone to another department takes effect on the next page refresh.
Why a menu item shows only together with its window
An employee sees a menu item only when their groups have two rights at once: to the item and to the window it leads to. Turn on the item in the “menu” section but leave the window toggle off, and the item won't appear — with no warning. Turn on the window toggle, and after F5 the item is back.
The window toggle, the module level on “Role” and the bulk actions in the “Actions” menu turn the menu item on and off together with the window. To remove the item but keep the window open, use the “menu” section of the expanded window row: the window still opens from its shortcut, and the row gets a triangle mark.
The next time you turn the window off and on, the item comes back.
- Start or end
- Action or result
- Decision: the path depends on the answer
If someone clicks a menu item but no longer has the right to the window (the page was opened before the right was removed), a red message pops up:
You have no access to this window. Contact your administrator.
One window bypasses this rule on purpose — the one where the menu itself is set up. Otherwise, if you locked yourself out, you couldn't fix it.
How to hide a button or tab in a window
The “buttons” section lets you remove individual elements from a window instead of closing it entirely. The names here are readable: Button "Add Category", Button "Delete Category", "Main data" tab: full description, Sidebar: competitor prices. These are exactly the buttons the module level on “Role” switches.
Not every window has buttons. Price lists, categories and products have the most; most others have one or two. If the task sounds like “let the content manager edit products but not see purchase prices”, first check whether the window has the button or column you need. If it doesn't, you can't split access: no such checkbox exists.
If a window is closed but its buttons are on, the row gets a triangle mark with the hint “Buttons are enabled while the window itself is closed — the button route still works”.
Two more warnings: “The window is open but its menu item is disabled — the shortcut works, the menu stays silent” (appears if the item was turned off in the “menu” section) and “Buttons lead to a subordinate window that is closed — the employee will get “No access””.
How to close a table column or part of the rows
A window's tables and their columns are in the “grids” and “fields” sections of the expanded window row. Not every window has tables. In the “fields” section, each column has one toggle: it sets or clears “View” and “Edit” together; the module level on “Role” changes only “Edit”.
- “View” cleared — the cell value comes back empty. This works in seven windows: products, contacts, documents (both the list and the document items), manufacturers, price list products, the employee list and support. In other grids the value stays in place.
- “Edit” cleared — the column can't be edited in any grid with permissions. On top of that, the server rejects the edit in five grids: products, contacts, documents, manufacturers and price list products. In the product grid, trying to change such a field, for example via “Set value in bulk”, shows “Editing this field is not allowed”; API v2 answers such a product edit with error 422 and the same text. In other grids this protects the interface, not the data.
- Required columns ignore “View”. A cleared checkbox won't hide their value — this is by design.
- “Row filter” — a badge next to the table that opens the condition builder with “Clear condition” and “Save condition” buttons. The group sees only rows that match the condition. It works in the grids of contacts, organizations, products, price list products, the employee list and support. It complements “Data scope”: “Data scope” narrows records by the person responsible, the filter by any condition, for example “wholesale customers only”.
What the window checkbox closes
Clear a window's checkbox, and it won't open from the menu, a shortcut or a button in another window: instead of its content, the employee sees “No access”. The “None” level on “Role” works the same way, because it sets the same checkboxes.
Windows missing from the list
A permission exists only for a window that is in the registry. Some windows open from a button in another window and aren't in the registry — they have no checkbox and nothing can restrict them. Not all of them are minor:
| Window | What it does | Opened from |
|---|---|---|
| Change category | moves all selected products to another category | the catalog grid |
| Mailing settings | builds a recipient list and sends them an email | the contact list |
| Viewing a carrier | opens a delivery service waybill that is already created | the document card |
| Employee card | edits a person's user account | the organizational structure |
The four most dangerous windows aren't on this list: “Contact merge”, “Restore site from backup”, “SQL queries to the site database” and “Delivery waybill creation” are in the registry and refuse by their own checkbox. All of them are in the “Other” module.
Child windows
Windows opened from a button in another window — the manufacturer card from the manufacturers list, “Product Cart” (product trash) and the product card from “Products”, AI Media Studio from the product card, the column mapping wizard from a price list — have their own checkbox, like main windows. Close a child window: the parent stays open, its button shows “No access”.
During the update, child window checkboxes were set the same as their parents': whoever had access to “Products” also has “Product Cart” and the product card. Nobody's access changed with the update — the only change is that these checkboxes can now be cleared separately.
The Organizer (projects, tasks, notes, presentations, documents, spreadsheets, forms) splits one screen into several windows — each closes with its own checkbox, and the “None” level on the “Organizer” module closes the whole group.
To close one action rather than a whole section, clear the checkbox of the window where that action lives. Close the parent window when the person doesn't need the whole section.
Scenarios
Logistics needs deals, but not the system windows
Task. The logistics department needs to see deals and the pipeline to plan shipments of large orders.
What to click. Leave the “Other” module, where deals live, untouched on “Role”. Go to the “Advanced” tab, type “Deals” in the search and turn on the “Deals” window toggle: its menu item turns on with it. Do the same for “Pipelines and stages”. To put deals on the desktop too, click the monitor icon in the window row.
What the employee sees. Deals and the pipeline next to their orders. What they won't get: “Contact merge” and other windows from the same “Other” module — the “Edit” level on “Other” would open them together with deals. On “Role”, the “Other” module shows as “Custom”.
What to do when a checkbox didn't work
| What you see | Why | What to do |
|---|---|---|
| You turned on an item in the “menu” section, but it didn't appear in the menu | The item shows only together with the right to the window itself | Turn on the window toggle and refresh the page (item and window) |
| Access to a window was removed, but the employee still opens it | The person is also in another department where the window is open (rights add up), or the window isn't in the registry and has no checkbox | Check the person's departments with “Check as employee”; a window without a checkbox closes only via its parent (what the checkbox closes) |
| You cleared “View” for a column, but the value is still there | Only seven windows erase the value, or the column is marked as required | For other windows, close the whole window or the matching button (tables and columns) |
FAQ
How do I hide the purchase price from a content manager?
Only if the window has a button or column with that price: then clear its “View” in the “fields” or “buttons” section. If there's no such checkbox, you can't split access (buttons).
What does an employee see when trying to change a restricted product field?
The cell won't open for editing, and “Set value in bulk” shows “Editing this field is not allowed”. Via v2, such an edit returns error 422 with the same text.
After a change on “Advanced”, the module on “Role” became “Custom”. Is that an error?
No. The module's checkboxes no longer match a level, and the screen shows it (“Custom”). Setting a level on “Role” replaces this manual setup entirely.
How do I give an accountant the “Sign” button without opening document editing?
Keep the “Documents” module at the “View” level and turn on just that button in the “buttons” section of the documents window.
I turned a window off and on again — why did the menu item I removed come back?
The window toggle always gives the item the same state as the window. If you don't need the item, turn it off in the “menu” section after turning the window on (item and window).
Does an employee need to sign in again after checkboxes change?
No. Checkboxes are read every time a window opens: just close and reopen the window or refresh the page (F5).
Where it is and who has access
- Desktop
- the “Users” shortcut → the “Manage groups” button
- Tab
- “Advanced”; from “Role”, the “Details” badge next to a module leads here
- Access right
- the “User group management” window — only for the “Management”
All ways into the rights window, and why it has no menu item, are covered in “Employee access rights”.
Related topics
- For the big picture — employee access rights.
- If it's simpler to open or close a whole module — module levels.
- If you need to restrict other people's customers rather than columns — “Data scope”.
- If you set up the product table columns yourself — the “Base catalog” grid.
