1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | AccessGroupSets |
| Full Name | Catalog.AccessGroupSets |
| Synonym | Access group sets |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Subsystem | Access Management (standard subsystem of BSL "Users"/"Access Management") |
| Object Nature | Service (technical), filled automatically by the platform/BSL mechanisms |
Purpose. The catalog stores predefined combinations (sets) of access groups that are assigned to users or external users of the system. Its task is to speed up and standardize the distribution of rights: instead of listing the same group of groups for each user, the set is created once and assigned in full. The catalog works in conjunction with the catalogs "Access Groups", "Users", "External Users", as well as with the identically named groups of users/external users. It is mainly used by administrators when configuring rights; it does not participate in everyday accounting work (sales, purchases, VAT, payroll) and does not affect the regulated accounting of the RK.
Important: this is a service object of the access control mechanism. It is not related to the chart of accounts of the RK, tax rates (VAT 16%, PIT, ESI, social tax, etc.) and does not participate in electronic document flow (ESF/SNT). National accounting parameters do not apply to this catalog.
Where to find in 1C: section "Administration" → "User and Rights Settings" → service data of the access management subsystem. Direct navigation link: e1cib/list/Catalog.AccessGroupSets.
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| ForExternalUsers | Boolean | Not checked | Indicates that the set is intended for external users (not for regular users of the information base) |
| ElementTypeOfSet | CatalogReference.AccessGroups / ExternalUsers / Users | Not checked | Determines the type of elements included in the set (access groups, users, or external users) |
| Hash | Number | Not checked | Checksum (hash code) of the set composition for quick identification of sets without line-by-line comparison of the table part |
| NotUsedSince | Date and time | Not checked | Date/time from which the set is considered outdated; used for archiving irrelevant sets |
| User | CatalogReference.ExternalUsers / Users | Not checked | Reference to a specific user or external user for whom the set was created |
| AllowedAccessGroupSet | CatalogReference.AccessGroupSets | Not checked | Reference to an allowed (approved) access group set for comparison/control of changes |
| AllowedUserGroupSet | CatalogReference.AccessGroupSets | Not checked | Reference to an allowed (approved) user group set for comparison/control of changes |
| NewAccessGroupSet | CatalogReference.AccessGroupSets | Not checked | Reference to a new (proposed) access group set planned to be applied instead of the current one |
| NewUserGroupSet | CatalogReference.AccessGroupSets | Not checked | Reference to a new (proposed) user group set planned to be applied instead of the current one |
Standard attributes of the catalog: Code, Name, DeletionMark, Predefined. The attributes Parent/Owner are not used for this catalog (flat, non-hierarchical, not subordinate).
2.2 Table Parts
Groups — stores a list of access groups (or user/external user groups) included in the set.
| Name | Type | Purpose |
|---|---|---|
| Group | CatalogReference.AccessGroups / ExternalUserGroups / UserGroups | A specific group included in the set; the actual type is determined by the value of the attribute ElementTypeOfSet |
The logic of set identity: the composition of rows in the table part Groups calculates the Hash. This allows finding an already existing set with an identical composition and reusing it without creating duplicates.
3. Forms
The service catalog of the access management subsystem has a minimal set of forms; its own significant forms are usually not set and automatically generated by the platform:
| Form | Purpose |
|---|---|
| List Form (auto) | View the list of sets by the administrator; service access through e1cib/list/Catalog.AccessGroupSets |
| Element Form (auto) | View the composition of a specific set (header attributes + table part "Groups") |
| Selection Form (auto) | Selecting a set in other objects of the access management mechanism |
Requires verification in the specific version 3.0.74.2: the presence of a custom managed element/list form — the composition of forms for service objects of BSL changes between releases.
4. Key Module Procedures
No application BSL code (evidence by modules) for this object is attached, so below are typical handlers for the service catalog of BSL. The main business logic is moved to the common modules of the "Access Management" subsystem, not to the module of the catalog itself.
Object Module (typical handlers):
BeforeWriting— recalculation of the attributeHashbased on the current composition of the table partGroups; control of the correctness ofElementTypeOfSetrelative to the types of rows.FillingHandler— initialization of a new set (element type, attributeForExternalUsers).FillingCheck— usually minimal: mandatory attributes for the service object are not checked.
Subsystem Level Logic (common modules "Access Management"/BSL):
- Searching for an existing set by
Hashand composition for reuse (elimination of duplicates). - Updating sets when changing user membership in access groups/user groups.
- Marking outdated sets by filling
NotUsedSinceinstead of physical deletion. - Comparing "allowed" and "new" sets (
AllowedAccessGroupSet/NewAccessGroupSetand similar for users) for control and application of rights changes.
5. Posting and Movements
The catalog is not a document and is not posted: it does not generate accounting entries and movements in accumulation/information registers of the accounting circuit. Accordingly, the accounts of the typical chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010) and tax movements (VAT 16%, PIT, ESI 10%, ESI 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%) are not applicable to this object.
The only "movements" related to the object are service: records are used by the record-level access restriction mechanism (RLS) to determine which data is accessible to which users. Sets participate in filling service registers of the access management subsystem (for example, information registers "Access Value Sets of Access Groups"/user membership), not in registers of regulated accounting.
6. Related Objects and Input Based On
Related catalogs and objects:
Catalog.AccessGroups— source of set elements whenElementTypeOfSet = AccessGroups.Catalog.Users,Catalog.ExternalUsers— recipients of sets (attributeUser, attributeForExternalUsers).Catalog.UserGroups,Catalog.ExternalUserGroups— possible types of rows in the table part "Groups".- Service registers of the "Access Management" subsystem — consumers of set data for rights calculation (RLS).
Input Based On: not provided — the object is filled automatically by BSL mechanisms, not manually by the operator and not through the "Input Based On" mechanism.
7. Extension Points
- Configuration Extension: adding custom attributes/table parts is possible but not recommended — the object is service and actively maintained by BSL code; changes may conflict with the logic of recalculating
Hashand updating sets. - Overridable common modules of the "Access Management" subsystem (
AccessManagementOverridableand analogs) — the standard way to influence the composition of groups/sets and access rules without modifying the catalog itself. - Event subscriptions (
BeforeWriting/OnWriting) — use with caution to avoid disrupting the service hash recalculation and synchronization of sets. - Update during release migration: when transitioning between versions of BSL, a restructuring of sets may occur; customizations should be designed to be resilient to mass recreation of elements.