Before every novice administrator of 1C infobases, sooner or later, the question arises: how to add a user to 1C. And if in version 7 of the program the answer to this question could be given unequivocally: through the Configurator, then in the eight, depending on the version of the program, the methods of adding a user can differ significantly.

What is the purpose of differentiation by users

Each infobase user has a set of specific rights and roles. To restrict access to specific configuration objects and avoid conflicts associated with incorrect input and correction of information, there is a list of users.

In addition, the list of users allows you to:

1. Regulate the program interface, excluding from the visual display those elements that do not need access;
2. Commit changes in the database in the context of this list.

The main rule when editing this list is that the user with full (administrative) rights should always be added first.

Adding a user through the Configurator

In fact, from a programmer's point of view, the master list of users is stored in the Configurator. It can be opened by going to the Administration-> Users menu (Fig. 1)

In the opened table, you will see two columns "Name" and "Full name" of the user. Actions with an existing user (limiting and adding rights, changing the password, etc.) can be performed by activating the line by double-clicking.

To add a new user, you must click the icon on the command bar of the table or the Insert (Ins) button on the keyboard, as a result a dialog box will open (Fig. 2)

Rice. 2

Briefly about the form elements on the "Basic" tab:

• Name - contains text information that will be displayed in the user's selection list when logging into the system; the name of the current user can be read in the code of program modules using the UserName () method;
• Full name - may coincide with the username, most often the full name of the employee is written here.

1. By internal means of the program, for which it is necessary to set a user password;
2. By means operating system;
3. Using OpenID.

The "Show in the selection list" checkbox set in the "Enterprise 1C Authentication" submenu indicates that the user will be displayed in the list called upon system startup. If it is not installed, then to enter this user he will have to enter his name (as it is set in the Configurator) using the keyboard in the corresponding window.

Rice. 3

There are only four elements on the "Other" tab (Fig. 3):

• Available roles (by setting certain checkboxes, you can significantly limit or increase the ability to change information);
• Main interface (you can adjust the visual display of the system);
• Language (main language of the program);
• Launch mode (managed or regular application).

Adding a user in 1C Enterprise mode

Starting from platform 8.2, adding new users became available in 1C Enterprise mode. For this purpose, the corresponding directory "Users" was added to the database.

In the thin client mode, access to it can be obtained by going to the "Administration" tab (Fig. 4) -> User and rights settings-> Users

Rice. 4

In the form that opens, to create a new user, click the "Create" button. A window will appear (Fig. 5)

Rice. 5

As you can see, some of the elements of this window coincide with the window for creating a new employee in the Configurator. Significant differences with this addition method:

• A user can be associated with a specific individual from the appropriate directory;
• By checking the box "Require setting a password at login", you can additionally protect the database from unauthorized access (the protection mechanism is as follows: the administrator adding a new element sets simplest password and informs it to the user, at the first login to the system, this password is entered, and when the system starts, a window appears asking for new identification data, so no one except the user can log in to the system);
• Specific access permissions for a particular user are issued not by turning on and off his roles, but by adding him to certain groups access, where you can get by activating the corresponding link on the form.

The profile defining a set of rights is stored in the "User groups" directory, you can change and add a profile in the "User group profiles" directory. Thus, the Administrator does not need to control each specific user, the access parameters are changed for the entire group as a whole.

In the normal application mode, the "Users" directories can be found in the Operations-> Directories menu (Fig. 6)

Rice. 6

In principle, the window for adding a new artist in this mode differs little from those presented above and there is no need to re-describe each of its elements.

In the article we would like to draw your attention to the "Additional Information" menu (Fig. 7)

Rice. 7

It contains 4 points:

1. User Settings;
2. Contact Information;
3. Access groups;
4. Additional rights (not available when the user has a profile).

The first menu item allows you to automate some of the executor's actions: set up automatic substitution of document details, display of calendars and events, prefixes, etc.

As the experience of using the 1C system shows, the "Additional rights" menu is most often required to enable editing printed forms documents. This is where the corresponding checkmark is located.

