1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | ExternalUsers |
| Full Name | Catalog.ExternalUsers / Catalog.ExternalUsers |
| Synonym | External users |
| Configuration | 1C:Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Hierarchy | Hierarchy of groups (external users are grouped for rights assignment) |
| Owner | No (independent catalog) |
| Purpose | Accounting and management of external users of the information base — individuals or legal entities who are not employees of the organization but have limited access to the information base (counterparties, partners, auditors, clients). Each external user is linked to an authorization object (for example, an element of the catalog "Counterparties") and may have their own information base user with configured access rights. |
Object Characteristic. This is a service catalog of the "Users" subsystem (part of the standard subsystem libraries). It does not participate in accounting, does not generate entries and movements in registers, and is not related to tax calculations. The catalog is used by administrators during the initial setup of access and is rarely changed in current operations. The list form supports filtering by user types and groups and automatically hides invalid (deleted) users when selected.
2. Attributes of Header and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Invalid | Boolean |
Not checked | Flag for archiving/blocking the user. When set, the user is excluded from selection lists and cannot log into the system. |
| AuthorizationObject | Arbitrary reference type (composite) | Mandatory (ShowError) | Reference to a business logic object (counterparty, organization, etc.) associated with the external user. Used for identification and access rights assignment. |
| SetRolesDirectly | Boolean |
Not checked | Flag for direct role assignment to the user, bypassing group settings. Protected from changes during group editing. |
| Comment | String |
Not checked | Arbitrary text note about the user, does not affect business logic. |
| Prepared | Boolean |
Not checked | Service flag indicating the user's readiness for work. Set after synchronization with the information base user. Cannot be manually reset after being set (protection against inconsistent changes). |
| UserIDInIB | UniqueIdentifier (UUID) |
Not checked | Unique identifier of the associated information base user. Automatically filled during creation/synchronization, controlled for uniqueness. |
| UserIDInService | UniqueIdentifier (UUID) |
Not checked | User identifier in the service (for cloud solutions). Automatically filled, controlled for uniqueness. |
| DeleteUserPropertiesInIB | ValueStorage |
Not checked | Deprecated attribute (marked as "not used"). Previously stored settings for the information base user. Left for compatibility with previous versions. |
Standard attributes of the catalog: Name (user representation), Code, Parent (group), DeletionMark, Predefined.
2.2 Table Parts
AdditionalAttributes
Purpose: to store arbitrary additional characteristics of the external user, configurable by the user (phones, addresses, other attributes). An extensibility mechanism without changing the configuration.
| Name | Type | Purpose |
|---|---|---|
| Property | CharacteristicTypes.AdditionalAttributesAndInformation |
Reference to the description of the additional attribute (data type, name, mandatory). |
| Value | Arbitrary type | Value of the additional attribute (type determined from the property). |
| TextString | String |
Representation of the value as text (for unlimited strings and special data types). |
3. Forms
The forms section in the attached evidence is not detailed (2.3 Forms …). Below is the typical composition of forms for the catalog "ExternalUsers" of the "Users" subsystem of the standard subsystem libraries:
| Form | Purpose |
|---|---|
| ElementForm | Card of the external user: authorization object, "Program access allowed" flag, information base user settings (login, authentication), role/group access assignment, "Invalid" flag, additional attributes, and comment. |
| GroupForm | Card of the group of external users: name, type of authorization object, composition of participants. Used for group access rights assignment. |
| ListForm | Hierarchical list of external users and their groups with filtering by type/group; invalid users are hidden by default. |
| SelectForm | Selecting an external user in other objects; automatically filters out invalid users. |
"Requires verification": the exact list of custom forms and their naming in the specific build 3.0.74.2 is version-specific (some forms may be used from common modules/extensions of the standard subsystem libraries).
4. Key Procedures of Modules
BSL code in the attached evidence is absent. Below are typical handlers of this type of object (object module / manager module), characteristic for the catalog "ExternalUsers" of the standard subsystem libraries:
Object Module:
FillProcessing— initialization of a new user, setting default values.BeforeWriting— control of the correctness of the link with the authorization object; checking that a duplicate external user is not created for one authorization object; synchronization of service flags (Prepared, identifiers).OnWriting— writing/updating the associated information base user (ServiceUsers.WriteChanges…), updating access groups.BeforeDeleting— deleting the associated information base user and clearing access rights settings.FillCheckProcessing— control of filling the mandatory attributeAuthorizationObject(ShowError).
Manager Module:
GetFormProcessing— substitution/selection of the required form.- Procedures for regulatory operations synchronizing external users with information base users (from common modules
ServiceUsers,ExternalUsers).
The logic of managing information base users, roles, and access groups is primarily implemented in the common modules of the "Users" subsystem (
Users,ExternalUsers,ServiceUsers,AccessManagement), rather than in the module of the catalog itself.
5. Posting and Movements
The catalog is not a document and does not perform postings: it does not generate accounting entries and movements in accumulation/accounting registers.
Side effects of writing an element only affect the service mechanisms of the platform and access subsystem:
- creation/modification of the information base user record (
InformationBaseUsers); - updating service information registers of the access rights subsystem (for example, "AccessGroups", "GroupAccessUsers", RLS access value sets);
- writing values of the table part "AdditionalAttributes" into the linked properties mechanism.
References to the chart of accounts of the RK and tax parameters of Kazakhstan 2026 (VAT rate 16%, MRP 4,325 ₸, MZP 85,000 ₸, basic deduction of individual income tax 30 MRP/month and no more than 360 MRP/year, individual income tax 10%/15%, OPP 10%, OPPR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%; accounts 1210/1030/1330/3310/3130/6010/7010; ESF/SNT) do not apply to this object — it lies outside the scope of accounting and tax accounting. These indicators are used in sales, receipts, payroll, and tax calculations documents, not in the service catalog of users.
6. Related Objects and Input Based On
| Connection | Object | Nature of Connection |
|---|---|---|
| Authorization Object | Catalog.Counterparties, Catalog.Organizations, etc. (composition determined by the type of attribute) |
Each external user is linked to a business logic element; used in RLS to restrict data visibility. |
| IB User | InformationBaseUsers (platform) |
One external user ↔ one IB user (by UserIDInIB). |
| Access Groups | Catalog.AccessGroups, access group profiles |
Rights assignment through membership in groups or directly (flag SetRolesDirectly). |
| Additional Attributes | CharacteristicTypes.AdditionalAttributesAndInformation |
Extendable attributes through the table part "AdditionalAttributes". |
| Groups (Hierarchy) | Catalog.ExternalUsers (groups) |
Hierarchical grouping for group rights assignment. |
Input Based On: not provided for the service catalog. Element creation is performed manually by the administrator from the list form or programmatically during synchronization with external systems/services.
7. Extension Points
- Additional attributes and information — standard way to add attributes to the external user without changing the configuration (through table part and characteristic types).
- Configuration extensions — overriding form handlers (
ElementForm,GroupForm) and adding attributes/commands without removing from support. - Common modules of the standard subsystem with the suffix "Overridable" — for example,
UsersOverridable,AccessManagementOverridable: configuring rules for filling roles, composition of authorization objects, and access profiles. - Event subscriptions — processing
BeforeWriting/OnWriting/BeforeDeletingfor integration with external identification systems. - Record-level access restriction (RLS) — through the attribute
AuthorizationObject, the external user gains access only to "their" data; logic is configured in the "AccessManagement" subsystem.
"Requires verification": the specific composition of overridable modules and integration points depends on the version of the standard subsystem supplied in build 3.0.74.2.