--- title: "Report \"User Information\" (Reports.UserInformation) — Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/otchet-svedeniya-o-polzovatelyah-reports-svedeniyaopolzov-en source: BuhGPT --- # Report "User Information" (Reports.UserInformation) — Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Report Name UserInformation Full Name Report.UserInformation Synonym “User Information” (no custom synonym defined in evidence) Configuration Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) Mechanism Basis Data Composition Sy --- 1. Identification Parameter Value Object Type Report Name UserInformation Full Name Report.UserInformation Synonym “User Information” (no custom synonym defined in evidence) Configuration Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) Mechanism Basis Data Composition System (DCS) Purpose. Administrative report for obtaining detailed information about users and external users of the information base. Used by administrators and information security specialists for auditing access rights, controlling authentication methods (standard, OpenID, OpenID-Connect, access token), and analyzing user login status. Generated on request; belongs to the user administration subsystem and is not related to accounting calculations (VAT, PIT, contributions, etc.) — this is purely an infrastructure report. Where to find: - Interface: section “Administration” → “User Information”. - Navigation link 1C: e1cib/list/Report.UserInformation 2. Header Attributes and Table Parts The report does not have its own metadata attributes and table parts — the entire output structure is defined by the data composition scheme. 2.1 Header Attributes Name Type Mandatory Purpose (none) — — The attribute table is empty; the report is managed only by the parameters and settings of the DCS 2.2 Table Parts Name Purpose (none) The result is generated by the DCS mechanism and output to a tabular document 2.3 Data Output by Report (DCS Dataset) Fields are taken from system metadata objects and user directories. Typical composition: Field Source Meaning User / External User Directory.Users, Directory.ExternalUsers Information base account Full Name directory attribute Full name / title Program Access Allowed IB user attribute Account activity Authentication Method IB user properties Standard / OpenID / OpenID-Connect / Access token OS Authentication IB user properties OS username during domain authentication Roles / Access Profiles RLS subsystem “Users” Set of rights/access groups Invalid directory attribute Marked as outdated Contact Information “Contact Information” subsystem E-mail, phone, etc. 3. Forms Form Type Purpose Main Report Form Managed report form (standard) Setting variant, input selection, launching generation, and outputting result to a tabular document No explicitly listed forms in the metadata — the standard managed report form of the platform is used. The default composition variant is “UserInformationAndExternalUsers”. Opening the user form is done through the report manager handler (see p. 4). 4. Key Procedures of the Module The object module of the report does not carry business logic; the key logic is concentrated in the manager module. Procedure/Handler Location What it does HandleGetForm Report manager module Intercepts the report form retrieval and substitutes the required (main) form/variant when opening from the interface — a key point that determines which form the user sees Other typical handlers of this type of object that may be present in the object module/scheme: - OnResultComposition — intervention in the composition process (layout adjustment, programmatic filling). - OnVariantUploadToServer / OnUserSettingsUploadToServer — adjustment of variant settings during upload. - BeforeVariantUploadToServer — compatibility processing of saved variants. Requires verification in the specific version: the exact list of object module procedures and the appearance of the DCS scheme depend on the BSP library supplied with release 3.0.74.2. 5. Posting and Movements The report is not posted and does not generate movements in registers, and does not create accounting entries. This is an object of type “Report”: it only reads data and outputs it to a tabular document. Accordingly, it does not relate to typical mechanisms of the accounting part of the RK configuration — accounting register, accounts of the RK chart of accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010), VAT calculation at a rate of 16%, PIT, OPE/OPEP/VOSMS/OSMS/SO and social tax, electronic documents ESF/SNT. All these mechanisms belong to accounting documents of the configuration, not to the administrative report on users. The data sources of the report are not accounting registers, but system objects of the platform and directories: Directory.Users, Directory.ExternalUsers, properties of IB users (IBUsers), subsystems “Users” and “Contact Information”. 6. Related Objects and Input Based On - Directories: Users, ExternalUsers — the main source of rows. - BSP Subsystems: “Users” (roles, access group profiles, RLS), “Contact Information”. - Platform Mechanisms: list of IB users, authentication methods. - Input Based On: not applicable — reports do not participate in the input based on mechanism and are not a basis for other objects. 7. Extension Points - Data Composition Scheme / Report Variants — adding custom fields, groupings, selections, and user variants without changing the code. - HandleGetForm (manager module) — substitution/adjustment of the opened form. - OnResultComposition — programmatic refilling or post-processing of the result. - Configuration Extension — adding form attributes, commands, event handlers of the report form without removing from support. - Subscriptions/redefinable BSP modules of the “Users” subsystem — influence on the composition of available users and rights reflected in the report. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_