Your tenant signs in to one screen carrying their lease, their cheque schedule, their documents, their maintenance requests and their move-out. They can sign the contract, raise a request and ask to leave; everything else is read-only, and that boundary is enforced in the database.

The portal opens on the active contract: the unit, the dates, the rent, the deposit and the payment frequency. Expired and terminated contracts are filtered out, because a tenant's question is almost always about the lease they are living under.

An unsigned contract raises a banner in the portal. The tenant draws their signature, it is stamped with the time, and their signature status moves to signed. They can download the contract PDF afterwards — the same document you see, resolved through the same call rather than a copy made for them.

Every cheque with its due date and status, and a count of those cleared. They can read it and they cannot change it: the policy behind the view grants select and nothing more. If they have utility bills recharged to them, a Utilities tab appears — and only then.

A maintenance request is raised with photographs and videos and a priority, and it arrives on your side marked as coming from the tenant. Whether they can reply on the thread afterwards is a switch you control per request. Their documents and their Ejari certificate open through links that expire. A move-out request is submitted from the same screen.

No. It is the same browser application, opened on a phone. There is no mobile app today and the site does not claim one.
The demo opens instantly, in the role this workflow belongs to, on sample data. There is no account to create and no form in front of it.