Skip to main content

​
Overview

Partner Milestone Template Admin lets a CE administrator define the milestone templates that structure partner progress workflows. A template is an ordered set of milestones; you control which entries appear, the order they run in, whether the template is active, and — optionally — which partner type it applies to. Templates are managed from the CE partner surfaces at /ce/contacts and are scoped to your organization.

​
Initial setup

Before milestone templates can be configured and used:
  1. Enable the Community Engagement (CE) module for your organization.
  2. Grant CE administrative access to the staff who will manage templates. Access to the partner surfaces at /ce/contacts is gated by ce.contacts.view, and template management requires the CE partner-administration permissions listed under Permissions.
  3. Confirm your partner-type taxonomy (optional). If you want a template to apply only to certain partner types, confirm the partner types you use so templates can be scoped to them. Templates left unscoped apply to all partners.
All template configuration is tenant-scoped — every template is stored against your organization_id and is never visible to other organizations.

​
Configuration options

  • Milestone template CRUD in the CE partner surfaces.
  • Template ordering (display_order) and activation / deprecation (is_active) controls.
  • Optional partner-type scoping on templates.

​
Permissions

Access to the partner surfaces at /ce/contacts is gated by ce.contacts.view. Milestone-template administration is part of the CE partner-administration surfaces, so staff who manage templates need ce.contacts.view plus the partner-management keys below: Grant these via the role editor (Settings → Roles). Per constitution §5.2.3, partner-type scoping and template content are tenant-configurable — there are no platform-wide hardcoded templates.

​
Auditing & monitoring

  • Every template mutation includes organization_id and is rejected for cross-organization access; row-level security enforces org isolation for each create, edit, reorder, activate, and deprecate operation.
  • Deprecating a template removes it from new partner-workflow selection paths, while historical partner records that already reference it remain readable.

​
Troubleshooting

  • Configuration changes don’t take effect. Some settings require a session refresh; users should sign out and back in.
  • A deprecated template still shows on existing partners. That is expected — deprecation only hides a template from new selections; partners already using it keep their history.
  • User guide
  • Source spec: specs/ce/specs/CE-06-EN-01-partner-milestone-template-admin.md