How to add user login and authentication to a website

What you need before starting

The project owner uses their existing Gammal Tech account or creates one if they do not have one. Every account requires national ID verification, and each person can have only one account. The national ID number and verification documents remain private from developers. The owner then opens the Developer Console to manage the website’s project.

Your website must use HTTPS. Register its exact hostnames, including both the main domain and its www version if visitors use both. Each project supports up to four registered domains. Browser API requests for account sign-in and saved user data must come from the project’s registered domains. The project ID is public configuration; no secret developer API key is required. The first project is free; additional projects carry a one-time fee shown through the account.

Five steps to add user login to your website

1. Choose the account benefit. Decide which preferences, saved items, or progress visitors should recover after signing in.
2. Set up the owner and project. Complete verification, create the project, and register the website’s HTTPS domains.
3. Add the sign-in experience. Have your developer connect a clear sign-in button to Gammal Tech’s hosted popup.
4. Design the signed-in view. Confirm the session before showing account-specific information, and provide a visible sign-out option.
5. Connect saved preferences. After sign-in, load only the data your project previously saved for that account, and save deliberate changes as the visitor uses the site.

How Gammal Tech fits your existing website

For an established customer base, plan how existing records will connect before replacing the old login. Gammal Tech does not supply underlying account contact or identity details for matching, and developers cannot request them through a separate API lookup. The session token is a sensitive session credential, not a permanent customer identifier for linking records. Automatic migration is not a documented feature.

Remember returning visitors without collecting contact details

Each signed-in user can have up to 1 MB of saved project data, available again across visits and devices. When retrieving customer data, your project can access only the data it previously stored for that same account. Useful examples include a preferred dashboard layout, a reading list, or learning progress. Storage is free within this size limit.

Gammal Tech does not disclose the customer’s underlying account name, email address, phone number, national ID number, or identity documents to your project, through login or a separate API lookup. If a display name is useful, visitors can provide one voluntarily in your own form. That is information your website collects directly, not information obtained from the underlying Gammal Tech account. Saved preferences should describe their experience; they should not be the sole authority for administrative access or paid benefits.

Pricing and checks before launch

Currency guide: Listed EGP prices are the billing amounts. USD figures are approximate, using USD 1 = EGP 51.78, the calculated midpoint of Banque Misr’s USD buying and selling rates on 24 September 2026. Your payment provider’s exchange rate and fees may differ.

Login, logout, and session verification are free. Login codes have a separate allowance: 200 OTP codes per project per month, then 0.40 EGP (approx. US$0.0077) per additional code. The allowance also covers codes sent during checkout identity verification.

For paid usage, top up your personal Gammal Tech wallet and transfer funds into the project balance. Paid OTP operations stop when that project balance is exhausted.

Before release, check sign-in, popup cancellation, sign-out, and saved preferences on another device. Sessions are kept per browser tab, so a fresh tab or reopened browser requires sign-in again; saved user data remains available after the user signs in.

Common questions