The user created in the program will be automatically added to the list in the Configurator. Feedback in the new versions of the program, it is not, which is extremely inconvenient and unusual for administrators who work in the old fashioned way.

This article will focus on setting up user access rights to objects of the 1C system.

In 1C 8, a separate metadata object is used to control user access, which is called Roles.

Note! This article was written to help programmers. Setting up rights in user mode using the example of 1C Accounting is discussed in.

A role defines the set of rights a user has. Roles mechanism is very similar to Windows rights mechanisms Active Directory... For each of the objects (reference books, documents), the developer sets his own set of rights - read / write / add / change / ...

The set of available rights - collection of all permissions in user roles.

If we open the Role metadata object, we can see the following picture:

The object has two tabs - Rights and Templates of restrictions. Rights - the main tab, Templates - a tab for setting rights at the record level in 1C ( RLS). This is a very important topic, I will try to describe it in future articles.

We will consider only the tab Rights.

• Objects- the list for which the rights will be set.
• Rights- a list of rights that can be set up.
• Restricting access to data- role fields for customization

Pay attention to the check marks at the bottom:

• Set rights for new objects- if the flag is set for a role, permissions will be automatically set on new metadata objects. I recommend installing if you often forget to set the rights to new objects.
• Set rights for attributes and tabular sections by default- a flag, when set, the attributes and tabular sections will inherit the rights of the owner (reference book, document, etc.)
• Independent rights of subordinate objects- if the flag is set, then the system, when determining the rights to the configuration object, will take into account the rights to the parent object

Setting rights for the entire configuration

If we open the Role and click on the configuration root, we will see the following settings:

More about each of rights to the whole configuration:

Get 267 1C video tutorials for free:

• Administration- administration of the infobase (requires the "Data administration" right)
• Data administration- the right to administrative actions with the data
• Database configuration update- right to
• Exclusive mode- use of exclusive mode
• Active users- view the list of active users
• - registration log
• - the right to launch a thin client
• - the right to launch the web client
• Fat client- the right to run the fat client role
• External connection- the right to start an external connection
• Automation- the right to use automation
• All functions mode- in managed application mode
• Saving user data- permission or prohibition to save user data (settings, favorites, history). Especially important for 1C managed forms.
• Interactively opening external treatments- opening external treatments
• Interactive discovery external reports - opening external reports
• Conclusion- printing, writing and copying to the clipboard

Setting 1C 8.2 rights to other metadata objects

For the rest of the main objects (directories, constants, documents, registers ...), the set of rights for the role is quite standard:

• Reading- reading (software)
• Adding- addition (software)
• The change- change (software)
• Deleting- deletion (software)
• View- viewing
• Interactive add- interactive add
• Editing- editing
• Online flagging for deletion- interactive mark for deletion
• Unmarking Deletion Interactively- unmarking for deletion
• Interactive deletion of marked- deleting marked objects
• Input by line- using line input mode
• Online uninstall- direct deletion (shift + del)

Rights only for documents:

• Interactive conduct- holding
• Cancellation- cancellation of documents
• Interactive non-operational- conducting (by standard commands of forms) a document in non-operational mode
• Interactive cancellation- interactive cancellation
• Interactive modification of the conducted- editing of the posted document. If the role has no right, then the user cannot delete the posted document, mark deletion, repost or make it unpost. The form of such a document opens in view mode

P.S. If you still did not manage to understand the roles of users, you can order.
Video with an example of setting rights in 1C Accounting 3.0:

01.06.2018

As in the typical configuration of "1C: Enterprise Accounting" edition 3.0, configure user access rights in such a way that each user can create, view and edit documents of only certain organizations.

The functional capabilities of the standard configuration "1C: Enterprise Accounting" of the PROF version allow you to keep records on behalf of several organizations (legal entities or individual entrepreneurs) in one common information base, which allows you to use general reference books and receive summary analytical information on several organizations within the group at once companies.

