This covers OotlaAI’s development preview, staff workspace and separate applicant portal. Establish customer deployment details and provider notices before rollout.
Updated 23 October 2026 · Scope: this application's development previewExamples are scripted. Private work is saved behind separate access checks.
Invented AI scenarios and onboarding choices use browser memory only: no customer records, messages, localStorage or sessionStorage. Reload resets them.
Pages, fonts, branding and photos are served locally. Photos are illustrative, not customer records or testimonials. No Google Analytics, advertising tags or external AI calls are active.
Database authentication uses hashed passwords and server sessions; authentication activity is recorded. Backend organization, role and property permissions apply. Public pages load no private staff data.
Essential ootla.sid: HttpOnly, SameSite=Lax and Secure in production. Sessions expire after eight hours; sign-out revokes them. Demo records are synthetic.
Applicants save details, private checklist files and consent in the database, then submit when requirements are met. Submission is not screening, approval or a lease.
Separate essential ootla.applicant.sid: HttpOnly, SameSite=Lax and Secure in production. Sessions expire after eight hours; sign-out revokes them. Invitations expire or can be revoked; access requires an active application grant.
Co-applicant details and files stay private. Authorized staff can review; downloads require authorization. Applicant access grants no staff membership.
Contact us opens a pre-addressed email draft. You choose whether to send it.
Use invented demo information. Keep private applicant, resident, payment and screening records in authorized workflows.
Scripted AI, SMS and phone examples make no live calls or send messages. Invitations are copied links, never emailed or texted.
Yardi and Google Calendar depend on configuration, with explicit setup/simulation states. Onboarding and Analytics, maintenance or payment previews activate nothing.
Configured providers remain authoritative for owned records; Yardi retains accounting authority. OotlaAI hands payments to existing providers, never authorizing, capturing, charging or refunding. Customer rollout requires access, permissions, notices and consent.
Questions about this preview? Contact us. For customer records or access, also ask your organization’s administrator.
Contact OotlaExplore the working demo, follow a workflow and see how OotlaAI can support your property team.
