The BlueCollar Project record is deployed with some default setup but is designed to be flexible and fulfill various customer needs.
As an administrator, new fields can be added as needed by navigating to Customization -> Lists, Records, & Fields -> Record Types and then selecting the Blue Collar Project record type. On the Fields tab select 'New Field' and add a field as you normally would.
Users can create saved searches and make them available as a sublist and then populate them in a subtab on the Project record.
This is useful since various businesses might want to create unique criteria or bring in custom fields specific to their account within project searches. The default deployment already includes saved-search sublists for Contracts, Purchase Orders, Invoices, and Time entries on the "Related Records" tab.
By default, BlueCollar Projects are not restricted to a single subsidiary, meaning that all users can see all projects regardless of their subsidiary role security. It also means that BlueCollar Projects are able to exist in multiple subsidiaries at once which is a common use case for certain industries like solar or transmission line installation.
Administrators are able to enable Subsidiary filtering by
Users will now be able to filter by the Subsidiary or Subsidiaries that the Project should be available in.
BlueCollar uses a dual-layer permission model: native NetSuite role permissions plus BlueCollar Global Permissions. BlueCollar does not ship out-of-the-box roles, so SuiteSuccess (or custom) roles must be granted access to the BlueCollar custom segments and records.
On the Role record, grant at least:
| Area | Permission | Level |
|---|---|---|
| Lists | Custom Record Entries | View or greater |
| Setup | Custom Record Types | View or greater |
| Setup | Custom Segments | View or greater |
| Custom Record | Each BlueCollar record the role needs | As needed |
On the Custom Segments (BlueCollar Project and Cost Code), grant each role: Value Management Record Access (View+), Record Access (Edit), and Search/Reporting Access (Edit).
Then configure feature access under BlueCollar Global Permissions. Two things to remember: administrators must be granted BlueCollar permissions explicitly (they don't inherit them), and a permission set to FULL does not automatically grant VIEW — if a feature calls for VIEW, set it to VIEW.
Projects are inactivated (and reactivated) through a formal request process rather than a simple checkbox, so the action is tracked and can report a failure reason if something blocks it. Inactivating a project requires the CORE / INACTIVATE_PROJECT / FULL permission; reactivating requires CORE / ACTIVATE_PROJECT / FULL.