A customer discovers a useful second website and encounters a familiar question: do I need another account? A reusable account gives participating services a common way to accept an account the customer already has. It can remove a repeated account-creation step while allowing each business to offer its own service.
If you are researching single sign-on for multiple websites, start by separating three decisions: which account the customer uses, when the customer signs in, and what information or access belongs to each service. Those decisions determine what you can honestly promise on your website.
What does one account across websites mean?
A reusable customer account is an account accepted by more than one participating service. With Gammal Tech, the customer uses their Gammal Tech account through the website’s integration. A participating website is one whose owner has connected that account flow; the account does not work automatically on every website on the internet.
Account registration and service onboarding answer different questions. Registration establishes the Gammal Tech account. Service onboarding helps a particular website understand what the customer wants to do there, such as choosing a tool, selecting a learning goal, or setting a display preference. Reusing the account does not remove information genuinely needed for that service.
For a customer who already has a Gammal Tech account, the next participating website can offer access using that existing account. A customer who has never joined Gammal Tech first needs to complete the account-creation process.
An example: using the same account on a second website
Consider a learning website and a separate planning tool that both integrate Gammal Tech. This is an illustrative customer journey, not a claim that these specific services are current partners.
- The customer uses the learning website. They sign in with their Gammal Tech account and use the learning experience that website provides.
- Later, they visit the participating planning tool. The tool offers Gammal Tech sign-in. The customer can use the account they already have instead of creating a second Gammal Tech account.
- They complete hosted sign-in for the planning tool. The website opens the Gammal Tech login window and confirms the resulting session. The earlier visit does not promise automatic sign-in here.
- They begin the planning task. The planning tool may ask them to choose a goal or enter details relevant to its own service. Their learning records are not automatically imported into a separate project.
The reusable element is the Gammal Tech account. The learning experience and the planning experience remain products with their own purposes. This is also the distinction to explain when a partner recommends your website to an existing account holder.
Is account reuse the same as single sign-on?
Account reuse and single sign-on describe different parts of access. Account reuse means using an existing account at another participating service. Single sign-on, or SSO, generally means authenticating once and then accessing other connected applications without another credential prompt while the relevant session remains valid.
For example, Auth0’s SSO documentation describes access to connected applications through an existing authentication session. Gammal Tech’s documented Web SDK flow provides account reuse with hosted sign-in and a session kept per browser tab. A fresh tab or reopened browser requires sign-in again.
| Arrangement | What the customer should expect |
|---|---|
| Separate website accounts | Each website requires its own account. Joining another service can introduce another registration process. |
| Gammal Tech account reuse | Participating websites accept the existing Gammal Tech account. The customer still signs in for the current website session. |
| Session-based single sign-on | Connected applications can accept an existing authentication session, subject to that SSO system’s configuration and policies. |
Use precise wording in your product: “Use your Gammal Tech account” describes the reusable-account benefit. “Sign in once and stay signed in everywhere” would promise different session behavior. For the browser experience itself, see the popup login guide.
What stays separate between participating websites?
| Customer question | What account reuse establishes |
|---|---|
| Does the next website receive my contact details? | The documented login does not return the account’s email address, phone number, or identity details to the partner website. |
| Does another project receive my saved information? | Saved information belongs to its account-and-project context. Do not expect an unrelated project to receive that data automatically. |
| Do purchases or memberships transfer? | An accepted account does not by itself establish a subscription, purchase, membership, or permission in another service. |
| Will an older website account be merged? | Automatic account linking and migration of existing website records are not documented parts of this flow. |
A participating website can use information saved for the same account in its own project across visits and devices. That continuity is useful when returning to the same service; it should not be described as a universal profile shared by every partner. The privacy-preserving login guide covers the account-privacy model in more detail.
How does a website become a participating service?
The website owner sets up a Gammal Tech project, registers the HTTPS domains that will use it, and integrates the Web SDK. The website then offers Gammal Tech sign-in and connects the confirmed session to its own customer experience. Adding an ordinary link to another website is not the integration.
For a startup launching another product, decide what the new service needs after sign-in: which task the customer can start, which details are necessary, and which access rules the product must enforce. The reusable account supplies a way to sign in; it does not create the whole product or its membership rules.
Follow the existing guide to adding user login for setup requirements and current account costs. To evaluate the business case before integration, read the benefits of reducing repeated registration.
Common questions
Can one account be used on multiple websites?
Yes, when those websites accept the account through an appropriate integration. Gammal Tech customers can use their existing Gammal Tech account on participating websites; an unrelated website does not automatically accept it.
Does using the same account mean I am already signed in?
No. Reusing the account avoids creating another Gammal Tech account. The documented website session is kept per browser tab, so a fresh tab or reopened browser requires sign-in again.
Will customers still need to fill out a registration form?
Existing Gammal Tech account holders do not need another Gammal Tech account for each participating service. A website may still request information needed for its service, and new Gammal Tech users first need to create their account.
Does a universal account work with every website?
Only websites that participate in the account system can accept it. Describe Gammal Tech as a reusable account across participating services rather than promising acceptance everywhere.
References and further reading
- Gammal Tech API reference — account flow, project setup, sessions, privacy, and saved project data.
- Auth0: Single Sign-On — reference for the session-based SSO distinction; its product capabilities are not attributed to Gammal Tech.
- Benefits of single sign-on: where reusable accounts fit — business value, repeated registration, and practical measurement.