Checked on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
A new accountant has started working. He needs to access the database, but he doesn't have his own login — and working under someone else's is not allowed: later, it will be unclear who conducted the document and who modified it. Conversely, an employee has left, but their account is still active, allowing anyone to access the database through it. Both cases are resolved in one place — in the directory "Users". Here you create, disable, and configure those who have the right to open your information database.
Just a note: this is a reference directory, not a document. It does not create entries, does not make accounting entries, does not generate electronic invoices (ESF) or tax return forms, and does not have printed forms in the usual sense. Its purpose is to manage accounts and rights. Below, this is honestly stated in the relevant sections, and the structure is preserved for your familiarity.
1. Purpose
The "Users" directory stores a list of those who can access the database. For each user, a login name, authentication method (password), connection to a natural person, and a set of rights through access groups are specified. This is how 1C understands who to allow into the program and what this person is permitted to see and change.
2. Where to find
Path in the interface:
- Reference Information and Administration (or the Administration section) → User and Rights Settings → Users.
- The "Create" button opens a new user card.
To open the list directly in 1C: Service → "Go to navigation link" and paste:
e1cib/list/Directory.Users
Important: the section is only visible to those who have administrative rights. If the "Users" item is missing — you do not have sufficient rights, please contact the database administrator.
2a. How to find out your release
"Help" → "About the program" (or the ℹ icon in the upper right corner). In the opened window, you will see:
- platform version (for example, 8.3.24.xxxx);
- configuration release — "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)".
Always check the release: the interface and the set of rights settings change between versions.
3. How to fill out
The user card is divided into the "Main" tab and subordinate links (rights, settings). Let's break it down by fields.
| Field | Required | Purpose and what happens in case of error |
|---|---|---|
| Full name | Yes | Full name as it appears in lists, in the "Responsible" field, in document signatures. Write a proper "Ivanova Maria Petrovna" — this is how the author of the entry will be searched later. |
| Login name | Yes | Login. This is what the person enters at startup. It must be unique. If left blank — login/password access will not work. |
| Natural person | Recommended | Connection to the "Natural Persons" directory. Contacts are pulled through it, and the employee is correctly identified as responsible. If not filled in — you will have to enter contacts manually, and there will be no connection "user ↔ employee". |
| Access to the program allowed | Yes (checkbox) | The main "switch". If unchecked — the card exists, but the person will not be able to enter the database. This is what is unchecked upon dismissal instead of deletion. |
| 1C:Enterprise authentication | Yes, if login by password | Enables login by username and password. Here you set the password, check "Require password change on first login" (the employee will set their own upon first entry) and, if necessary, "User is prohibited from changing password". |
| Operating system authentication | No | Login via Windows account without entering a password. Convenient, but ties to a specific PC/domain. |
| OpenID authentication | No | For login through an external identification service. Rarely used in standard operations. |
| Show in selection list | No | If unchecked, the login will not be displayed in the dropdown list at database startup — it will have to be entered manually. Useful for "technical" and service accounts. |
| Launch mode | No | Auto / Managed application / Regular application. In the standard Tax Code of the RK, leave "Auto". |
| Invalid | No | Checkbox for archived records. Such a user is excluded from selection lists and cannot log in. |
| Contact information (Email, phone) | No | Needed for mailings, access recovery, notifications. If you make a mistake in the email — the person will not receive service emails from the database. |
Separately — the rights block:
- Access rights / Access groups — via the link in the card. The user is included in one or more access groups (for example, "Accountants", "Payroll Calculator", "View Only"), which rely on access group profiles. Without an access group, a person will log in but will see almost nothing.
- The "Administrator" checkbox (through the "Administrator" profile) grants full access. Distribute carefully.
After filling out, click "Save and Close". If 1C authentication is enabled — at this moment, an information database account is created.
4. Analyzed example
Situation: we hired accountant-calculator Akmetova Aigul Serikovna. She needs access to payroll and HR, but without administrator rights. The salary amount is not relevant, but for context: the minimum wage in 2026 is 85,000 ₸, and she will be calculating thresholds based on it. We set the rights as follows:
- Administration → User and Rights Settings → Users → Create.
- Full name:
Akmetova Aigul Serikovna. - Login name:
AkmetovaA. - Natural person: select from the "Natural Persons" directory (if not available — create it right here).
- Check "Access to the program allowed".
- "1C:Enterprise authentication" → enable "Require password change on first login" (Aigul will set her password).
- Save. Go to the "Access Rights" link → add the access group "Payroll Calculator" (profile "Payroll Calculation").
- Save and Close.
What "formed" from these actions (analogous to entries for a service object):
| Where recorded | What exactly |
|---|---|
| Information database accounts | User AkmetovaA created with the flag "require password change" |
| Information register "User Access Groups" | Aigul → group "Payroll Calculator" |
| Register "Users by Groups" / RLS | Visible data defined (payroll, HR) |
Accounting entries Dr/Cr this object does not create — this is not a business operation, but an access configuration. Upon first login, Aigul will enter her password, and all documents conducted by her will be marked by her as the author.
5. Types of accounts
There are no "operations" in the accounting sense in the directory, but there are different types of access it covers:
- Regular user — employee, logs in with a password (1C authentication).
- OS user — login via Windows/domain account.
- Technical/service user — with "Show in selection list" unchecked, for exchange, regulatory tasks.
- Invalid — archived record of a dismissed employee, access prohibited.
- External users — maintained in a separate directory "External Users" (for web clients/services), this is not this object.
6. What is formed upon saving
Once again, honestly and to the point — entries, ESF, and tax return forms do not arise here. Upon saving an item:
- a user of the information database is created/updated (if 1C:Enterprise authentication is enabled);
- movements are written to the information registers of rights: user access groups, values for RLS (record-level restrictions), personal settings;
- the connection "User ↔ Natural Person" is updated;
- the registration journal records the fact of creating/modifying the account.
7. Printed forms
The directory does not have its own printed forms (invoice, act, waybill) — there is nothing to print here. For access control, use administrative service reports:
- report "Access Rights" (who can do what) — from the rights settings section;
- "Registration Journal" — who logged in and when, what was changed;
- report by access groups / group members.
8. Common errors
- "Username (for login) is already in use. Please specify another name." — the login must be unique. Change
AkmetovaAtoAkmetovaASor add initials. - "Password does not meet complexity policy." — password complexity check is enabled. Add numbers/uppercase letters or agree on the policy with the administrator (User and Rights Settings → Password Policy).
- "User has no roles (access groups) specified." — the person is created but not included in any group. Go to "Access Rights" and add a group.
- "Insufficient rights to perform the operation." — you are not an administrator and cannot edit other accounts. Contact someone with the "Administrator" profile.
- "Access to the program is prohibited." — the checkbox "Access to the program allowed" is unchecked or "Invalid" is checked. Check both.
- Deleted the user, but their name is still "hanging" on documents. — do not delete, but uncheck "Access allowed" and check "Invalid": deletion breaks links in conducted documents.
9. FAQ
1. How do "Users" differ from "Natural Persons"? "Natural Persons" are people (employees, accountable persons) for accounting and payroll. "Users" are accounts for logging into the database. One user is linked to one natural person, but not every natural person is a user.
2. How to properly dismiss an employee from the database? Do not delete the card. Uncheck "Access to the program allowed" and check "Invalid". The history of their documents will be preserved, and they will no longer be able to log in.
3. The user forgot their password — what to do? The administrator opens the card, sets a new password in the authentication block, and checks "Require password change on first login". The person will log in and set their own.
4. Can you prohibit an employee from changing their password? Yes, the checkbox "User is prohibited from changing password" in the 1C:Enterprise authentication block.
5. Why does the new user see nothing after logging in? They are not included in an access group. Open "Access Rights" in their card and add the necessary profile (for example, "Accountant").
6. Does this directory create entries or ESF? No. This is an access configuration. Entries and electronic documents (ESF in the ESF IS, tax return forms) create accounting documents, not the user directory.
7. How to hide a service account from the selection window at startup? Uncheck the checkbox "Show in selection list". The login will remain active, but it will have to be entered manually.
8. What does the connection with a natural person provide? Contacts are automatically pulled, the responsible person is correctly substituted in documents, and HR and payroll reports see who is who.
9. Can one person be given multiple roles at once? Yes. Add them to several access groups — rights are summed up. For example, "Payroll Calculator" + "View Bank".
10. Who can create users? Only a user with the "Administrator" profile (full rights). A regular accountant does not have access to the rights settings section.
10. Related objects
- Natural Persons — based on a natural person, it is convenient to create a user (link "employee ↔ account").
- Access Groups and Access Group Profiles — define what the user is allowed; the user is included in groups.
- User and Rights Settings (password policy, RLS access restriction) — general rules applied to all.
- Registration Journal — control of user actions after their creation.
How to find out your release
"Help" → "About the program": it indicates the version of the 1C:Enterprise platform and the configuration release. This manual is compiled for