Know what is happening with your renovation.

01 / The product in one minute

DH Project organises communication around each renovation. Clients see decisions and their own accounts, the team shares project materials, and the administrator follows projects and separate financial relationships.

1. Clients understand what they approve, which work they pay for and how material funds are used.
2. Administrators manage access, notice new activity and retain document versions and confirmations.
3. Team members discuss issues in context, find documents and receive personal mentions.

02 / Registration and first access

Start with the personal invitation sent by your project administrator. The general sign-in page is for existing accounts.

1. Open the complete invitation link in your browser and select a language.
2. Enter your name and the exact email address used for the invitation.
3. Create a password of 10–128 characters and repeat it. Keep it in a password manager.
4. Choose “Create account and continue”. If you already have an account, choose “I already have an account” and sign in.
5. If an invitation card appears after sign-in, check the project and role, then choose “Join the team”.

03 / Web browser and Android

1. On a computer, iPhone or iPad, use “Open web app” above. No installation is required.
2. On Android, download the APK above, open it and approve installation. If Android asks to allow this source, do so only for the administrator-provided build.
3. Use an invitation for first access; use your email and password for later sign-ins.
4. Refresh the browser to load interface updates, or close and reopen the Android app. Install a new APK over the existing app when the administrator releases a new build.
5. Allow Android notifications when prompted if you want them. The web app has in-app activity indicators; browser push notifications are not yet enabled.

04 / Projects and unread messages

1. Each project has a card on the home screen. Desktop users also see a project list on the left.
2. A blue counter identifies new messages. Open the project and use the section counters to locate the activity.
3. Entering a section with new messages takes you to the first unread message. With no unread messages, it opens at the latest one.
4. To add a project, the administrator selects “Create”, enters a recognisable name and then invites the team.
5. The globe changes your interface language without changing anyone else’s language.

05 / Team and permissions

The administrator opens Team → Invite, enters an email, selects a role, creates a link and sends it to that person. Creating the link does not send an email automatically.

1. Administrator: creates projects, invites and revokes access, proposes dates, initiates approvals and manages accounts.
2. Client: chats, uploads materials, accepts or requests changes to proposals and accepts their stage amounts. Cannot initiate document approvals.
3. Designer, engineer/inspector and coordinator: discuss work, submit proposals for approval and upload new document versions. They cannot access financial accounts.
4. Contractor: chats, uploads materials and sees only their own accounts and relevant material movements. Cannot initiate approvals or approve documents on behalf of the client.
5. In “My project roles”, the administrator may select several professional functions. This never grants the right to approve as the client.
6. Revoking access removes project access but preserves the participant’s earlier messages.

06 / Project sections

1. Chat: shared conversation, photos, videos and documents. There is no approval button here.
2. Designs: drawings, design choices and related discussions.
3. Documents: contractual and other working documents.
4. Reports: progress, photographs, videos and report documents.
5. Settlements: restricted work accounts and material funds, visible according to the financial relationship.
6. Files: archive of attachments from the four communication sections. Search and open files here; approvals are created in their source sections. Financial receipts remain in restricted accounts.

07 / Messages, attachments and @mentions

1. Choose the project and section, type your message and press the send arrow.
2. Use Photo, Video or Document to add files. Photos need no caption. A message accepts up to 10 photos or one video/document. The limits are 25 MB per file and 50 MB per photo group.
3. In Chat, press @Mention or type @name and select a participant. You can mention several people.
4. The message remains visible to the whole chat. The recipient sees “You were mentioned”; this is not a private message.
5. Check the “Saved on server” indicator. History is retained; send corrections as a new message.

08 / Translation and search

Each participant chooses Russian, Ukrainian, Polish, English or German. Automatic translation covers chat text and settlement descriptions, with the original available to view. PDF contents, images and videos are not automatically translated.

