Client administrator
Prepare setup and access responsibilities; recognise current limitations.
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
- Client administrator user guide
Loading files…
- Workplace Codex for client administrator
Loading files…
Relevant pages
Frequently asked questions
How do I check which project the demo shows?Fictional demo
Check the project name and demo label before reading an action or deadline. Where the project selector is available, change the selection and check that the context changes. Examples include relocation and hybrid working, with different practical information. Selecting a demo project is not an invitation to a real client project, and an example deadline does not apply to you. Access to a client project requires an invitation; logging in or choosing an example is not enough.
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 should a client administrator prepare before activation?Workflow in preparation
Prepare the purpose, intended outcomes, locations, groups, languages and responsible people. Identify the sponsor, editor and question owner, and distinguish fixed decisions from open ones. Record the partner, playbook, version and permitted uses. The operational client-project setup process is not yet available; project selection in Deploy is fictional and does not invite employees. Before activation, arrange tested configuration and permissions, clear content ownership and an agreed route for corrections or access problems.
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.
Why can I see a file but not download it?Partly demo or in preparation
Workshop files W01 through W16 require sign-in and download permission; an administrator grants that permission at /manage/users. Role manuals and presentations can be downloaded without signing in. The Dutch consultant manual is not yet available. Documents in Deploy are fictional examples. Check which type of file you are viewing. If an expected download fails, report the page, title, language and error message through your Workplaced contact. Do not use someone else’s account.
Does a Codex account automatically give access to a client project?
No. A Codex account does not automatically provide access to a client project; an invitation is required. One login covers the Codex and /experience, using email and password or Google at /login. Role manuals and presentations can be downloaded without signing in, except the Dutch consultant manual, which is not yet available. Workshop files require sign-in and separate download permission. A working login therefore does not mean you can open every project or file.
What should I do if login or access does not work?Partly demo or in preparation
Use /login with email and password or Google. If sign-in works but a project does not open, check whether you have an invitation. Workshop downloads require separate permission, granted by an administrator at /manage/users. Record the page, time and error message and ask for help through your Workplaced contact. A support form, support email address and ticket system are not yet available. Do not share a password, recovery code or session link.
May I put confidential information into the public demo?Fictional demo
No. Use only fictional information when trying /experience. News, documents, pulse, worksheets, actions, events and phases are examples there; nothing is actually saved or approved. Do not enter employee cases, personal learning evidence or confidential project documents. For real work, use the procedure agreed by your organisation. If you are unsure about appropriate use, speak to your Workplaced contact before sharing confidential information.
Is feedback or a pulse response automatically anonymous?Partly demo or in preparation
No, do not assume anonymity. The pulse in Deploy is a fictional example; no real responses are saved or approved. The "Was this helpful?" button and feedback storage are not yet available. There is therefore no working feedback process from which you can infer anonymity. Before taking part in a real questionnaire, check its privacy information and who may view the answers. Discuss any uncertainty through your Workplaced contact.
Does technical support automatically see private project content?
No. Technical support does not automatically have access to private project content. Access is only possible through a temporary, recorded authorisation. Arrange the help you need through your Workplaced contact before sharing project content. Share only necessary information, without passwords, tokens or unrelated personal data.