Account Teams & Preferred Resources

Business perspective: Account Teams & Preferred Resources

1. Business Summary

Defines preferred resource pools per account/brand, governs default selection plans, and tracks account–resource–assignee combinations with approval status.

2. Business Value

Improves quality and consistency by matching clients with proven resources.

3. Users / Stakeholders

Vendor managers, AMs, PMs.

4. Workflows

  • AccountTeamController scoped to roles (e.g., role 14).
  • AccountsResource and BrandsResource HABTM-style links.
  • AccountAssigneeCombinationStatus tracks triplets (Account/Resource/Assignee) with status.
  • Used by selection cron via Plan + Strategy.

5. Sub-Features

  • Account team assignment.
  • Brand resource pools.
  • Combination statuses.

6. Business Rules

  • Role 14 or admin can manage teams (Observed).
  • Teams influence default plan in selection.

7. Data Entities

AccountsResource, BrandsResource, AccountAssigneeCombinationStatus, AccountReference.

8. Entry Points

  • resources/accountTeam, resources/accountsResources, resources/brandsResources.

9. Inputs & Outputs

  • Inputs: account, resource, status.
  • Outputs: preferred lists used in selection.

10. Integrations

  • Selection engine, RFR, Pricing.

11. Calculations / Logic

  • Filtering at selection time.

12. Status Lifecycle

  • AccountAssigneeCombinationStatus enumerated.

13. Permissions

  • VM, AM, brand-scoped.

14. Reports & KPIs

  • Coverage (accounts with teams), churn of preferred resources.

15. Risks & Observations

  • Stale teams may prevent better/cheaper resources from being selected.

16. Source Code Evidence

  • app/Plugin/resources/Controller/AccountTeamController.php, AccountsResourcesController.php, BrandsResourcesController.php, AccountAssigneeCombinationStatusesController.php.

← Deep dives index