Naturally, in this case, it becomes necessary for some users to be able to work on behalf of only one or several strictly defined organizations and to restrict access to data of other organizations.

In programs based on the 1C: Enterprise 8.3 technological platform, this task is solved using a data access restriction mechanism at the RLS record level, which can be deciphered as Record Level Security (record-level security) or Row Level Security (row-level security).

Previously, this mechanism had to be built in in the configuration mode with the help of programmers. In the standard configuration "1C: Enterprise Accounting" version 3.0 functionality the access restriction mechanism in the context of organizations is already included in the standard functionality and can be enabled and configured by an ordinary user (with administrator rights) independently without the help of specialists.

This method RLS access rights settings in the context of organizations can be used in the standard configuration "Enterprise Accounting" version 3.0, both in the local version installed on the user's computer and in the cloud version of 1C: Accounting.

Let's consider the RLS setup using the example of a typical configuration "1C: Enterprise Accounting 8" edition 3.0 ("Taxi" interface).

Initial data.

There is an information base that keeps records of four organizations, of which one individual entrepreneur and three LLCs (see fig.)

One Administrator and three users will work in this infobase: the chief accountant, one unit manager and a sales manager.

You need to configure user rights as follows:

Customization

The first step is to enable the ability to differentiate access rights by organization. To do this, in the "Administration" section, select "Configure users and rights"

In the form that opens, in the "Access groups" subsection, check the box next to "Restrict access at the record level".

Please note that the inclusion of this mechanism for the differentiation of rights can lead to a significant decrease in the speed of the system (especially if it was not working fast before) and an increase in the performance requirements of the computer and server equipment used.
The reason for the decrease in the speed of work is that the standard requests when accessing the data, additional selections are added, and each time the user accesses any data in the infobase, the program will perform an additional check.
Therefore, before enabling this setting, we recommend that you first check its effect on the program performance on a test copy of your infobase.

After that, in the "Users" directory, select the user whose rights we will configure and press the "Access Rights" button.

The "Administrator" profile allows access to all data of all organizations, additional customization administrator rights are not required. The system must have at least one user with administrator rights.

First, let's set up the rights of the chief accountant "Ivanova Anna Sergeevna", who needs to be given full access to all organizations.

The window for setting rights will open.

It is necessary to select the "Chief Accountant" user profile.

The chief accountant must have full access to all organizations, therefore, in the right window, in the "Access value" column, select "All allowed".

For the sake of fairness, it can be noted that the "Chief Accountant" could be assigned the "Administrator" rights - this would automatically give access to the data of all organizations, but then the Chief Accountant will also have system administration points in the interface.
This can be done if there is no separate administrator and his role is performed by the chief accountant, but one user should not be assigned more than one role.

If the configuration describes several roles with restricted access at the record level (RLS), then we do not recommend assigning more than one such role to one user (for example, accountant and HR), since when all requests are executed, the conditions of both RLS will be added to their conditions using a logical OR, which can lead to a decrease in the speed of processing the request and, as a result of the entire program

If the setting is made in cloud service"1C: Fresh", then when saving the settings, the program may ask for confirmation of changes in access rights, for which it will be necessary to enter the password of the user on whose behalf the setting is made.

The next user is Vladimir Ivanovich Popov, who needs full access to the documents of one organization "IP Popov V.I."

Restriction of access to data can be configured in two ways: according to the principle of "white" or "black list", ie. you can configure the user to access the list of allowed organizations and then the user will have access to the data of the organization that is specified in this list, or vice versa, configure the list of prohibited organizations and then the user will have access to the data of all organizations in the infobase, except for those specified in this list.

We select the profile "Chief accountant", in the column "Type of access" in the upper right window select "All prohibited". After that, in the "Allowed values" window, press the "Add" button and in the drop-down menu, select SP Popov V.I.

We save the settings.

We pass to setting up the rights of the next user Sidorov Petr Nikolaevich, who needs to be given access only to the extract of the primary documents of the sales department on behalf of only two organizations: LLC "Leader" and LLC "Mebelshchik".

