Custom Field Groups are a new way to manage your Custom Fields more efficiently in Hub Planner. Instead of assigning fields one by one—or showing the same list to every project or resource—you can now bundle related fields into groups and apply them where they’re needed.
Group fields by your business logic—such as department, project type, role, or region. These groups can then be applied to resources and projects, simplifying how you work with Custom Fields at scale while also improving filtering, sorting, and reporting capabilities.
What are Custom Fields?
Custom Fields let you tailor Hub Planner to reflect how your business actually works. You can track skills, certifications, locations, availability, or any other detail that matters to your planning, reporting, and decision-making.
Some common examples include:
Some common examples include:
-
Find the right resource: Quickly identify the team member with the right skills
-
Filter by location: Narrow down resources based on region to find the right team member for a project.
-
Project Fields: Adding your own custom fields related to projects to be able to quickly sort them or enhance reporting.
Custom Fields are incredibly flexible—but as your setup grows, they can become harder to manage. That’s where Custom Field Groups step in.
Why use Custom Field Groups?
Custom Field Groups offer a straightforward and efficient way to organize your custom fields in a way that makes sense for your business logic. By grouping related custom fields together, you can enhance data entry and retrieval processes, making them more intuitive and efficient.
-
Group related fields for structured data management
-
Assign groups to multiple projects or resources
-
Set visibility and permissions based on user roles
-
Improve filtering, sorting, and reporting workflows
-
Fully compatible with the Hub Planner API
Use Cases:
How you’ll use Custom Field Groups will depend on your team setup and workflow. But to give you a head start, here are a few ways we see teams planning to use them.
Adding New Resources in the Workspace
Use case: Adding a newly hired resource
Why: Apply a pre-defined group like “Developer related Team Fields” with role, skill level, certifications etc. —all at once for faster setup and consistency.
Core Fields for All Resources
Use case: Fields you want for all resources in your account
Why: Bundling these and making them into a default group, assigned at scale, ensures every resource has the core fields needed for workflows and reporting.
Role-Specific Field Sets
Use case: Designers vs Developers
Why: Keep things relevant by applying tailored groups like “Design Team Fields” or “Engineering Team Fields,”.
Managing External vs Internal Resources
Use case: Separating external vs internal resources
Why: To simplify resource allocation, group Custom Fields related to internal resources together, and do the same for external resources. This helps you plan and report more effectively across different resource types.
