Handing Off to Editors
Onboard editors safely after your site is already working, using the right first-access path for either Dyrected Cloud or self-hosted admin.
Use this page when your site integration, schema, render path, and first preview flow already work, and you are ready to give someone else access.
By the end, you should know what the safest first editor handoff looks like for your runtime.
This page is intentionally shared across frameworks. The onboarding decision is not really about Next.js, Nuxt, Vue, or React. It is about where the admin is running and how new people get into it.
The first handoff rule
Do not onboard anyone until one real content edit already makes it from Dyrected into the frontend.
That is the success signal that matters most. If the builder cannot make one edit and see it appear on the site, an editor should not be the person discovering what is still unfinished.
Cloud handoff
Use the Cloud path when the project is connected to a hosted Dyrected site and the team will log in through the Cloud-managed workspace.
The practical first handoff is:
- Make sure the site, preview flow, and content routes already work.
- Invite the team member through the Cloud Dashboard.
- Have them complete one real content edit.
- Confirm that the edit reaches the frontend as expected.
For Cloud, teach the invitation flow. That is how team members enter the managed content workspace.
Cloud account boundary
Cloud accounts are for the people working inside Dyrected: owners, teammates, clients, editors, and administrators.
Do not use Cloud workspace access as customer login for your app. If the product has members, buyers, subscribers, tenants, or account-specific dashboards, keep that authentication in the product app or identity provider that already owns it.
Cloud handoff checklist
Before a real client handoff:
- make sure the schema has synced successfully
- confirm the frontend reads published Cloud content
- confirm preview works if the project uses preview
- invite one editor first, not the whole team
- ask that editor to make one small safe edit
- verify the edit reaches the site