Select the "Sales Manager" profile. We select the access value "All prohibited". In the window "Allowed values", first select LLC "Leader", and then press the add button again and select the second organization LLC "Mebelshchik".

We save the settings.

If this information turned out to be useful for you, then we like the article on social networks and share the link on our favorite forums))).

Online company, 2018

As in 1C: Enterprise Accounting, edition 3.0, configure user rights in the context of organizations, Restricting user access rights at the record level to data of only one organization in 1C: Accounting using the RLS (Record Level Security) mechanism, The user should see documents only from his organization in a multi-company information base 1C: Accounting, How to use the mechanism of restricting access at the record level (RLS - Record Level Securiy) in 1C: Accounting to set up user rights to documents of only one organization? Setting up a mechanism for differentiating rights at the level of RLS (Record Level Security) records in 1C: Accounting 8.3. documents of only the necessary organizations? As in 1C: Accounting 8.3, allow the user to access the data of only one organization, Configuring the RLS system to restrict user rights to access documents of only one organization in the 1C configuration: Enterprise Accounting revision 3.0, How to configure access restriction at the RLS record level in a typical 1C configuration : Accounting 8.3, Access restrictions by organization in 1C: Accounting 8.3. using the RLS mechanism, As in 1C: Accounting 8.3, configure user access rights to the data of only one organization, As in 1C: Accounting 8, hide organizations for some users, Configuring the RLS system (Row Level Security - restricting rights at the row level) in 1C: Enterprise Accounting revision 3.0, Restricting access to data of only one organization for a specific user in 1C: Accounting 8.3, As in a typical configuration of 1C: Enterprise Accounting revision 3.0, configure user access rights in the context of organizations, How to enable the ability to configure access restrictions at the record level in of a typical configuration 1C: Enterprise Accounting revision 3.0, As with multi-company accounting in 1C: Accounting, allow the user to access documents of only one organization, As in 1C: Enterprise Accounting 3.0 configuration, configure user access rights to documents of only one organization, Setting up the RLS system (Record Level Security - restriction of rights at the level of records) in the configuration 1C: Enterprise Accounting rev. 3.0, Setting up RLS mechanisms to restrict the user access rights to data of only one organization in the 1C configuration: Enterprise Accounting rev. 3.0, Restricting access to documents of only one organization for a specific user in 1C: Enterprise Accounting 3.0, How to hide documents of one organization in a common 1C: Accounting database for one user, In one infobase 1C: Accounting keeps records of several organizations, how to set up RLS so that could the user only see documents for their organization? At the enterprise, in one infobase of 1C: Accounting, multi-company accounting is maintained and database users need to configure access in such a way that each user can create, view and edit documents of only certain organizations? How in 1C: Accounting 8.3 using the RLS mechanism (Record Level Security - restriction of rights at the level of records) to configure the restriction of the visibility of documents for a specific user in the context of the selected organizations?

Tags: Setting up RLS in 1C: Accounting 8.3, How to set up restriction of rights at the record level in 1C BP 3.0

- Vasya, from today on, you start users!
- But I'm a programmer, not a system administrator ?!
- Sysadmins do not know 1C, so you will start users!
- Aaaaa !!!

A programmer is a person who writes programs for a computer. However, the management of the list of users in 1C is usually entrusted to the one who is associated with 1C, namely the 1C programmer.

In principle, some programmers do not mind, since this gives them some "privileges" in their hands.

Nevertheless, the list of users in 1C does not differ much from the lists of users in other programs. Therefore, adding a new user or disconnecting an existing one is as easy as shelling pears.

1C users

So, 1C has its own list of users. With it, access to the 1C database is regulated. When entering the database, 1C will ask you to select a user from this list and enter a password.

There are options in which 1C does not ask for a username to log in. However, this does not mean anything at all . It's just that in this case, the user from the list is mapped to the Windows / domain user and is automatically detected. How

