Client Project Access
The Client project access section controls which projects your client (company) users can see in the Projects module. These settings only affect client users; your internal team continues to see all projects. Choose one of two modes:Filtering Projects
When you select Filtered projects, three filters appear. A project is shown when it matches at least one selected type, board, or specific project.1
Select Filtered Projects
In the Client project access section, choose Filtered projects.
2
Choose Your Filters
Select PSA project types, project boards, or search for specific projects. You can combine any of the three filters.
3
Save
Save your settings. Client users immediately see only the projects that match your selections.
Projects explicitly hidden on their own project page remain hidden, even when they match these filters. Hiding a project individually always takes priority.
Section Visibility
Control which major sections appear in the Projects module by toggling these options:Some sections have dependencies. For example, Project Tickets requires PSA Phases to be enabled, and Time Entries requires Project Tickets to be enabled.
Kanban Settings
The ticket-level Kanban feature is currently in development and available only in development environments.
- Show Kanban - Enable/disable the Kanban tab in project details
- Group By - Default grouping for ticket columns (Status, Technician, or Priority)
- Density - Default card density (Comfortable, Compact, or Dense)
Field Visibility
Fine-tune which fields appear on project cards with these toggles:Basic Information
Basic Information
- Project Name - The project title
- Company - The client company name
- Status - Project lifecycle status badge
- Summary - Project description text
- Project Lead - Assigned project manager
Progress Fields
Progress Fields
- Progress % - Completion percentage
- Estimated Hours - Budgeted hours
- Actual Hours - Hours worked
- Hours Variance - Difference between estimated and actual (under/over)
Timeline Fields
Timeline Fields
- Start Date - Project start date
- Due Date - Project deadline
- Timeline Comparison - Visual progress indicator on timeline
- Last Changed - When the project was last updated
Financial Fields
Financial Fields
- Estimated Revenue - Projected revenue
- Actual Revenue - Revenue earned
- Revenue Variance - Difference between estimated and actual
Live Preview
As you toggle field visibility options, the Live Preview card on the right side of the page updates in real-time. This shows you exactly how project cards will appear with your current settings.Status Mapping
MSPortal uses status mappings to organize projects into kanban columns. There are two separate mapping configurations:Project Kanban Columns
This mapping controls how project lifecycle statuses (from your PSA) map to display columns on the main Projects dashboard kanban. Default Column Groups:- Not Started
- In Progress
- On Hold
- Completed
- Cancelled
1
View Current Mappings
The Project Kanban Columns section shows each column and which PSA statuses are assigned to it.
2
Add Statuses to a Column
Click on a column to expand it. Use the dropdown to select PSA statuses that should appear in that column.
3
Set Default Status
For each column, you can set a default status. When you drag a project to that column and only one status is available, this status will be applied automatically.
4
Remove Statuses
Click the X next to any status to remove it from the column mapping.
Ticket Kanban Columns
This mapping controls how ticket statuses (from your PSA service boards) map to columns in the project-level ticket kanban view.This is separate from the project status mapping because tickets use different status values than projects. For example, ticket statuses might include “New,” “Scheduled,” “In Progress,” “Waiting Customer,” while project statuses might be “Planning,” “Active,” “On Hold.”
- Each column can have multiple ticket statuses mapped to it
- Set a default status for auto-selection when dragging
- Unmapped statuses can be added dynamically when moving tickets
Managing Status Mappings
Adding New Statuses
When a new status appears in your PSA that isn’t mapped to any column:- The status will appear in the Unmapped Statuses list
- Drag or select it to add it to the appropriate column
- Save your changes
Auto-Add Unmapped Statuses
When you drag a project or ticket to a column that doesn’t have the required status mapped:- MSPortal detects the unmapped status
- If you have settings permissions, you’ll be prompted to add the status to the column
- Choose Yes to add it automatically, or No to just move the item this once
Resetting to Defaults
Click the Reset to Defaults button to restore all project display settings to their original values. This will:- Set client project access back to All projects and clear any filters
- Re-enable all section and field visibility toggles
- Reset status mappings to default configurations
- Reset kanban settings to defaults
Permissions
Best Practices
Start Simple
Begin with default settings and customize as you learn what information your team needs most.
Match Your Workflow
Map PSA statuses to columns that match how your team actually works and thinks about project stages.
Set Defaults
Configure default statuses for each column to speed up drag-and-drop operations.
Keep It Clean
Hide fields that your team doesn’t use to reduce visual clutter on project cards.
Related Resources
Projects Overview
Learn how to use the Projects module
Integrations
Set up your PSA integration to sync projects