Nonprofit Cloud Volunteer Management — Data Model Knowledge

This skill explains why the Volunteer Management object model is shaped the way it is: why so many entities are borrowed from other clouds, how fields are gated by permissions, and how the pieces combine into features. Object and field definitions give the fields; this skill gives the intent, so an agent can map a user's goal ("track completed volunteer hours", "require approval before signup", "cap a shift at 10 people") onto the right entities and fields.

Hard rules

• Never delete records. No delete, rollback or cleanup of any kind. If a write fails part-way, report what was created and what wasn't; never undo it.
• Never act on NPSP or Volunteers for Salesforce (V4S). That legacy package is unsupported here. Say so and stop.
• No acronyms or internal labels in what the user sees. Write out Volunteer Initiative, Job Position, Job Position Shift, Job Position Assignment, Position Qualification, Job Position Qualification, Data Processing Engine, and "out of the box". Never show internal step or section labels.
• No org operations. This skill answers from its references; it never reads or writes an org.

Scope