How to configure macro access?

In the parameters of a macro section you can set a short name (alias), mark the macro as available from chat and limit it to skill groups — then only operators of those groups see the macro in the macro list.

When you need it

There are many macros, and operators of different lines need different ones.
A macro changes the status or subject of a request, and only certain teams should run it.
You need a short, stable macro name that is easy to find.

Good to know

A root administrator turns the feature on: Menu → Settings → Instance settings, category Scenario Builder, switch «Macro access: alias, chat and skill groups». While it is off, the modal has no new fields and macro lists work as before.
The alias is unique across the whole instance: two macros cannot share an alias, even in different processes.
Skill groups limit who sees the macro in the list: the «Run macro» dialog, mass run, the old operator panel and CustomData macros. A macro without skill groups is visible to everyone, as before.
A root administrator sees all macros. An administrator who is not in any skill group sees only unrestricted macros.
If a skill group is deleted or disabled, the macro does not disappear — the group simply stops applying to it. The macro remembers a disabled group: once it is enabled again, the restriction applies again.
«Available from chat» is only stored for now: calling a macro from the chat input arrives in a later version.

Before you start

A root administrator has turned the feature on in instance settings.
You may edit scenarios (Scenario Builder).
The skill groups you need already exist in the operator panel settings.

Step by step

1. Open the macro section parameters

Open the process in Scenario Builder.
In the section list click the gear next to the section used as a macro.
Make sure «Used as Macro» is checked — the new fields appear under it.

2. Set the alias

In «Macro alias (short name)» enter a name, for example verify_doc.
Lowercase latin letters, digits, _ and - are allowed, 2 to 32 characters. Capital letters and surrounding spaces are fixed automatically when you leave the field.
«Alias is already in use» under the field means another macro has this alias — choose another one. «Invalid alias» means the name has characters that are not allowed. While there is an error, «Confirm» is disabled.

The alias is optional.

3. Mark «Available from chat»

Turn on «Available from chat». It is active only when an alias is set; clearing the alias turns it off.

4. Limit to skill groups

In «Skill groups with access» choose one or more groups (search is available).
An empty field means «Available to all operators».

5. Save

Click «Confirm», then «Publish».
The alias shows as a /verify_doc badge next to the section in the list and on the macro's start node.

If someone took the same alias while you were editing, publishing shows «Alias is already in use» — change the alias and publish again.

How to change the request status and subject from a macro

No separate action is needed. Add a Request Update node (action_request_update) to the macro and set the status and subject in it — the action applies to the room the macro was run from. The status changes in any room; the subject changes only in ticket requests — in a regular chat the node leaves the subject as is. Action parameters: Request Update node parameters.

What happens next

Operators outside the selected skill groups no longer see the macro in the macro list.
A section copy keeps the same skill groups but has no alias and no «Available from chat» — set the alias again.
Import of a process or section and sections from the marketplace arrive without alias and skill groups: skill group ids differ between instances, so choose the groups again.
Restoring a version brings the alias back only if it is free; skill groups stay as they are now.