TABLE OF CONTENTS
- Explanation
- Configuration
- Behaviour in the system
- How our customers use this
- More articles on this topic
Explanation
Users are the people with (permitted) system access. You can create as many users as you like. Each person should have their own user with their own access data. At this point, the users receive the right to act in the system via roles, as far as the role allows it.
Configuration
The user can be configured via the menu on the page User.
Behaviour in the system
- A user gets view permissions and the right to do things in the system always from the organisational unit in which he is located downwards. This means that he can do something in his OU and in all the ones below it. It is not possible for him to act in neighbouring or superordinate OUs.
Example: A user is created at city level and his role is administrator. He can only see the correspondence templates that are created at city level and below. Not the ones that were created for Germany and Co. - If a user is deleted, his user name is still listed in the application, tender etc. history.
- Login
Here you determine the login details and how a user can log in.
- Username
- Access to the system by Username/Password and/or single sign-on
Properties
This information, along with the roles, lays the foundation for what the user is allowed to do in the system
In addition, you can use the information in placeholders to make it visible to the applicant.
- Organisational unit
- Company
- Language
- Salutation
- Title
- First Name
- Last Name
- Signatory authority
- Position
- Division
Notifications
Here you control how or if the user is notified about new tasks and applications
- Upon incoming message
- Daily E-Mail for
- New Applications
- Overdue tasks
- Expiring Job Publications
- Expiring External Job Publication Channels (Multiposting)
Contact Information
You can use the information in placeholders to make it visible to the applicant in job ads or correspondences.
- Street, No.
- Additional Address
- Zip Code, City
- Country
- Email Address
- Telephone
- Mobile
Permissions
Through these you control what the user is allowed to do and see in the system.
Images
This image can be included in job ad templates, for example.
How our customers use this
Many of our clients use a username and password login. However, setting up single sign-on is also possible. Users then only have to log on to their computer once in the morning, but do not have to enter their user name and password again when starting d.vinci. Users can request a new password themselves if they have forgotten it.
More articles on this topic
- Sign up user
- Unlock user
- Change password
- Login/login page
- Single Sign-on (SSO)
- Preview application permissions
- Enable daily notifications retroactively
- Move user to another organisational unit
- User role
- API user