JTBD-DS-04 · Delivery & Service
Restrict partner access to assigned work only
not supported. No implementation and no test. It would have to be built. This is the default status in the catalogue — a row moves out of it only when a test proves it.
What the catalogue records
authorization and tenancy now exist, but no partner access surface does: M13 records a partner engagement and grants no access to restrict, and no verifier ships to authenticate a partner (JTBD-15)
Evidence
This row names no test and no document of its own, and its status does not claim one. Treat it as unbuilt: nothing here proves it, and nothing here says otherwise.
What this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework ships no authentication, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Delivery & Service
- Hand over a won Deal to delivery — validated end to end
- Create a Commessa / Delivery Project from an Order — partially supported
- Involve a third-party delivery partner (engagement, role, scope) — partially supported
- Manage milestones and deliverables — partially supported
- Track hours and costs on delivery — validated end to end
- Calculate delivery margin (forecast vs actual) — partially supported
- Manage a Change Request with impact and approval — validated end to end
- Collect customer acceptance on deliverables — partially supported