Selecting the Right Mechanism for a Client Workspace (CCAO-F)

Putting the four slots to work at once

The earlier knowledge points each isolated one mechanism. This one is the analysis skill the CCAO-F exam builds toward: taking a realistic, mixed configuration need and routing every part of it into the correct slot at the same time. The canonical setting is a consultant running one Project per client, because it exercises all four mechanisms together and forces the two hardest calls, account-level versus Project-level and knowledge versus Memory.

Getting this right is what turns individual configuration knowledge into a working operating pattern. Getting it wrong is subtle, because each wrong placement still runs at first; the cost is a Project that is harder to maintain and, in the multi-client case, one that risks leaking context between clients.

Behavior and facts: instructions and knowledge

Start with the two most familiar slots. The firm wants every client deliverable written in a formal register, wants Claude to cite the source document for factual claims, and wants it to flag anything uncertain rather than guess. All three are rules about conduct, so they are standing instructions in that client's Project.

The client's brand guide, the current statement of work, and the last few status reports are facts Claude should draw on. They are knowledge base documents. Notice the pairing rule at work: the cite-sources instruction is only usable because those documents actually sit in this Project's knowledge base for it to cite.

The two calls that separate levels

Now the harder calls.

The firm-wide status-report formatter is a repeatable, multi-step procedure that should produce the same structure for every client. Because it is shared and structured, it is a Skill, and because Skills live at the account level, it is built once under Customize and reused across every client Project. Putting the formatter into one client's instructions would trap a reusable procedure inside a single Project and force it to be re-created for the next client, which is the account-level reusability point.

The client's stakeholder names and standing preferences are evolving, client-specific continuity, so they are that Project's scoped Memory. And because Memory is isolated per Project, one client's stakeholder details never appear in another client's Project. That isolation is what makes one-Project-per-client safe.

On the Team and Enterprise plans there is one more lever worth knowing: a configured Project can be shared with the whole engagement team under permissions, so everyone works from the same instructions, knowledge, and Skills rather than each person rebuilding context. Project-scoped Memory is exactly what keeps that shared setup safe, since it guarantees one client's continuity cannot cross into another client's Project even when several people are using the same configured baseline.

What the CCAO-F exam trips candidates on

The exam sets two traps, both at the level boundaries. The first is placing a firm-wide reusable procedure inside a single client Project's instructions instead of building it once as an account-level Skill. The tell is a procedure that should be identical for every client written into one client's setup; the credited answer lifts it to an account-level Skill.

The second is storing one client's stakeholder preferences in a shared or wrong Project, breaking the isolation scoped Memory is meant to provide. The tell is client-specific continuity placed somewhere it could surface for another client; the credited answer puts it in that client's own scoped Memory. Both traps punish ignoring the level: a reusable procedure belongs account-level, and client continuity belongs Project-scoped.

Common misreadings to avoid

How this shows up on the exam

Domain 5 analysis questions hand you a mixed brief and ask you to place each element. Sort by kind and by level: behavior to instructions, facts to knowledge, firm-wide procedures to account-level Skills, and client continuity to scoped Memory. Watch specifically for the level traps.

This capstone draws on Skills as account-level reusable procedures, scoped Memory and Project isolation, and the pairing rule. It leads naturally into client isolation through Project and Memory scoping, which pushes the isolation question further.