The only option when 1C does not really ask the user is when creating a new (empty) database. In this case, the list of 1C users is empty. Until the first user is added, 1C will log in automatically. A similar system is used in Windows with one user without a password.

1C users differ from each other:

• Access rights
• Interface (available in the menu items).

As such, there is no "superuser" or "group of administrators". An administrator is the user who has all rights in the configuration and administration rights enabled. In an empty database (when the list of users is still empty) - just such a user should be added first.

Two lists of 1C users

In fact, 1C has two lists of users. One of them (the list of 1C users) is "real" from the point of view of the programmer. It is located in the configurator. It is according to him that 1C determines the user.

This is the approach of the old typical configurations (for example, trade management 10, accounting 1.6, etc.) - users are edited in this list, and they are automatically added to the user guide when they first log in.

The second (users of version 1C 8.2, "not real") is the users directory (and the external users directory, as in ut 11). The reference book existed before, but the approach of the new typical configurations is that users start in it, and they automatically enter the "real" list.

The main problem of this approach is that those who do not like to work this way and want to do it the same way - they cannot do this, since certain fields are filled in at the establishment, and if you add a user with pens in the list, then they will no longer be picked up in the reference book automatically.

How to add a user to the list of 1C users

So, the list of 1C users is in the configurator. and open the Administration / Users menu.

To add a user, you must press the add button (or Ins from the keyboard). If the list is now empty, then the first user should be with administrative rights(see below).

• Name - username (which he will choose when entering 1C)
• Full name - reference name, does not appear anywhere
• Password
• Show in picklist
  o if the checkbox is checked, then the user will be in the selection list when entering 1C
  o if the checkbox is not checked, then the user will not be in the selection list (that is, it cannot be selected), but you can enter his name from the keyboard and enter
• Operating system authentication - can be associated with a Windows / domain user and this user will not need to enter a password (it will log in automatically).

On the Other tab, you can select the rights and basic settings of the user.

• The main interface is a menu that will be available to the user (used only in the thick client)
• Russian language
• [Main] Startup mode - thick or thin client, using this parameter you can enter the configuration of the thin client - thick and vice versa
• Available roles (user rights).

User rights in configurations are usually divided into blocks ("roles"). In the old configuration approach, they were broken down by user positions (cashier, manager, etc.). This approach has a drawback - since in different organizations the cashier and manager may have different functions.

Therefore, in the approach of the new configurations, they are broken down by actions (access to the closing of the month, access to cash transactions). That is, a set of operations is set for each user.

In both cases, you have basic access rights to enter the program. In the old approach, this is:

• User
• Full Rights (for administrator).

In the new approach, these are:

• BasicRights
• Basic Rights
• Launching Thin Client - plus LaunchingXxxClient to launch others
• SubsystemXxx - a check mark for each subsystem (tab in the interface) that the user needs
• Full Rights (for administrator, not Administration!).

PS. Basic rights are not required for external users.

How to add a 1C user - 1C 8.2 users

The list of 1C 8.2 users in the new version is located in 1C (in 1C Enterprise mode), in the Users and External users directories (only if the configuration supports). The difference is that you should not create users in the configurator, but in this guide, and they will be automatically sent to the configurator.

If you are using a thin client, see the Administration tab of the desktop. Otherwise, open the Users directory, for example, through the Operations menu.

Click the Add button (or Ins from your keyboard). For you to manage the list of users, you must have the FullRights rights enabled.

Unlike the first approach, here you do not directly specify each right (role) to the user, but specify the groups of rights (user groups).

The User groups reference contains a profile that defines a set of rights (roles). In the User group profiles reference, you can change or add such sets of rights (roles).

1C user settings

In some configurations (especially in the configurations of the old approach), it is not enough to create a user. Additionally you need:

• Login for the first time in the system
• After that, find the user in the user guide
• In the form of a reference press (options "or")
  o Menu Go / User Settings
  o Menu Additional information / User settings and Additional user rights
  o In some configurations, this is a plate directly in the user form
  o In some configurations global menu Service / User settings programs
