Guided family setup
A six-digit email code verifies the account before the family, household and head login are created in one transaction.
Family core
One family,
Create the family once, then invite the people who belong to it — each with a household, a role and a private way in.
One family,
everyone in their place.
Create the family once, then invite the people who belong to it — each with a household, a role and a private way in.Arabic & English · Invite-only membership · Server-enforced family access
Email-verified setup Expiring invitations Session control
Family core
Identity before any module.
The family is the first record: who belongs, where they live and what they may do.Invitations bound to a place and a role
Invite a spouse or child into a specific household as a specific role; tokens are hashed, expire after seven days and work once.
A member directory that means something
See every member with their household, roles and lockout state — and resend or revoke pending invitations.
Profiles with a face
Display name, phone and a 512-pixel WebP avatar; verification badges stay with the member across the platform.
Devices under control
List active sessions, revoke one device or sign out everywhere; changing the password ends the other bearer sessions.
A clan, not just a login
Add households under one clan; the ClanHead is present in every household and headship can transfer when the family decides.
Built-in controls
The family decides who gets in.
Membership is not a public sign-up: invitations, roles and sessions are controlled at the server.Roles checked twice
Every page is authorized, and each service call re-validates the role — only parents invite, only heads oversee.
Invites never stored in the clear
Only a SHA-256 hash of each invitation token is kept; the link expires and cannot be replayed.
Plan limits are enforced
Trial households and members are guarded when they are created, not merely hidden in the interface.
Every identity action is audited
Provisioning, invitations, resends, revocations and acceptances leave an audit event behind.
From first email to a full household
Five steps, one family.
No spreadsheets of usernames, no shared passwords.Verify your email
Enter the six-digit code and watch it expire if you wait too long.
Name the family and household
Choose the trial modules; the head login receives Parent and ClanHead.
Invite your people
Pick a household and a role for each invitation.
Accept and join
The invitee sets a password and lands in the right household.
Keep it current
Photos, phones and devices are maintained from the profile page.
One identity for six modules
Why it matters
The family is the boundary.
Every module asks the same identity service who belongs, and every answer is scoped to your family.
- One account per member, never shared
- Invite-only — no public sign-up into a family
- Family isolation enforced in the data layer
- Parent, Child and ClanHead roles
- Sessions can be revoked device by device
- Identity changes are audited
Connected by identity
Every module starts here.
Family core hands the other five modules their people, roles and households.Family tree
Living members claim their node; the tree shows who is You and who is Linked.
Memories
Member names and avatars drive photo tags and the people filters.
Finance
Every account, deposit and loan records the family member behind it.
Vehicles
Owners and drivers come from the family roster, not free text.
Quran
Bookmarks and memorisation progress stay attached to the member's family account.
Email and audit
Invitations, recovery codes and identity events leave through one audited path.
Start today
Bring your family in.
Create the family once; every module will know who belongs.
Arabic & English · Private by design · Part of the Sulala platform