External User Groups — Technical Description of the Object (Accounting for Kazakhstan 3.0)

1. Identification

Purpose. The object manages groups of external users (contractors, partners, information providers, individuals with access to the portal/services). It serves to assign roles and access rights to a set of external users, to organize their hierarchical structure, and to limit the types of participants through the attribute “Purpose”. Administrators and security officers work with the object during the initial setup of external access, when adding new external users, and when changing the access organizational structure. When initializing the information base, the system automatically creates a predefined group “All External Users”.

Important note on type. By the composition of attributes and tabular parts (Composition / Roles / Purpose), by forms and by role in the configuration, this is a service catalog of the platform/BSP, not an accounting document. References to the type “Document” in the setup are a classification inaccuracy. Practical consequence: the object is not conducted and does not generate accounting/register movements (see section 5). The attributes “Comment” and “AllAuthorizationObjects” and three tabular parts exactly correspond to the structure of the catalog ExternalUserGroups in BSP.

Where to find in 1C: section “Administration” → “External User Groups”. Navigation link (by setup): e1cib/list/Document.ExternalUserGroups. Actual working link for the catalog: e1cib/list/Catalog.ExternalUserGroups — requires verification in the specific build, depends on what type of metadata the object is registered in your information base.

2. Header Attributes and Tabular Parts

2.1 Header Attributes

2.2 Tabular Part “Composition” (Group Participants)

Stores the list of external users included in the group.

2.3 Tabular Part “Roles”

Defines the set of roles (access rights) assigned to the group; roles apply to all its participants.

2.4 Tabular Part “Purpose”

Specifies the types of external users for which the group is intended (contractors, individuals, etc.).

3. Forms

Separate SelectionForm/GroupForm are not explicitly highlighted — group selection is usually done through ListForm in selection mode.

4. Key Module Procedures

BSL fragments in evidence are not attached, so below are typical handlers of this type of BSP object (actual names and availability depend on the build; key logic for ExternalUserGroups is stable between versions).

Object module:

• FillProcessing — for a new group sets default values, if necessary — types in “Purpose”.
• BeforeWriting — correctness control: if AllAuthorizationObjects is set, the composition of participants cannot be edited manually; checks that the types of participants from “Composition” correspond to “Purpose”; prohibits changing the predefined group “All External Users” in an invalid part.
• OnWriting — membership synchronization: recalculation and recording of service registers of information about users' membership in groups (see section 5), updating the access rights cache.
• BeforeDeletion — reference integrity control, prohibition of deletion of the predefined group.

Element form module:

• OnCreationOnServer — initialization of tabs “Composition/Roles/Purpose”, building a list of roles with checkboxes, setting the availability of elements depending on AllAuthorizationObjects and the rights of the current user.
• Handlers for participant selection commands (SelectParticipants), role management (SetCheckboxes / ClearCheckboxes / filtering), sorting the composition.
• AfterWritingOnServer / NotifyAboutChange — notifying open forms about changes in the composition of access groups.

List form module:

• OnCreationOnServer — setting up hierarchical display, conditional formatting, filtering.

5. Conducting and Movements

The object is not a conducted document and does not generate accounting entries and register movements. This is a service object of the access management subsystem. It has no tabular part of movements, no ConductingProcessing procedure, and does not participate in regulated accounting.

Accordingly, for this object the accounts of the standard chart of accounts of the RK are NOT applicable (1210, 1030, 1330, 3310, 3130, 6010, 7010), tax parameters of Kazakhstan 2026 (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, basic deduction for individual income tax 30 MRP/month and no more than 360 MRP/year, individual income tax 10%/15% with a threshold of 8,500 MRP, OPP 10% with a base cap of 50 MSP, OPPR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%) and electronic documents (ESF/IS ESF, SNT). These indicators relate to accounting documents of the configuration, not to access management objects.

What actually happens upon recording (not conducting):

• Recording of the catalog element and its tabular parts.
• Updating service information registers of the “Access Management” / “Users” subsystem — information about the membership of external users in groups (used by the RLS mechanism for calculating rights). Specific names of registers (for example, the register of membership in user groups) — requires verification according to the composition of the metadata of your BSP build.

6. Related Objects and Input on Basis

Input on basis: the object does not participate in typical “Input on Basis” mechanisms (neither as a basis nor as a result) — this is a service object for access settings.

7. Extension Points

• Configuration extension: adding attributes/commands to ElementForm and ListForm, overriding handlers OnCreationOnServer, BeforeWriting, OnWriting through &Instead / &After / &Before.
• Programmatically overridable BSP modules: access group logic is configured through overridable modules of the “Users”/“AccessManagement” subsystems (…Overridable), not by editing the standard object.
• Event subscriptions: OnWriting/BeforeWriting of the catalog — for integration with external portal/services (synchronization of composition).
• Restriction on changes: the predefined group “All External Users” and the flag AllAuthorizationObjects should not be changed in extensions — this will violate rights calculation.
• Recommendation: do not introduce accounting/tax logic of the RK into this object — documents of regulated accounting of the configuration are intended for this.