Partner administrator
Distinguish the demo portfolio, method versions, assignments and licences.
Fictional demo and workflow in preparationChoose the guidance that fits your work. Your selection helps you navigate; access to protected content still depends on your assigned permissions.
User guides and presentations
- Partner administrator user guide
Loading files…
- Workplace Codex for partner administrator
Loading files…
Relevant pages
Frequently asked questions
Does viewing a role screen give me that role?
No. Reading a public role page or guide grants no project role or extra permissions. Role manuals and presentations are available without login, except the Dutch consultant PDF, which is not yet available. Client projects require an invitation. Workshop files also require login and download permission; an administrator grants that permission at /manage/users. A job title, selected role screen or Codex account does not replace those access requirements.
What can a partner administrator do with Portfolio?Partly demo or in preparation
Portfolio shows fictional projects, decisions and issues needing attention. Editing partner playbooks, assigning consultants and managing licences are not yet available. Download the partner guide and role presentation without logging in from the partner role page in Support, in Dutch or English. The material is dated 4 October 2026. Use it to prepare ownership, permitted uses, languages and version choices. The playbook cards illustrate the intended model. Example partners and figures are not client references or evidence of a commercial agreement.
How should access for a partner or consultant be arranged?Workflow in preparation
Management of partner assignments and consultant allocations is not yet available. Prepare a bounded assignment granted by an authorised client role, within which the partner assigns consultants. Keep individual project roles and content licences separate. Working for a partner gives no general right to client data or personal cases. Have the administrator record the organisation, project, task and duration. Before operational use, test that an unrelated user and someone whose assignment has ended cannot access information beyond their authority.
What should happen when an adviser leaves the project?Workflow in preparation
Agree how the assignment ends, access is withdrawn and authorised client outputs remain usable. An operational departure and export workflow is not yet available. Keep client decisions and project history separate from partner playbooks and paid learning content. Retaining project results does not automatically grant access to the full partner library; ending an assignment should not erase the agreed client record. Have the administrator confirm your contract's retention, reading and export arrangements before relying on automatic handling.