Set up the company account

Introduction

Company setup defines how the lab appears inside Kashef and how patients see the lab on receipts, invoices, reports, and portal pages. Treat this page as the source of truth for the lab identity.

The goal is not to fill every possible setting on day one. The goal is to make the workspace reliable enough for staff training and the first real order. Start with the settings that affect every record: company name, logo, language, currency, branch identity, contact details, report identity, and billing plan.

Company identity

Open Administration > Lab Settings and review the company profile. Add the legal lab name, public display name, primary phone number, public email, tax details if applicable, and the brand logo used on reports and invoices.

Use the public display name patients recognize. If the legal name is different, keep it in the billing or tax fields while using the recognizable brand name for patient-facing material.

Upload a clean logo with enough contrast for white backgrounds and printed reports. A poor logo makes reports look unprofessional and can be hard to read when printed in black and white.

Locale, direction, and currency

Kashef supports Arabic and English. Choose the language your team will use most during daily work. Arabic switches the panel to right-to-left direction, while English uses left-to-right direction.

Set the currency before entering prices or taking payments. Currency affects catalog pricing, invoices, cash collections, reports, and financial reconciliation. Changing currency after live financial records exist can make reports confusing.

If your team works in both languages, test the main workflow in Arabic and English before training. Confirm that staff understand field names, statuses, and printed document labels in the language they will use.

Branch and contact defaults

The first branch usually becomes the main operational location. Add its address, phones, service area, and working notes. If the branch offers home visits, define the service radius and make sure the dispatch team understands which areas can be accepted.

Branch context matters throughout the Lab Panel. Orders, samples, inventory, cashier activity, reports, and staff access usually belong to a selected branch. Confirm the active branch before reading numbers or creating records.

If your lab has more branches, add them after the main branch is correct. Branches should not be created as duplicates just to test the system. Use clear names such as "Main Branch", "Nasr City Branch", or "Alexandria Branch".

Billing and plan limits

Review the active plan before inviting staff. Some modules may depend on the subscription level, such as advanced permissions, automation, inventory, home visit dispatch, portal features, or AI assistance.

If a module is not available in the plan, decide whether to upgrade before training the team. It is better to know limits early than to train staff on a workflow they cannot use.

Report and document identity

Before creating real orders, confirm the report header, footer, signatures, QR behavior, and public contact information. Reports are clinical documents, so their identity must be correct from the start.

At minimum, verify:

• Logo and lab name.
• Branch address and phone.
• Footer text and patient instructions.
• Signature areas or reviewer identity.
• QR code or verification link behavior.

If an email-verification link is expired, incomplete, or already used, Kashef shows one private recovery page without displaying account details. While signed in, select Send a new verification link and use only the newest message. If you opened the link in another browser, sign in to the intended account first.

• Default language used on printed documents.

Do one test report before accepting patients. A report that looks wrong after release usually means the template or company identity was not reviewed early enough.

Operational defaults

Review defaults that affect daily work: order statuses, sample handling, payment methods, result review rules, and notification channels. You do not need to customize everything immediately, but the default workflow should match how your lab actually works.

If the lab requires payment before release, reviewer approval before portal visibility, or QC checks before result release, configure those expectations before go-live.

Password recovery privacy

On Forgot password, Kashef always shows the same confirmation whether or not the email belongs to an account. This protects staff account privacy. The message means only that the request was accepted; it does not confirm that an account exists. Check the inbox and spam folder, then ask an administrator to verify the staff profile through an authenticated channel if no message arrives.

A temporary login lockout does not block access to Forgot password. Recovery requests have a separate abuse limit; if it is reached, wait for the displayed retry period instead of repeating the request.

After repeated failed sign-in attempts, Kashef replaces the login form with a Sign-in temporarily paused page. It shows the retry countdown and a password-recovery link. Wait for the countdown before trying again; administrators do not need to deactivate the account for this short protection window.

Setup checklist

Before moving to onboarding, confirm:

• The company name and logo are correct.
• The language and direction are comfortable for the team.
• The currency is final for live work.
• The main branch exists with correct contact details.
• The plan supports the modules you intend to use.
• Report identity has been reviewed.
• The owner knows who will be invited as manager, reception, technician, and finance staff.

When those points are ready, continue with Complete onboarding.