RUKKENZH
Ask AI
Sections1C configuration objects
External Users Groups" catalog (Trade Management for Kazakhstan 3.4)
Article language:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH
Article version:📘 For accountants⚙️ For technical specialists

External Users Groups" catalog (Trade Management for Kazakhstan 3.4)

Applies to: 1С:Управление торговлей для Казахстана, release 3.4.5.21 (9 July 2026) · by 1C-Sapa Group, 1C partner
СТ
Сапа Т.И. — 1C and accounting expert, practising trainer
Prepared by the BuhGPT editorial team

1. Identification

Parameter Value
Object type Catalog
Name ГруппыВнешнихПользователей
Full name Справочник.ГруппыВнешнихПользователей
Synonym "External User Groups"
Configuration Trade Management for Kazakhstan, ed. 3.4.5.21
Subsystem "Users" (mechanism from the Standard Subsystems Library, SSL)
Hierarchy Item hierarchy (groups can be nested within each other)
Owner None (independent catalog)
Main presentation By description
Purpose Grouping of external users who have identical access to system data. Used in the record-level access restriction mechanism (RLS) and when configuring rights for external users (partners, counterparties, individuals working through the web client/personal cabinet).

Where to find: navigation link e1cib/list/Справочник.ГруппыВнешнихПользователей. In the interface — section Master Data and Administration → User and Rights Settings → External Users → External User Groups (available when the "External users" option is enabled).

The catalog is a service object: it does not participate in inventory, cash, or tax accounting. Application objects of TM (sales, e-invoices (ESF), waybills (SNT), VAT 16% calculations, IIT, MPC, etc.) do not reference it — it serves only the security and access control subsystem.


2. Header attributes and tabular sections

Header attributes

Attribute Type Purpose
Наименование String Group name (standard attribute).
Родитель CatalogRef.ГруппыВнешнихПользователей Reference to the parent group (item hierarchy).
ВсеПользователи Boolean Flag of the predefined group that automatically includes all external users. Usually set only for one predefined group "All external users"; its composition is not edited manually.
Комментарий String (unlimited) Free-text description of the group's purpose.

Tabular sections

Tabular section Columns Purpose
Пользователи ВнешнийПользователь (CatalogRef.ВнешниеПользователи) Explicit list of external users included in the group. Not filled in when the ВсеПользователи = True flag is set.
Назначение ТипПользователя (Type / DefinedType) Restricts which type of owner object (Partners, Counterparties, Individuals, etc.) external users may have to be included in the group. Used by the form to filter the picker and to validate the composition.

Requires verification for the specific build 3.4.5.21: the exact set of columns in the Назначение tabular section and the presence of service attributes (e.g., the "Group participates in task assignment" flag) depend on the version of the embedded SSL. The core (hierarchy, ВсеПользователи, the Пользователи tabular section) remains unchanged between versions.


3. Forms

Form Type Purpose
ФормаЭлемента Item form Main group form: name, parent, comment, and editing the composition (the "Users" table). Contains commands for picking/adding external users taking into account the restrictions of the Назначение attribute.
ФормаСписка List form View the hierarchical list of groups; navigate to composition; create/copy groups. Opened via the navigation link.
ФормаВыбора Selection form Select a group from other objects and rights settings.

A separate group (folder) form is not required — the hierarchy is built at the item level, so editing is done through ФормаЭлемента.


4. Key module procedures

No separate application BSL code is attached in the evidence, so below are the standard handlers for this SSL object type. In the standard configuration code, the logic is placed in common modules of the "Users" subsystem (ВнешниеПользователи, ПользователиСлужебный, ПользователиВнутренние).

Object module (Справочник.ГруппыВнешнихПользователей.МодульОбъекта):

  • ОбработкаЗаполнения — fills default attributes when creating a new group.
  • ПередЗаписью — validity control: prohibits manual modification of the composition of the predefined "All external users" group (ВсеПользователи = True), checks the composition against the specified Назначение, prevents hierarchy loops.
  • ПриЗаписи — calls the service method for updating the denormalized group composition (recalculating members taking into account nested groups) and subsequently updates RLS access keys/sets.
  • ПередУдалением — checks references and prohibits deletion of the predefined "all external users" group.

