The organization workspace is intentionally simple: Dashboard · Projects · Customers · Production · Notifications · Settings. New Project remains a prominent action without becoming permanent navigation clutter.
Getting started
Create an organization workspace, choose your project-number prefix, configure customer intake, and invite your internal team.
Projects
Projects are the operating record. A project can contain one or many products, sourcing details, artwork, garment specifications, invoices, files, vendor information, and production releases.
Customer intake
Each organization can publish a mobile-friendly Start a Project link. Customers can submit contact information, project type, product preferences, quantities, sizes, artwork placement, desired graphic size, hat details, notes, and reference files without a Fourth Rein login.
Artwork & garment approvals
Artwork proof versions and garment specification versions can be sent through secure customer review links. Customers can approve or request revisions, and Fourth Rein preserves the version and decision history.
Products & sourcing
Track preferred brand/style, product color, supplier, supplier SKU, source URL, availability/sourcing status, size quantities, decoration method, placements, graphic size, and hat-specific profile/closure/bill details.
Customer status
Every project can have a permanent unguessable read-only status link. The customer sees the project number, workflow stage, target date, and customer-relevant product information—never internal notes, sourcing notes, vendor pricing, or private production files.
Invoices & payments
Record invoices, payment links, due dates, payments received, and payment methods. An organization can require a specified amount to be recorded before production release is allowed.
Production
Assign vendors, upload vendor-visible production files, and release a project only after required approvals and payment gates are satisfied. The production release snapshots the exact approved garment specs and vendor-visible files for that run.
Project communication
Internal notes and customer messages are separate. Internal notes remain inside the organization. Customer messages appear on the customer status page and can follow the configured email-notification path.
Closing inactive work
Pre-production projects can be closed without deleting their history. Organizations can record reasons such as quote declined, customer canceled, no response, inactive, duplicate, or other, and can reopen eligible closed projects later.
Customer acknowledgments
Customer-supplied items and artwork/reference uploads can require acknowledgments. Fourth Rein stores the accepted policy version, text snapshot, customer identity, acceptance method, and timestamp.
Security & team access
Organization Owners and Admins use authenticator-app 2FA. Team roles and permissions control who can work with artwork, production, sales, billing, settings, or view-only information.
Current v0.11 scope
v0.11 keeps the v0.10 project-governance foundation and adds the public Fourth Rein website and organization-focused documentation. The customer-facing and organization-facing experience remains mobile-friendly and built around the same project record.