"Users Directory (Catalogs.Users) — Technical Description"

1. Identification

Purpose. The catalog stores data about users of the information base (IB). It links IB accounts with individuals of the organization, manages access (through association with roles and access group profiles), stores contact information and service attributes. It is used by administrators and HR specialists for creating, editing, and deactivating employee accounts.

The key feature of the catalog is the two-way integration with the internal user list of the IB platform: each record is synchronized with the platform account through the attribute UserIdentifierIB (name, authentication, password, roles). Therefore, the catalog is not "ordinary" — it cannot be edited independently of the IB user mechanism (BSP subsystem "Users").

2. Attributes of the Header and Table Parts

2.1 Header Attributes

2.2 Table Parts

AdditionalAttributes

Stores user-defined additional fields, configurable through the subsystem "Additional Attributes and Information".

Typically, users of BSP also have a second table part — ContactInformation (phones, addresses, e-mail), implemented through the eponymous subsystem. Its composition is determined by the settings of types of contact information. (Requires verification in the specific build 3.0.74.2 — availability may depend on enabled functional options.)

3. Forms

4. Key Module Procedures

The attached evidence does not provide BSL code, so below are the typical handlers of this type of object (object module / manager module) in BSP configurations. Specific names/lines are clarified according to the source code of build 3.0.74.2.

Object Module (ObjectModule):

• BeforeWriting(Refusal) — control of data correctness, setting service flags, checking rights to modify the IB account; blocking changes to UserIdentifierIB outside the standard mechanism.
• OnWriting(Refusal) — synchronization of catalog properties with IB user properties (login name, roles, authentication) through ServiceUsers / Users BSP.
• BeforeDeletion(Refusal) — deletion/marking of the related IB account, clearing user settings.
• FillingProcessing(FillingData) — initial filling upon creation (Prepared, current user as author).
• FillCheckedAttributes… / FillingCheckProcessing — control of mandatory fields during interactive writing.

Manager Module (ManagerModule):

• BeforeSelectionProcessing, DataRetrievalForm — managing the selection form, hiding inactive/service.
• Procedures for selecting the current user (CurrentUser()), checking administrative rights, working with the IB identifier.

The main business logic for user management is located in the common modules of the BSP subsystem: Users, ServiceUsers, InternalUsers — where creation/linking with IB, setting roles, handling inactivity, and password recovery are implemented.

5. Posting and Movements

The catalog is not a document and does not perform posting — it does not generate accounting entries and movements in accumulation/accounting registers. Accordingly, the chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.) and tax rates (VAT 16%, individual income tax, social contributions 10%, social contributions for retirement 3.5%, social health insurance 2%, social health insurance 3%, social tax 5%, etc.) are not applied within the catalog itself.

Indirect influence on accounting:

• Through Individual the record is linked to an individual, which participates in HR and payroll documents. It is there that the tax norms of the RK for 2026 apply: basic deduction for individual income tax 30 MRP/month (not more than 360 MRP per year), MRP = 4,325 ₸, minimum wage = 85,000 ₸, individual income tax 10% up to 8,500 MRP of annual income and 15% above, ceiling for social contributions — 50 minimum wages.
• As analytics/responsible: the user is recorded in the fields "Author", "Responsible", "Modified" of documents and information registers — this affects selections and reports, but not on monetary movements.
• BSP information registers (not movements of the catalog, but related data): UserSettings, UserAccessGroups, IBUsers, etc. are filled when the user is recorded.

6. Related Objects and Input Based On

Related Objects:

• Catalog.Individuals — through Individual (HR, accruals, individual income tax/social contributions).
• Catalog.AccessGroups and CharacteristicTypesReference.AdditionalAttributesAndInformation — rights and additional attributes.
• Catalog.Subdivisions (or equivalent) — through Subdivision.
• List of IB platform users — through UserIdentifierIB.
• Practically all documents and registers of the configuration refer to the user as the author/responsible.

Input Based On: there is no typical "input based on" that generates documents for this catalog. Service commands are available: setting rights/access groups, copying settings to another user, password recovery, creating an individual based on user data (within the BSP mechanisms).

7. Extension Points

• Additional attributes and information — extending the data composition without changing the configuration (table part AdditionalAttributes + information register "Additional Information").
• Event subscriptions BeforeWriting/OnWriting/BeforeDeletion of the catalog — for external synchronization, logging, integration.
• Overridable common BSP modules (OverridableUsers, OverridableAccessManagement) — standard points for customizing roles, selections, default values.
• Configuration extensions — adding attributes, changing forms (ElementForm, ListForm) and handlers through the extension mechanism without removing from support.
• Additional processing/reports (AdditionalReportsAndProcesses) assigned to the Users catalog.
• Contact information — expanded by adding types of contact information for users.