Item form module (ФормаЭлемента):

  • ПриСозданииНаСервере — blocks editing of the composition for the "All external users" group, configures element availability according to the current user's rights.
  • External user selection handlers (ПользователиНачалоВыбора / the "Select" command) with a filter by the Назначение attribute.
  • ПослеЗаписиНаСервере — notifies of composition changes to update related forms.

Common modules (serving the catalog):

  • ВнешниеПользователи — programmatic API: getting a user's groups, checking membership, updating composition.
  • ПользователиВнутренние / ПользователиСлужебный — recalculates the group composition register and updates RLS data.

5. Posting and movements

The catalog is not a document and is not posted — it does not generate ledger entries or movements in application accumulation registers. Accordingly, the accounts of the standard Kazakhstan chart of accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010) and tax calculations (VAT 16%, IIT, MPC 10%, MPCE 3.5%, OSMC 2%, OSMC 3%, SC 5%, social tax 6%) do not apply to it — this is an object of the security subsystem, not accounting.

The only "movement" triggered by writing an item is the update of service data for the access restriction mechanism:

What is updated Purpose
Information register СоставГруппВнешнихПользователей (independent, denormalized) Flat list of "Group ↔ ExternalUser" pairs, expanded taking into account nested groups and the ВсеПользователи flag. Used in RLS templates for quick verification of an external user's membership in a group.
Access value sets / access keys (RLS) Recalculated when the composition changes so that rights changes take effect without a restart.

The recalculation is performed on the server when the item is written (ПриЗаписи → SSL service methods).


6. Related objects and input based on

Related objects:

  • Справочник.ВнешниеПользователи — items in the group composition (external users are created based on partners, counterparties, individuals).
  • Справочник.ГруппыПользователей — similar mechanism for internal (staff) users.
  • РегистрСведений.СоставГруппВнешнихПользователей — denormalized composition for RLS.
  • Objects of the "AccessManagement" subsystem: profiles, access groups, access keys/sets — use external user groups as access values.

Input based on: not provided (neither as a basis nor based on other objects). Created manually in the list or programmatically via the ВнешниеПользователи API.


7. Extension points

  • Configuration extension: adding attributes/commands to ФормаЭлемента and ФормаСписка, intercepting object module handlers via &После / &Вместо annotations (with caution — the logic is tightly coupled to the SSL core).
  • SSL programmatic API: methods of the common module ВнешниеПользователи (getting a user's groups, checking membership, programmatic management of composition) — the preferred integration method instead of working directly with the catalog.
  • Additional attributes and information: the "Properties" subsystem allows the group to be extended with additional attributes without changing metadata (requires including the object in the set of additional information types).
  • RLS mechanism: custom access restriction templates can rely on the СоставГруппВнешнихПользователей register when developing industry-specific data visibility restrictions for partners/counterparties.
  • Event subscriptions on catalog writes — for integration with external access management systems (e.g., synchronizing group composition).

Requires verification during customization: the signatures of the "Users" subsystem service procedures belong to the internal SSL API and may change between platform/library releases — reliance should be placed on documented export methods of the ВнешниеПользователи module.

Frequently asked questions

Does the "External User Groups" catalog generate postings and participate in VAT/IIT accounting?
No. It is a service object of the security subsystem. It is not posted, does not generate movements on the chart of accounts of the Republic of Kazakhstan, and does not participate in tax calculations (VAT 16%, IIT, MPC, etc.). When recorded, it only updates the "External User Group Composition" information register and RLS data.
How do external user groups differ from user groups?
External user groups combine elements of the "External Users" catalog (partners, counterparties, individuals working through the personal account/web client), while "User Groups" combine staff (internal) users of the information base. Both mechanisms are used for access delineation, but for different categories of users.
How do all external users end up in a group at once?
The predefined group has the attribute AllUsers = True ("All external users") set. Its composition is not edited manually — all external users are automatically considered to be included in it. For other groups, the composition is set explicitly in the "Users" tabular section, taking into account the restriction by the "Purpose" attribute.
What is the correct way to programmatically work with group composition?
Through the export methods of the "ExternalUsers" common module (membership check, retrieving groups, managing composition), rather than direct writing to the catalog. This ensures the correct recalculation of the denormalized "External User Group Composition" register and RLS access keys.

Read also

Latest answers

Sources

Was this article helpful?
💼 Need help with 1C or accounting? Слава КВЦ — many years of 1C practice in Kazakhstan. Explore the annotated Tax Code of RK 2026 or ask in the BuhGPT chat — answers in seconds.