Trust
Billing and access
Client access is tied to assigned workspace membership, and live publishing can require active Devport Access.
Access model
Clients receive access to a specific Devport workspace. Access depends on verified identity, assigned workspace membership, and the workspace access state.
Subscription direction
Paid client workspaces can require active Devport Access before approved updates are published to the live website.
Assigned clients can still enter their workspace, edit approved fields, save drafts, and preview safely before payment.
Active subscribers can use Manage billing in Devport to open Stripe's secure billing portal for payment methods, invoices, and cancellation.
Subscription changes happen in Stripe and sync back to Devport through the billing webhook. Real paid customer launch should wait until Devport confirms billing, support, and legal readiness.
What clients should expect
- The developer or Devport operator issues or approves workspace access.
- The client signs in through the supported Devport identity path.
- The client sees only assigned projects.
- If billing is required, drafting and preview remain available, but publishing requires active Devport Access.
- The client can cancel or update billing from the Manage billing action without receiving Stripe dashboard access.
- Support is available if access or billing state looks wrong.