Platform owner
Manages businesses, plans, entitlements, lifecycle, risk, billing actions, platform analytics, support, and product configuration.

A SaaS platform needs more than subscription pricing. It must separate tenant data, roles, configuration, limits, communication, billing state, support, and owner operations while keeping the product coherent.
Manages businesses, plans, entitlements, lifecycle, risk, billing actions, platform analytics, support, and product configuration.
Own profile, brand, users, configuration, data, usage, subscription, integrations, and role-safe daily dashboard.
Owners, admins, agents, staff, customers, or viewers see only the data and actions their business and role permit.
Owner details, business identity, agreement, password, abuse controls, and duplicate checks.
Time-limited code, resend controls, rate limits, expiry, feedback, and recovery.
Tenant record, owner membership, secure key, default plan, trial dates, and isolated settings.
Business profile, product setup, users, domains, integrations, first success action, and completion state.
Daily dashboard, notifications, usage, support, settings, audit, and role-safe collaboration.
Upgrade, downgrade, trial expiry, payment state, grace, limits, cancellation, export, and reactivation.
Every protected feature should be evaluated by the backend using the current tenant, plan state, entitlement, limit, and lifecycle. The interface then explains what is available and why an action is locked.
| Layer | Question | Example |
|---|---|---|
| Plan state | Is the subscription usable? | Trial active |
| Entitlement | May this tenant use the feature? | Advanced analytics |
| Limit | How much may they use? | Five agent seats |
| Role | May this user perform the action? | Owner manages billing |
Search, inspect lifecycle, owner, plan, trial, usage, installation, risk, and recent activity.
Prices, currencies, limits, entitlements, manual activation, payment hooks, renewals, and failed states.
Signups, verification, errors, email, notifications, storage, background jobs, integrations, and incidents.
Authorized impersonation policy, tickets, administrative actions, sensitive changes, exports, and evidence.
Visual filtering is not isolation. Backend queries, files, sockets, exports, background work, analytics, cache keys, notifications, and administrative actions must all verify tenant and role boundaries.
Starlife will map the platform owner, client workspace, account lifecycle, entitlements, architecture, and delivery stages.