Registration and Onboarding
The current NowToPrint signup, usage-type onboarding, activation, and launch package model.
Registration and Onboarding
NowToPrint keeps the first signup screen frictionless. Users create a personal account first, then choose how they will use the platform from onboarding cards and complete profile or approval steps in the dashboard.
Flow
Signup
-> email verification
-> usage type cards
-> dashboard activation timeline
-> profile and approval steps
-> package/permission-based usage
Signup screen
Signup collects only:
- first name
- last name
- password or Google login
- legal consent
Company name and tax details are not collected on the first signup screen. Account intent is selected during onboarding; corporate customer, print producer, and supplier accounts complete company/business profile information before onboarding is marked complete.
Usage type
| Usage type | Internal key | Initial access |
|---|---|---|
| Individual customer | individual_customer | Dashboard |
| Corporate customer | corporate_customer | Dashboard |
| Agency / Broker | agency | Limited dashboard, pilot/approval |
| Print Shop / Producer | print_producer | Approval notice and limited dashboard |
| Supplier | supplier | Approval notice and limited dashboard |
Agency / Broker, Print Shop / Producer, and Supplier accounts cannot publish public listings or use producer/supplier operational actions until platform approval is complete.
Workspace and profile
Individual-customer onboarding can complete without company information. Corporate customer, print producer, and supplier onboarding requires company/business profile details before the account is marked complete.
Producer and supplier accounts still require platform approval before marketplace publishing, quote operations, supplier actions, paid invoicing, or Enterprise onboarding.
Dashboard activation
The dashboard uses activation language instead of internal IAM wording:
- Account created
- Email verification
- Usage type
- Profile details
- Platform approval
- Package status
User-facing copy uses "account contact" instead of "owner" where possible.
Launch packages
| Package | UI label | Seat limit | Team invites |
|---|---|---|---|
free | Free | 1 | Disabled |
starter | Starter | 1 | Disabled |
pro | Pro | 1 | Disabled, pilot/waitlist |
enterprise | Enterprise/Kurumsal | Future multi-user | Sales/platform approval |
Pending invites count against the seat limit. Single-user packages cannot create a second active member or a second pending invitation.
Platform users
Platform admins are not created by public signup. A person signs up as a normal user first, then a platform role request is created. A different platform_owner can approve or reject the request; the role activates only after approval and verified email.
هل كانت هذه المقالة مفيدة؟
مقالات ذات صلة
آخر تحديث