A useful client dashboard should make it easy to return to a project, review an update or continue a course. If every visit begins with remembering a separate portal password, the sign-in process can distract from the service customers came to use.
With Gammal Tech, a portal can use hosted account login instead of storing its own customer passwords. Clients sign into their Gammal Tech account in a popup, and the website can confirm the resulting session before continuing the account experience.
Design the returning-client experience
The clearest portal journey starts with a visible sign-in choice and explains which account the customer needs. After sign-in, the portal can retrieve saved personal settings such as a preferred dashboard view or a draft the person was working on.
Gammal Tech sessions are kept per browser tab. Opening a fresh tab or reopening the browser requires sign-in again. Saved user data persists across visits and devices, so the portal can restore appropriate settings once the customer signs back in.
A visible sign-out option is especially helpful on shared computers. Sign-out clears the local session; the portal must also remove private information from its displayed pages. Closing a tab should not be presented as a substitute for a clear sign-out experience.
Features that support customer portals
| Portal | Useful account experience |
|---|---|
| Agency client dashboard | Remember preferred filters, saved views and presentation settings when a client returns. |
| Learning platform | Save personal learning preferences or practice progress and retrieve them after sign-in on another device. |
| B2B customer area | Provide hosted account sign-in alongside your business's own membership and record-access rules. |
| Project workspace | Keep modest personal drafts or settings without building a separate preferences database. |
Each user's stored data has a maximum size of 1 MB. Treat this as personal application state, not a general file repository or an authority for granting access to paid resources.
A project supports up to four registered HTTPS domains. A main website and a portal subdomain can share that project; register every domain used. Separate domain registration does not create automatic sign-in across browser tabs.
Connect the account to the right customer experience
Gammal Tech login does not disclose the person's account email, phone number or identity to the portal. This reduces the contact information your frontend receives through authentication. It also means a new session cannot automatically be matched to a customer record by email.
For an existing client portal, plan a suitable account-linking process before launch. A signed-in person should receive access to an organization, project or purchase only after your service establishes the correct relationship.
- Keep customer records separated. Your service needs to enforce which records each account may see or change.
- Control staff permissions explicitly. A valid session alone does not make a person a manager or administrator.
- Keep payment access trustworthy. Paid entitlements should follow verified payment and business records, not a setting the customer can edit.
If a portal needs an email address for notifications, collect and verify the necessary contact information separately. Gammal Tech owner notifications go to the project owner only and are not a customer mailing service.
What does portal login cost?
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.
Gammal Tech login, logout and session verification are free. Personal storage is free within its 1 MB per-user limit. Your first project is free; additional projects have a one-time creation fee.
Login and checkout identity-verification codes share an allowance of 200 OTP codes per project per month. Additional codes cost 0.40 EGP (approx. US$0.0077) each. Estimate this from code usage rather than the number of clients: a customer may need to sign in on more than one visit.
For example, 600 OTP codes in one month leave 400 after the allowance, costing 160 EGP (approx. US$3.09). This covers OTP usage only; AI, owner notifications and payment services have separate pricing.
Top up the owner's personal wallet and transfer money into the project's separate balance for paid usage. Paid OTP operations stop when the required project balance is unavailable, so include funding in your portal's operating plan.
Common questions
Can my portal use its own subdomain?
Yes. Register the HTTPS portal domain in the project alongside other website domains you use. Each project supports up to four registered domains.
Will login identify the customer by email?
No. Gammal Tech confirms the signed-in session without sharing email or phone details. Existing customer records require a separate account-linking process.
Does logout clear everything shown on the portal?
It clears the local session. Your portal must also clear its displayed private information and continue enforcing access permissions.
References
- Gammal Tech API and SDK reference — account login, privacy, storage, domain limits and pricing.
- Privacy-preserving login — what account login shares with your website.
- OWASP Authorization Cheat Sheet — permissions and access decisions.