Quick Summary
Projects are organizational labels that help you group related requests together. Think of them as folders that keep your work organized, especially useful when managing multiple clients or websites.
What You'll Learn
- What is a project in Thrivepix
- Why projects matter for organization
- How projects work as labels
- Managing multiple projects
- Best practices for project organization
What is a Project?
A project in Thrivepix is a label or folder that groups related requests together. It's NOT a traditional project with start/end dates or milestones - it's simply an organizational tool.
Think of Projects As:
- Labels for categorizing requests
- Folders for grouping related work
- Containers for organizing by client, website, or category
- A way to keep your dashboard clean and organized
Projects Are NOT:
- Required to submit requests (they're optional)
- Time-bound with deadlines
- Requiring client information
- Limiting what you can request
Why Use Projects?
The Problem Without Projects
Imagine you have 100+ requests over time:
- All requests mixed together in one long list
- Hard to find specific client's work
- Difficult to track what's done for each website
- Confusing when managing multiple clients
- No way to see all work for one project
Example Chaos:
- Request #1: Client A homepage
- Request #2: Client B logo
- Request #3: Client A contact form
- Request #4: Client C landing page
- Request #5: Client A footer
Finding all Client A requests? You'd have to scroll through everything!
The Solution With Projects
Organize requests by project:
- Project: Client A Website
- Homepage
- Contact form
- Footer
- All Client A work in one place - Project: Client B Branding
- Logo
- All Client B work grouped - Project: Client C Marketing
- Landing page
- All Client C work together
Benefits:
- See all requests for one client instantly
- Track progress per project
- Keep work organized and findable
- Manage multiple clients easily
- Clean, organized dashboard
How Projects Work
Projects as Labels
When you create a request, you can assign it to a project:
- Create or select a project
- Submit request under that project
- Request is labeled with project name
- View all requests by project
Project Information
Projects only need:
- Project Name: How you'll identify it (required)
- Description: Optional notes for yourself
We DON'T Ask For:
- Client contact information
- Client company details
- Project deadlines or timelines
- Budget information
- Any sensitive client data
Why? Projects are just organizational labels for YOUR use. We don't need your client's information.
Project Naming Best Practices
Good Project Names
For Agencies Managing Multiple Clients:
- ✅ "Client A - Main Website"
- ✅ "Client B - E-commerce Store"
- ✅ "Client C - Landing Pages"
- ✅ "Acme Corp Website"
- ✅ "Smith & Co Rebrand"
For Your Own Websites:
- ✅ "Company Website"
- ✅ "E-commerce Store"
- ✅ "Blog Platform"
- ✅ "Marketing Landing Pages"
- ✅ "Internal Tools"
For Specific Campaigns:
- ✅ "Q1 2026 Campaign"
- ✅ "Product Launch Pages"
- ✅ "Holiday Promotions"
- ✅ "Website Redesign 2026"
Poor Project Names
- ❌ "Project 1" (not descriptive)
- ❌ "Stuff" (too vague)
- ❌ "Website" (which website?)
- ❌ "Test" (not meaningful)
- ❌ "asdfgh" (random characters)
Managing Multiple Projects
Typical Project Structures
For Agencies:
- One project per client
- Or multiple projects per client (website, branding, marketing)
- Keeps client work separated
- Easy to bill and track
For Businesses:
- One project per website/property
- Or projects by department (Marketing, Sales, Support)
- Or projects by initiative (Redesign, New Features, Maintenance)
For Startups:
- Main Product
- Marketing Site
- Landing Pages
- Internal Tools
Project Organization Strategies
Strategy 1: By Client
Best for: Agencies, consultants
- Project: Client A
- Project: Client B
- Project: Client C
Pros: Clear client separation, easy billing
Strategy 2: By Website
Best for: Businesses with multiple properties
- Project: Main Website
- Project: E-commerce Store
- Project: Blog
- Project: Landing Pages
Pros: Organized by property, clear ownership
Strategy 3: By Category
Best for: Varied work types
- Project: Website Development
- Project: Design Work
- Project: Bug Fixes
- Project: New Features
Pros: Organized by work type
Strategy 4: By Time Period
Best for: Campaign-based work
- Project: Q1 2026
- Project: Q2 2026
- Project: Holiday 2026
Pros: Time-based organization
Working Without Projects
Projects are optional! You can:
- Submit requests without assigning to a project
- All requests appear in your main queue
- Works fine for simple workflows
- Good if you only have one website
When to Skip Projects:
- You only work on one website
- You have fewer than 10 requests total
- You prefer a simple, flat structure
- You don't need organization
Project Features
What You Can Do
- Create Projects: As many as you need
- View by Project: Filter requests by project
- Assign Requests: Add requests to projects
- Move Requests: Change project assignment
- Archive Projects: Hide completed projects
- Delete Projects: Remove unused projects
What Projects Don't Do
- Don't limit request types
- Don't affect turnaround time
- Don't require client information
- Don't create separate queues
- Don't affect pricing
Project Workflow Example
Agency Managing 3 Clients
Setup:
- Create Project: "Client A - Website"
- Create Project: "Client B - Store"
- Create Project: "Client C - Landing Pages"
Daily Work:
- Client A needs homepage update → Submit request under "Client A - Website"
- Client B needs product page → Submit request under "Client B - Store"
- Client A needs contact form → Submit request under "Client A - Website"
- Client C needs new landing page → Submit request under "Client C - Landing Pages"
Result:
- All Client A work grouped together
- All Client B work grouped together
- All Client C work grouped together
- Easy to see what's done for each client
- Simple to track and bill
Common Questions
Q: Are projects required?
A: No, they're optional. You can submit requests without projects.
Q: How many projects can I create?
A: Unlimited! Create as many as you need.
Q: Can I move a request to a different project?
A: Yes, you can reassign requests to different projects anytime.
Q: Do I need to provide client information?
A: No! Projects are just labels for YOUR organization. We don't need client details.
Q: Can I delete a project?
A: Yes, but requests under that project will become unassigned (not deleted).
Q: Do projects affect my queue or turnaround time?
A: No, all requests go into your main queue regardless of project.
Q: Can multiple team members access the same project?
A: Yes, if you have team members on your account, they can all see and work with projects.
Need More Help?
Contact your project manager or email support@thrivepix.com