en:userpermissions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:userpermissions [2018/06/12 07:50] – Boris Kalisch | en:userpermissions [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Users permissions ====== | ||
- | |||
- | The Buildary user permission system is designed to allow very straightforward work on smaller projects with a few members project team. At the same time, it is flexible enough to meet the demands of large corporate customers and project teams of the largest construction sites. | ||
- | |||
- | The Buildary user permission system can be viewed as a two-level system. | ||
- | |||
- | ** The first level of permissions is at the domain level ** and controls if the user can create new projects and diaries in that domain. The user's permissions are set by the domain administrator. | ||
- | For users working in their personal domain, this level is irrelevant, because, in the personal domain, the user always has all the permissions. | ||
- | |||
- | ** The second level is the construction diary and its entries **. For each construction diary, authorised persons and their roles are listed. The role defines the user's permissions in the diary. This is a level that every diary administrator needs to understand and use properly. | ||
- | |||
- | ===== Project team members ===== | ||
- | |||
- | If you have set up a project and you want to grant access to other users, you must enter them as Project Team Members. This is done in the Project set up window. | ||
- | |||
- | After the user has been added to the project, the invitation email is automatically sent to his/her address. Project team members can enter the project but they do not have access to any dairy until you add them to the diary authorised person list. | ||
- | |||
- | ===== Diary authorized persons ===== | ||
- | <WRAP 100%> | ||
- | <WRAP 600px left> | ||
- | {{gallery>: | ||
- | </ | ||
- | If you want a user to access a diary, you must include him/her in the diary authorized person list. The list can be found in Diary identification option. You also need to assign a role to the user. This role gives him the permission to work in the diary. | ||
- | |||
- | The roles are defined in the Team Members Role tab in the Project set up window. The following permissions can be set up: | ||
- | |||
- | * ** Diary Administration ** - this permission allows you to edit diary identification data, enter authorized persons, and delete diary (unless it contains signed and closed daily reports). | ||
- | |||
- | * ** Regular Entries ** - this permission allows you to insert, edit, and delete records in the Weather, Labour, Plants, Materials, and Performed Works sections. Mind that you can edit only your own entries and only until the day is locked. | ||
- | |||
- | * ** Other Entries ** - this permission allows you to insert, edit, and delete records in the Other Entries section. Mind that you can edit only your own entries and only until the day is locked. | ||
- | |||
- | * ** Documents ** - this permission allows you to insert, edit and delete entries in the Documents sections of the diary identification. This permission covers all four document sections (Project Documents, | ||
- | |||
- | You are automatically entered to the authorized person list as a diary administrator after you create a new diary. In addition, you are an owner of the diary. It grants you the same permission as the diary administrator. Diary owner cannot be restricted by deleting or changing his role in the diary. | ||
- | |||
- | <WRAP info> | ||
- | Any user listed as an authorized person in the diary has full permission to view all diary data regardless of his/her role. | ||
- | </ | ||
- | |||
- | |||
- | |||
- | ===== Domain users ===== | ||
- | |||
- | On the other hand, it is very important for a company domain administrator to correctly understand and set domain-level permissions. Only the employees of your company are added to the domain user list. | ||
- | The external users are added only as project team members of a specific project. Not to the domain user list. | ||
- | |||
- | <WRAP 100%> | ||
- | <WRAP 600px left> | ||
- | {{gallery>: | ||
- | </ | ||
- | Domain users can be granted the following permissions: | ||
- | |||
- | * ** Domain Administration ** - This permission allows the user to edit domain settings, insert domain users including their permission settings, delete the domain. | ||
- | |||
- | * ** Create New Project ** - This permission allows the user to create new projects in a given domain. | ||
- | |||
- | * ** Administrate Project ** - This permission allows the user to edit project information, | ||
- | |||
- | The user is automatically written to domain users as an administrator after he/she creates the domain. In addition, he/she becomes the owner of the domain which grants him/her the same permission as a domain administrator. Therefore, deleting a user from domain user list or changing his/her domain permissions can not restrict the domain owner in his/her permissions. | ||
- | |||
- | <WRAP info> | ||
- | After you add a user to the domain, an e-mail is sent to his/her address, with an invitation to create an account. The E-mail address is the key to linking the user account and the user in the domain users list. It doesn' | ||
- | </ | ||
en/userpermissions.1528782628.txt.gz · Last modified: 2018/06/12 07:50 by Boris Kalisch