Shook Console uses a three-tier assignment model to track responsibility for every production plan. Understanding how assignments are inherited is key to managing them efficiently.Documentation Index
Fetch the complete documentation index at: https://docs.shook.digital/llms.txt
Use this file to discover all available pages before exploring further.
The three roles
| Role | Abbreviation | Assigned at | Assignee pool |
|---|---|---|---|
| Customer Success Manager | CSM | Company level | Shook admin users |
| Creative Operations | COps | Project level (default) or Plan level (override) | Shook admin users |
| Customer Point of Contact | POC | Project level (default) or Plan level (override) | The company’s own users |
CSM (Customer Success Manager)
The CSM is responsible for the overall client relationship. One CSM is assigned at the company level and covers the entire company.COps (Creative Operations)
The COps person manages the creative/production operations for individual projects and plans. They are set at the project level, and all plans within that project inherit the same COps by default. Individual plans can override the project-level COps with their own assignment. When a plan has its own COps, it shows the assignee’s name. When it inherits from the project, it shows “Project default” in the dropdown.POC (Customer Point of Contact)
The POC is the main contact on the client side — typically a person from the client’s organisation. Like COps, POC is set at the project level and inherited by plans, with individual plan overrides possible.Because POC represents a client-side contact, the assignee pool for POC is the company’s own users — not Shook staff.
Inheritance model
Changing assignments
Assignments can be changed in several places:| Where | What you can change |
|---|---|
| Company detail page | CSM (company level), COps and POC per project, COps and POC per plan |
| Organization chart modal | All of the above in an interactive visual tree |
| Assignments Monitor | Full tree view — CSM per company, COps/POC per project and per plan |
| Project detail page | COps and POC for the project, plus individual plan overrides |
| Plan detail page | Stat cards show COps and POC (edit from Assignments or Company detail) |
| SLA Monitor | Inline COps and POC dropdowns on each plan row |
| My Assignments | Stage changes only (assignment editing from other pages) |
Bulk assignment operations
When changing COps or POC at the project level, the system asks how to handle plans that already have custom individual assignments:- Keep custom assignments — only update plans that currently have no individual override (i.e., those using “Project default”)
- Override all — apply the project-level assignment to every plan, replacing any individual overrides
Common workflows
Onboarding a new company
- Open the company detail page
- Set the CSM at the company level
- For each project, set the COps and POC
- If individual plans need different assignees, override them in the project’s expanded plan list or in the org chart
Reassigning when a team member leaves
- Go to All Assignments → By User tab
- Select the departing team member and their role (COps or CSM)
- For each company/project/plan in the list, update the assignment to the new person
- Alternatively, use the company detail page and bulk-apply the new COps to all projects and plans