Connection 01
Tenant-scoped data
Company records, settings, connections, payments, inventory, and workflows are resolved in the active tenant context.
Security and control
Rivet is built around tenant-scoped records and explicit permissions so the people operating one rental company do not inherit access to another.
What connects
Connection 01
Company records, settings, connections, payments, inventory, and workflows are resolved in the active tenant context.
Connection 02
Sensitive settings and operating actions require the appropriate tenant or platform permission.
Connection 03
Renter card details are entered in Stripe-hosted checkout rather than a Rivet card form.
How it works
Each stage preserves the customer, rental, tenant, and operating context needed by the next one.
Users access a company through an active membership and role.
Rivet scopes operating requests to the company selected for that authenticated user.
Management, billing, payment, and platform functions apply explicit authorization checks.
Supported workflows retain identifiers and audit context for important changes and external events.
Operational outcomes
01
A multi-tenant platform can support separate rental businesses without treating them as one shared account.
02
Stripe handles sensitive card entry and the tenant controls its connected payment account.
03
Permissions and recorded workflow state make sensitive actions easier to review.
Questions
No. Supported card payments use Stripe-hosted checkout.
Rivet supports company memberships and an active-company context while preserving tenant-scoped access.
This page describes implemented product controls. Rivet does not claim a certification that has not been independently completed.
Use the Get Started form and identify the message as a security concern so it can be routed for review.
Keep exploring