Documentation Service Catalog Catalog Resource Form
Detailed guide

Catalog Resource Form

The resource form for defining reusable delivery roles or resource types.

Use this form to create a clean record the first time or safely update an existing one without guessing which field drives downstream behavior.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Add reusable resources before estimate builders create duplicates through quick-add flows.

Put it into practice

  1. Start with duplicate prevention: search existing resources first and confirm naming conventions.

    InteractionsService Catalog > Resources: search list before opening create form.

  2. Create or edit the resource identity using role names estimate builders recognize quickly.

    InteractionsResources tab: click New Resource or row edit action.

  3. Set classification and cost-related fields carefully because these values influence delivery cost assumptions and margin outcomes.

    InteractionsCatalog Resource Form: complete classification and cost fields.

  4. Save and verify the resource is visible and categorized correctly in the resources list.

    InteractionsAfter save, return to Resources list and validate the new/updated row.

  5. If needed for active planning, confirm the resource is available in estimate resource assignment flows.

    InteractionsProject Estimate lines: open resource assignment modal and confirm resource is selectable.
    Open workflow: Estimate Workflow

What to review

Page header and breadcrumb

Confirms whether you are creating or editing, gives you the back path, and is the quickest way to avoid updating the wrong record.

Primary form sections

The form is grouped so you can complete one block at a time instead of hunting for every field in a single long screen.

Required inputs and field labels

Every required label tells you what must exist before the record can be saved; blank or invalid values should be corrected before moving on.

Validation and inline errors

Use these messages as instructions, not warnings to dismiss. They tell you exactly which field blocks save and why.

Primary save action

Commits the record only after the form validates. Use it after reviewing every section because it is the action that changes workspace data.

Cancel or return action

Leaves the form and takes you back without finishing the workflow. Use it when you opened the wrong record or need to check related data first.

Resource identity

Use names that estimate builders will recognize immediately.

Cost or classification fields

These values affect pricing and staffing logic downstream.

Usage notes

Any notes should make the resource easier to choose correctly later.

Guardrails

  • Classification and required pricing inputs should validate before save.
  • Only catalog maintainers should change reusable resource definitions.

If it starts drifting

  • If a new resource does not appear where expected, verify you saved the right resource type and not a rate.