1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | AccessRights |
| Full Name | Report.AccessRights / Reports.AccessRights |
| Synonym | “Access Rights” (in metadata, the synonym is not defined separately — the name is used) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Mechanism | Data Composition System (DCS) |
| Subsystem | StandardSubsystems.ReportVariants, functionally relates to the access control block |
Purpose. The report “Access Rights” is an analytical and auditing tool for administrators and information security specialists. It provides a detailed picture of the rights of a selected user or access group to metadata objects: assigned roles and profiles of access groups, permitted/forbidden actions (reading, adding, modifying, deleting, viewing, editing), as well as restrictions at the record and field level (RLS). It is used during the initial security setup, access audits, incident investigations, and for documenting the current state of rights according to information security policy requirements.
The report is analytical: it only reads and displays data, does not perform writing or change security settings.
Where to find in 1C:
- Navigation link:
e1cib/list/Report.AccessRights - Interface: section “Administration” → “User and Rights Settings” → service reports on access (or through the “All Reports” panel → administration group / report variants).
2. Attributes of Header and Table Parts
2.1 Header Attributes
In the report metadata, explicit header attributes are not defined (the array attributes is empty). The report is fully managed by the data composition scheme: selection and grouping parameters are set in DCS and variant settings, not through object attributes.
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| (attributes are absent) | — | — | Filtering and parameterization are performed using DCS tools |
Standard DCS parameters through which the report is managed (set in the scheme/settings, not as object attributes):
| DCS Parameter | Purpose |
|---|---|
User / AccessGroup |
Object of analysis — for whom the report is built |
IncludeProfiles |
Expand the composition of access group profiles |
OnlyAllowed |
Show only actions marked as “allowed” |
MetadataObject |
Limit selection to specific metadata objects |
The specific set of parameters is version-specific and is defined by the data composition scheme of the report — this requires verification in the specific delivery 3.0.74.2.
2.2 Table Parts
Table parts are absent. The result is formed directly into a table document based on the composition scheme; intermediate data are not stored in the object structure.
3. Forms
In the report metadata, custom forms are not defined (the array forms is empty). An automatically generated report form is used, managed by the mechanism StandardSubsystems.ReportVariants.
| Form | Source | Purpose |
|---|---|---|
| Report Form (auto) | Generated by the platform + BSL | Selecting a variant, setting parameters/selections, generating and printing the result |
| Report Variant Form | Subsystem “Report Variants” | Saving and selecting user layout settings |
| Settings Form | Subsystem “Report Variants” | Extended configuration of structure, selections, and DCS formatting |
4. Key Procedures of Modules
BSL code in the reference evidence is not attached, therefore below are typical handlers for the report in DCS, integrated with BSL (actual signatures are verified in the specific delivery).
Report Object Module:
OnResultComposition(DocumentResult, DataDecoding, StandardProcessing)— intercepts standard composition; here, if necessary, standard processing is disabled and the result is programmatically filled with data about rights (collection of roles, actions, RLS restrictions for the selected user/group).DefaultDataCompositionSettings()/ initialization of the scheme — setting initial parameters, selections, and structure.
Form Module (for BSL implementations):
OnCreateOnServer(Refusal, StandardProcessing)— callsReportsServer.OnCreateOnServer(...)for integration with the report variants subsystem and setting up the command interface.OnLoadVariantOnServer(Settings)— additional configuration of the form for the selected report variant.
General Module/Report Manager:
ReportSettings(Settings, ReportSettings)— registration of report variants in the “Report Variants” subsystem, description of available variants and their visibility.
The presence of a custom
OnResultCompositionis version-specific: if the report is fully declarative, the handler may be absent, and all logic is implemented in the DCS scheme.
5. Posting and Movements
Not applicable. The object is a report, not a document: it is not posted, does not generate records in registers, and does not create accounting entries. The report only reads metadata rights and access settings and outputs the result in a table document.
Accordingly, this object does not relate to either the chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010), nor tax calculations (VAT 16%, PIT 10/15%, social contributions), nor electronic documents (ESF, SST) — they are used by accounting documents of the configuration, but not by the access rights report.
6. Related Objects and Input Based On
Input based on for the report is not provided (this is not a document). Functionally, the report is related to the following objects of the access control block:
| Object | Role in Interaction |
|---|---|
| Directory “Users” | Source of the subject of analysis |
| Directory “Access Groups” | Grouping of rights, assignment of profiles |
| Directory “Access Group Profiles” | Set of roles and restrictions displayed in the report |
| Roles (metadata objects) | Primary source of rights for actions with objects |
| Information Registers of the Access Subsystem | Storage of assigned profiles/groups and RLS parameters |
| Subsystem “Report Variants” | Storage and selection of layout settings |
7. Extension Points
- Report Variants. Creation of user variants through the “Report Variants” subsystem (without changing the configuration) — additional groupings, selections, conditional formatting.
- Configuration Extension. Adding custom fields/data sets to the DCS scheme or intercepting
OnResultCompositionin the extension for additional filtering (for example, only for certain metadata subsystems). - DCS Settings. User selections, sorting, and conditional formatting without programming.
- Integration with BSL. Registration of additional variants in
ReportSettingsof the report manager; connection to the mechanism for sending/saving reports. - Rights to the report itself. Visibility of the report is regulated by roles — access to it should be restricted by administrators and information security officers, as it reveals the rights map of the system.