• Configure additional settings / user rights that define autocomplete fields and some access.

How to disable a 1C user

[Temporary] user disconnection is not provided in most configurations. Here are the variations you can use to achieve this result.

Old approach configurations (via configurator):

• Delete user
• Change password
• Remove the role User (will not be able to log in).

New Approach Configurations (Through Enterprise):

• Uncheck the Access to inf. base allowed
• Change password
• Exclude from all access groups.

Active users of 1C

1C allows you to find out the list of users who are currently in the database.

To do this, in Enterprise mode, select the Tools / Active Users menu (thick client, administrative interface). V thin client- the Administration tab, on the left Active users (maybe in See also).

In the Configurator mode, select the Administration / Active users menu.

Disconnecting 1C users

As you know, in order to update the database (configuration), it is necessary that all users exit 1C (not in all cases, but often required).

Users do not like to go out (this is a fact). And if you ask them by phone, they will surely come back in 30 seconds. With 200 users, it becomes a lot of fun.

Therefore, there are three ways to disconnect users from 1C:

Working in the 1C program allows different users to assign functional access to documents and reference books of the database. For instance:

• If the user works as an accountant, then he is assigned a corresponding role in 1C, which allows him to add, change, delete documents and reference books on business activities.
• If a 1C user works only with reports and views the database data, for example, a manager, then he is given the right to read data.
• A user who can work with all objects of the 1C - Administrator program has full rights and gets unlimited access to work with the database in 1C.

Access rights can only be configured Administrator- a 1C user who has been assigned Full rights.

Setting access rights in 1C 8.3 Accounting 3.0

In 1C: Accounting 8 ed. 3.0 there are 4 main profiles for working with the program:

• Administrator;
• Accountant;
• Chief Accountant;
• Synchronization with other programs;
• Only reading.

To understand the principle of setting rights in 1C, let's turn to the configurator. When analyzing configuration objects, we will see a special branch Roles, which lists all possible accesses to database data specified by 1C developers:

Each role corresponds to a set of capabilities for working with configuration objects, these are -

• Reading;
• Adding;
• Carrying out;
• Cancellation of the event;
• Editing;
• Removal.

If you open a given role, then for each object you can see what you can do with each configuration object:

It is important to know that a 1C user can be assigned any set of roles from the list specified by the developers. At the same time, if it is impossible to change the object in some role, but it is possible in another role added to this user, then the resulting one by user rights will be - can be “changed”. The roles are mutually complementary. In order for the object not to be changed by the user, there should not be "Change" in any of the roles assigned to it.

Setting up access rights in 1C 8.3 Accounting

Setting up access rights in 1C 8.3 is carried out in the section Administration - Settings for users and rights:

The User and rights settings window opens:

Let's consider the possibilities of setting up access in 1C.

How to create a new user in 1C 8.3

By default, the 1C program sets The entrance to the program is allowed, Show in picklist and entering the program using the login and password set in 1C. You can set the password yourself, or you can offer to set it to the program. Typically, a password programmed 1C, meets a more serious level of verification and it is more difficult to find such a password when breaking the system.

Remember the password! If the password is lost, then only the Administrator can reset it. If the passwords are lost and you cannot enter the database, you will have to "hack" the entrance to the database.

For this, specialists use a HEX editor and, in the right places, change the information responsible for working with users. It is possible to do this, but not desirable.

How to set up access rights based on typical profiles in 1C 8.3

Each user (Administration - Settings of users and rights - Users) is assigned Access Rights from the list of profiles that is in the configuration. For example, for the accountant Petrova S.B. assign a profile Accountant:

Here we can transfer the settings to a new user from a user already working in 1C: Functionality setting, internal report settings, etc., so as not to waste time and do not type everything manually:

We mark the settings for transferring to the new user Accountant Petrov from the Administrator user:

We transfer personal settings, print settings and Favorites:

