Invite partner accounts with scoped access.
Per-app runtime access policies grant the portal to roles, named users, or managed accounts from claimed email domains — enforced at the edge.
Build portals for invited partner and customer accounts — order status, document exchange, and request queues. Every action is authenticated, audited, and pinned to a release.
Per-app access policies scope the portal to roles, named partner accounts, or claimed email domains.
Order status views, document exchange, request queues, and account detail panels.
Ship reviewed changes, tenant audit events, tests, and release gates by default.
Orders, documents, and partner requests
Partner actions per day
Relpin provides the primitives teams need to serve invited partner accounts on governed operational data, review sensitive changes, and keep every portal action traceable from draft to production.
Per-app runtime access policies grant the portal to roles, named users, or managed accounts from claimed email domains — enforced at the edge.
Server-side SQL reads operational order data. Each account sees only the records it is scoped to — nothing is exposed publicly.
Documents are referenced server-side, and every shared-document action is recorded with the acting account.
Ticket-like requests move through open, in-review, and answered states, with your team handling each one inside the portal.
Row-level audit triggers capture field-level changes and the acting account — append-only, enforced at the database level.
Schema, access policies, and UI changes move through DEV, TEST, and PROD as reviewed artifacts with approval gates.
Start with a governed portal for invited accounts, connect operational data, and ship changes through deterministic Relpin releases.
Open beta · Invited accounts only · Governance-focused
Order status · Document exchange · Request queues · Audit trails