Customer identity and access management for startups

Start with the customer experience you need

A learning service may need returning lesson progress. An agency portal may need to show a client only their own project information. A team product may need administrators, members, and billing permissions. These experiences share a need for sign-in, but their access rules differ.

Write down the account journey and the permission decisions separately. This makes it easier to choose services without buying capabilities you do not need or assuming that a basic sign-in feature supplies every business control.

What Gammal Tech provides

These features are useful for preferences, progress, and compact personal app state. They do not by themselves establish a complete team-management, enterprise directory, or organization-role system.

Customer portals and multiple domains

Each project can have up to four registered HTTPS domains. A business may use those slots for its main site and selected application or portal subdomains. The bare domain and its www version count separately. Browser API requests for account features use these registered domains as the project’s whitelist. The project ID is public configuration, and no secret developer API key is required.

Registered subdomains can share the project’s users and payments. That does not mean automatic sign-in across every tab or device: sessions are kept per browser tab, and a fresh tab or reopened browser requires another sign-in. A session token remains a sensitive credential and must be protected even though the project ID is public.

Before choosing a project structure, list all the website addresses you plan to use. A clear domain plan avoids promising more sites under one project than the documented four-domain limit allows.

Guest payment links are a separate public, shareable flow. They can be opened from anywhere without a secret API key or a domain whitelist. Sharing the same link does not change the receiving owner.

Privacy and customer information

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. When your project retrieves saved customer data, it receives only what that project previously stored for the same authenticated account. This supports returning preferences without exposing the underlying account profile.

If a client portal requires a billing contact, delivery address, or business profile, it can ask the customer directly for that information. This is a separate collection through your own forms, not a request to Gammal Tech for the underlying account details. Your forms and saved documents can therefore still contain personal data.

Who can see what remains a product decision

A valid session establishes that the user is signed in. It does not alone establish which company records they own or whether they should have administrative privileges. Your business must arrange appropriate controls for those decisions.

When evaluating a provider, ask about the specific features you need: organization membership, account migration, support processes, session controls, and any required reporting. Confirm requirements that go beyond the published sign-in and user-data features before committing to a customer promise.

Setup and pricing for customer sign-in

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.

Each person has one Gammal Tech account, and every account requires national ID verification. Existing account holders reuse that account on participating websites. The national ID number and verification documents remain private from developers. The owner creates a project in the Developer Console and registers the required HTTPS domains before integration. No secret developer API key is needed.

The code allowance includes codes sent during login and checkout identity verification, and resets monthly. Paid usage comes from the project balance: add funds to your personal wallet, then transfer them into the project. The first project is free; additional projects have a one-time fee shown in the Console.

Common questions