How Rimas360 separates companies, controls who sees what, and records every change to access.
Every company is its own tenant. Reads and writes are scoped to that tenant on the server, never by what a browser sends.
Only people a company has invited can sign in. Someone on the company's email domain can ask to join; an administrator approves.
Fourteen hotel roles with editable templates, per-user grants, and access limited to the properties each person is assigned.
Optional second step by emailed code: it expires in 10 minutes, allows five tries, and can remember a device for 30 days.
Every administrative and permission change is written to an audit log the company can read.
When Rimas360 support signs in as a user, it lasts at most two hours, a banner shows on every page, and every action is logged with the support person's name.
The services Rimas360 runs on today.
| What | Provider | Where |
|---|---|---|
| Database | Supabase (PostgreSQL) | AWS us-east-1 |
| Application hosting | Vercel | United States |
| Sign-in | Google accounts | |
| Transactional and inbound email | Resend | Provider-managed |
We will answer your security questionnaire and walk your team through access and data handling.