Press the book. Select and in the form for selecting settings "Copy and close". All settings for the new user from the Administrator user have been migrated.

Setting up access rights with the addition of new profiles in 1C 8.3

Create a new profile with limited access to reference books and documents. Access Group Profiles - Create:

It is convenient to create a new profile for 1C subsystems. For example, for the rights of the Calculator, we can mark the following functionality:

• Reflection of salaries in accounting;
• Reading taxes and fees;
• Mutual settlements with employees;
• Personalized accounting;
• Salary accounting:

According to the book. Selected roles only a list of the selected user roles is shown. Personnel accounting can be set separately for the HR profile.

How to set up additional access rights to existing standard profiles in 1C 8.3

A specific 1C user with a selected profile can add functionality. For example, for the user Petrov, in the Accountant profile, the command All functions but we can add it this user... Go to Administration - User and Rights Settings - Access Group Profiles. Book. Create - All functions mode - add rights. “All functions” mode:

Add a new profile to accountant Petrova S.B .:

Setting up additional access rights to individual documents and directories in 1C 8.3

This setting provides for work with a configuration extension. Let's say you need to configure 1C user access to an arbitrary set of documents and directories. The set of these documents and reference books can be different - 1C developers are not able to provide all options for suitable roles that users may need in practice. Moreover, requests for data access can be completely extraordinary.

In 1C 8.2, we had to remove the edit prohibition from the configuration and add new role into Role objects, assigning access to the necessary directories and documents, and, accordingly, difficulties arose with the subsequent update of 1C. Such configurations were no longer automatically updated, so only users of organizations that had 1C programmers on their staff could afford such pleasure.

In 1C 8.3, in connection with the emergence of a new opportunity to work with configuration applications, we can realize our task of differentiating user rights without removing the prohibition of editing from the main configuration and leaving it completely standard. How to do this - now we will consider:

1. For reference Users we will introduce an additional variable "Access_Realization_Goods", which will take on the values ​​"Yes" or "No".

Go to Administration - General settings - Additional details and information. We include the ability to work with "Requisites and information from general list values ​​":

1. Opening a hyperlink Additional details.

In the left column of the lists of configuration objects, we find Users and click on the book. Add... Fill in the opened form as shown below. The new variable will have two values: "Yes" and "No". Let's combine the values ​​into the "Access" group. Fill in the Main tab:

Fill in the Values ​​tab:

1. Now let's fill in this props for our users.

"Petrov's accountant" - No:

"Administrator" - Yes:

All the necessary actions in the 1C 8.3 database have been done, now we will work with by expanding the Configuration.

1. We enter the database configurator: Configuration - Configuration extensions:

We add a new configuration extension according to the book. +:

We agree with the default data of the extension or set our own:

We open the configuration of the extension according to the book. :

Now we will transfer the data necessary for work from the main configuration. The created configuration extension "Extension 1" is still empty:

In the main configuration, we find in the documents - the document Sales of goods and services, and transfer the form with which we will work. For example, let's add "ProductDocumentForm" to the configuration extension by placing on the name of the form and clicking on it with the right button. mice. From the drop-down menu, select the "Add to extension" command:

Open the form in the configuration extension and create event handling Before Recording... When creating an event handler, the 1C 8.3 program will ask you to indicate where to create the program code. We choose: Create on the client and a procedure on the server without context:

When creating an event, we will see the event processing procedure assigned by the 1C 8.3 program in the empty cell of events "BeforeRecording": "Exp1_BeforeRecording":

Go to the form module and insert the following program code:

We update the changes and run the database in user mode to check the changes made. Log in under the user Accountant Petrov and edit the document Sales of Goods and Services, click the book. Write down:

For the administrator, editing the document will go smoothly.

The given program code can be put in the 1C 8.3 configuration extension for any document and reference book and this will allow not changing the typical configuration, but at the same time solving the problem of access to database objects for different users.

How to share a variant of the report with individual settings for other users in 1C 8.3 ZUP, see our video: