12. Pass access data to the company database manager

A good technical handover doesn't end with an email. It ends when the responsible person successfully logs in, changes the password and takes their first controlled step.

Why this station counts

The Company Database Manager role requires X-ERP rights, but does not automatically require infrastructure access. This separation protects the server and database without hindering technical administration.

The resilient process

1. Create a personal X-ERP administration user with minimal role required.
2. Submit address/company name and startup password separately.
3. Accompany the first login and mandatory password change.
4. Have a defined task executed and confirmed.
5. Document the recipient, timing, scope, support and blocking route.

Functional test - only then continue

• Access belongs to a named person.
• No infrastructure secret was given.
• First login and password change are confirmed.
• Role is sufficient for the task, but not beyond.

If the result is not correct

• Shared administrator access remains active after personnel changes.
• Password and URL travel in the same channel.
• Unclear responsibility delays lockdowns and security response.

This is what you take with you

The operation switches from installation to technical responsibility in a controlled manner without blurring the safety boundaries.

Video

▶Handover of access data to company database manager

Further information / source

Related topics

1. For system administrators – set up servers and create company databases › 07. X-ERP-Company-Creator (create company database/client)
2. For system administrators – setting up servers and creating company databases › 13. Backup, monitoring and recovery

Frequently asked questions