1. Check “Message language” before sending, especially when writing in a different language from your interface.
2. If translation is unavailable, the original remains. Do not approve text you do not understand; retry translation or ask the author to clarify.
3. Open the project’s magnifying-glass search, enter a word, phrase or attachment name and select a section or the whole project.
4. Select a result to jump to its message. Search does not extract text from scans or PDFs.
5. Translations are cached. The pilot shares a limit of 450,000 characters per month and 15,000 per day across chat and settlements.

09 / Approvals and document versions

1. The administrator, designer, engineer/inspector or coordinator opens Designs, Documents or Reports, adds the materials, enables “For approval” and sends the proposal.
2. The client opens the attachment, checks the text and chooses “Approve” or “Changes needed”, giving a reason for changes.
3. The response is stored with the person and time. This records a decision; it is not a qualified electronic signature service.
4. To replace a document, choose “Upload new version” on the current single-attachment document. The previous version stays in history.
5. A new version does not inherit an earlier approval. Check its number and “Current” status before deciding.

10 / Contract dates and file archive

1. Open Contract dates at the top of the project. The administrator proposes start and finish dates.
2. The client accepts the proposal. When revised dates are proposed, the previously accepted dates remain valid until the revision is accepted.
3. In Files, search by filename and check the author, date and source section.
4. The archive includes older versions; check current status in the original discussion.

11 / Work-stage payments

Only the client and administrator see that client’s account. Only the contractor and administrator see that contractor’s account. Other participants cannot access these amounts.

1. Once the participant has registered, the administrator opens Settlements → Open participant account and chooses a client or contractor.
2. In Work, select the participant and create a stage with a clear description, PLN amount and optional due date.
3. The other party reviews it and selects “Accept amount”. Unaccepted proposals are excluded from agreed value.
4. After actual payment, the recipient confirms receipt: the administrator for client payments, and the contractor for administrator payments.
5. Partial payments are supported. Example: 6,000 PLN agreed, 4,000 PLN received, 2,000 PLN outstanding. Entries above the remaining balance are rejected.
6. Read the translated description and compare it with the original. Check both the amount and the work scope before confirming.

12 / Cash and material funds

1. Open Settlements → Materials and record Funds from client: amount, method and purpose.
2. Record giving cash to a contractor as a separate transfer. The recipient confirms receipt before the funds become available to spend.
3. The contractor or administrator records a purchase, description and optionally an image/PDF receipt up to 10 MB. The administrator approves contractor purchases.
4. Use Return remaining funds for unused cash. The recipient confirms the return or may reject an unconfirmed entry.
5. Example: client funds 3,000 PLN; contractor receives 1,000 PLN and spends 750 PLN. After confirmation, the administrator holds 2,000 PLN, the contractor 250 PLN, and 2,250 PLN remains overall.
6. A transfer between people is not a purchase. Pending outgoing entries reserve funds and reduce the available balance.

13 / Troubleshooting

1. Cannot sign in: check the invited email, keyboard layout and password. Use the personal invitation for first access.
2. Invitation unavailable: ask the administrator to check email, expiry and revocation, and issue another link if needed.
3. Missing a section or button: check your role and project. Finance and approval functions are intentionally restricted.
4. Upload failed: check connection, file format and size. Before retrying, check whether the message has already appeared.
5. Payment save error: refresh the list before entering it again. Avoid creating a duplicate until the first attempt is checked.
6. Report bugs with device, browser/app version, language, project, steps, expected result and actual result. Hide passwords and personal information in screenshots.

14 / For partners and investors

The product connects discussion, document version, client decision and financial stage within one renovation. Role-based access, individual languages and project activity indicators support a distributed team handling several sites.

1. Available in the pilot: projects and invitations, five interface languages, chat, mentions, search, versions, approvals, contract dates, private accounts, material funds, web access and Android.
2. Pilot measures to validate: first-login success, time to find a decision, clarity of approvals, accuracy of balances and usability across multiple projects.
3. Possible development: independent companies and subscription plans, permanent domain, account recovery, broader notifications, payment corrections and reporting. These are planned directions, not existing features.
4. No claims about paying customers, revenue or investment returns are made here. Those require pilot evidence and a separate financial model.