--- title: "Directory \"Access Groups of Individuals\" — Accounting for Kazakhstan 3.0" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-gruppydostupafizicheskihlic-buhgalteriya-dlya-en source: BuhGPT --- # Directory "Access Groups of Individuals" — Accounting for Kazakhstan 3.0 > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name AccessGroupsOfIndividuals Full Name Catalog.AccessGroupsOfIndividuals Alias — (matches the name) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Type Hierarchical (hierarchy of groups and element --- 1. Identification Parameter Value Object Type Catalog Name AccessGroupsOfIndividuals Full Name Catalog.AccessGroupsOfIndividuals Alias — (matches the name) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Type Hierarchical (hierarchy of groups and elements) Owners No (independent catalog) Purpose Service catalog of the rights management subsystem. Groups individual users into access groups with unified rights to functions and data of the configuration. Used by administrators during initial setup, adding employees, and changing the organizational structure. Where to find in 1C: section "Administration" → "Access Groups of Individuals". Navigation link: e1cib/list/Catalog.AccessGroupsOfIndividuals The catalog is a service element of the access management mechanism. It does not participate in accounting operations (no postings, no movements in accounting registers), therefore the tax parameters of the RK (VAT rate, MRP, individual income tax deductions, etc.) do not apply to this object — they are implemented in accounting documents and calculation registers, not here. 2. Attributes and Table Parts 2.1 Header Attributes User-defined attributes in the metadata are not defined — the catalog uses only standard attributes of 1C catalogs. Name Type Mandatory Purpose Code String No Unique access group code for identification Name String Yes Name of the access group (e.g., "Accountants", "HR Specialists") Parent Catalog.AccessGroupsOfIndividuals No Reference to the parent group for building the hierarchy 2.2 Table Parts Table parts are absent. The structure of the catalog is simple, without additional tabular data. 3. Forms The catalog contains five forms: Form Purpose ListForm Main form of the access groups list (56 UI elements). Viewing, searching, creating, and ordering groups in the hierarchy. ElementForm Key form for creating and editing a specific access group (13 elements). Main working place for the administrator. GroupForm Editing the node-group in the hierarchy (13 elements). Used when the element is a group (folder). SelectionForm Selecting a group from the list when substituting in other objects (50 elements). GroupSelectionForm Alternative form for selecting a specific group (folder) in the hierarchy (23 elements). 4. Key Module Procedures Evidence in the text of the modules (BSL) is not attached — below are the typical handlers characteristic of a service hierarchical catalog of this type. Specific lines should be clarified by the version code 3.0.74.2. Object Module (ObjectModule): - BeforeWriting(Refusal) — control of correctness before writing: checking for the inadmissibility of circular hierarchy (a group cannot become its own parent), control of filling in the name. - OnCopying(CopyingObject) — resetting service fields when copying an element. - FillingProcessing(FillingData, FillingText, StandardProcessing) — default filling when creating. Form Modules (ElementForm, ListForm): - OnCreateOnServer(Refusal, StandardProcessing) — setting visibility and availability of form elements, establishing restrictions on administration rights. - BeforeWritingOnServer(Refusal, CurrentObject, WritingParameters) — server-side validation before writing from the form. - AfterWritingOnServer(CurrentObject, WritingParameters) / AfterWriting(WritingParameters) — updating related access data after saving. "Requires verification" (version-specific): the exact composition of procedures for synchronizing user rights with the access group in 3.0.74.2 may differ — confirmed by the object module of the specific version. 5. Posting and Movements The catalog is not posted and does not generate movements in accounting registers or postings according to the chart of accounts. As a service object of the access mechanism, it only affects: - Composition of user rights — through related registers/mechanisms of the access management subsystem (affiliation of individuals to groups). No accounts from the standard chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010) and electronic documents (ESF, SNT) are involved by this catalog — this logic is implemented in the accounting documents of the configuration. 6. Related Objects and Input Based On - Individuals / users — elements of the catalog group individuals for assigning unified rights; references to the group are used in the access management subsystem. - The catalog itself (Parent) — recursive link for building the hierarchy of groups. - Input based on — not provided: the service catalog is not a basis for documents and is not created based on other objects. 7. Extension Points - Configuration extension: adding custom attributes (e.g., comment, responsible person, validity period of the group) through catalog extension without removing from support. - Form handlers: intercepting OnCreateOnServer, BeforeWritingOnServer in the extension ElementForm for additional validation or auto-filling. - Object module: enhancement of BeforeWriting for additional business rules (prohibition of deleting system groups, control of name uniqueness). - Event subscriptions: BeforeWriting/OnWriting/BeforeDeleting of the catalog for auditing changes in the composition of access groups. - Roles and RLS: integration of the group into access restrictions at the record level when customizing the rights model. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_