Authentication
WorkOS authentication for Renaro
Renaro uses WorkOS as the authentication foundation so operator identity, organization context, roles, and account access can remain explicit.
- Web
- AuthKit sessions
- Mobile
- PKCE flows
- Context
- Org-scoped requests
- Roles
- Operator capabilities
Authentication supports tenant isolation
Identity is not just login. It defines which organization, role, account, and capability a user operates within.
- Map authenticated users into request context before server work executes.
- Use organization context to scope tenant data access.
- Support role and capability patterns for operator workflows.
Where this page fits
Auth integration pages help enterprise and technical buyers understand the security posture behind the product.
- Link WorkOS content to security, tenant isolation, and corporate accounts.
- Keep the landing app static while documenting the operational auth model.
- Avoid claiming certifications or SSO setups that are not visible in the product.
Related integration paths
Common questions
Are integrations implemented directly in the landing app?
No. The Astro landing app documents and routes SEO traffic to Renaro's product areas. Operational integrations are owned by the API, worker, and platform domains.
Why create integration landing pages?
Operators and technical buyers search for specific provider support. These pages state the current data and workflow boundary and link to capabilities that are available today; they do not imply that an unconfigured OAuth connector is live.
See Renaro with your own trips.
Bring a few of your real reservations. We'll show you how your office would handle them in Renaro, from the first phone call to the paid invoice.