Account onboarding and subscriptions
How users are invited into Pluck, where onboarding lives, and how subscription management is surfaced.
Help updated for v0.10.21 · 2026-07-13
Inviting users
User invites are designed to keep onboarding inside Pluck. Admins can still use verification and password-reset emails, but the preferred path is a clear onboarding link that explains the next step to the new user.
After creating a user, send the invite message that matches how your team communicates. The link helps the person verify, set a password when needed, and land in the app with less guesswork. If someone cannot sign in, check whether the account is verified, whether a temporary password still needs to be changed, and whether the user belongs to the expected company.
In practice, company and platform user-management screens now favor a shareable Pluck onboarding link instead of auto-sending a verification email immediately. That invite flow keeps the visible user experience inside Pluck while verification and password-reset emails remain available as fallback actions. Invite actions can copy a full message, a direct onboarding link, or still trigger backend verification/reset email delivery when needed. Admin user-management screens can mark users verified and generate temporary passwords without leaving Pluck. Unverified users are blocked from normal app use until verification is completed or an admin marks the account verified. Users with admin-generated temporary passwords must set their own password on next login before continuing into the app. Company security settings can leave sessions unlimited or set a maximum session age in days.
Onboarding walkthroughs
Walkthroughs are lightweight reminders, not permanent popups. They introduce important workflows and are versioned so users only see automatic guidance when something meaningful changed.
Admins can globally enable or disable automatic versioned onboarding tutorial popups from the platform admin controls.
In practice, the manual replay entry points are hidden for now while the tutorial experience is revisited. Major feature updates can still use the same versioned walkthrough system when the app needs a focused guide.
Account agreements
Agreements keep acceptance visible and auditable. When agreement text changes, Pluck records the version a user accepted so support and administrators can tell which terms were acknowledged.
Tenant owner accounts are required to accept the current EULA, plus the Beta tester NDA when that global agreement switch is enabled.
In practice, platform admins can require either agreement for individual company users from Admin -> Company users. Admin global settings control the current agreement text; versions update automatically when the text changes. Accepted users keep a timestamped snapshot of the terms they acknowledged on their user record.
Subscriptions
Subscription information controls which features and limits are available to a company. User-facing billing should explain what is available without exposing internal or not-applicable platform features.
If a feature appears locked, the subscription or entitlement is usually the first thing to check. Pluck should make unavailable features understandable instead of mysterious: users should know whether something is included, unavailable for their plan, or not applicable to the way their company is configured.
In practice, subscription plans are managed from the admin console, and eligible companies can now open Stripe checkout from `Settings -> Company -> Billing` when billing is configured. Internal beta access can be assigned by admins without appearing as a purchasable plan. Plans can now carry structured limits for user count, serialized item count, and API access so future billing enforcement uses shared hooks. Customer-facing billing hides feature rows marked Not applicable so unavailable internal features do not look like upgrade options. Stripe webhook processing now updates tenant subscription records, but more advanced billing actions like customer portal, upgrades, and cancellations may still be added later.