Editor Accounts

This page helps you put authentication in the right place before you build around it.

In Dyrected Cloud, authentication is about who can enter the hosted content workspace: owners, teammates, clients, editors, and administrators. Your application still owns customer login, member accounts, checkout sessions, tenant membership, and product-specific identity.

In self-hosted Dyrected, authentication can also be part of your application runtime. That is where collection auth, JWT sessions, password reset, invitations, and auth endpoints belong.

Cloud authentication is workspace access

Think about Dyrected Cloud the way you would think about a managed content workspace. You invite the people who should edit content, publish changes, manage media, and work inside the CMS. Dyrected handles access to that workspace and the hosted content backend behind it.

Use Cloud auth for:

• site owners who manage the content workspace
• clients and editors who update approved content
• team members who need dashboard access
• workspace access to the hosted content API and media library

Keep your application auth in your application. If your product has customers, members, subscriptions, carts, orders, checkout sessions, dashboards, tenants, or account-specific business logic, use the auth system that owns that product surface: your app, your framework, or a dedicated identity provider.

That boundary keeps the Cloud setup simple. Dyrected manages content. Your app manages product identity.

What a Cloud handoff should prove

Before inviting a client or teammate, make sure one real content edit already flows from Dyrected Cloud into the frontend. That is the handoff signal that matters.

The first handoff usually looks like this:

1. Create or connect the Cloud site.
2. Sync the schema so the hosted content backend knows your collections and globals.
3. Confirm the frontend can read published content.
4. Invite the editor or client into the Cloud workspace.
5. Ask them to make one safe edit and confirm it reaches the site.

Use Handing Off to Editors for the full onboarding checklist.

What Cloud auth is not

Dyrected Cloud should not be framed as a hosted customer-auth system for your app.

For example:

• a membership site should keep member login in the app or identity provider
• an ecommerce site should keep customer accounts, carts, orders, and payments outside Dyrected Cloud
• a SaaS product should keep tenant membership and product permissions in the product backend

Dyrected Cloud can still power the content around those products: landing pages, help content, pricing copy, docs, changelogs, media, and editorial workflow.

Where to go next

• Handing Off to Editors — invite people into the right editing path
• Cloud vs Self-hosted — compare runtime boundaries
• Cloud-safe access control — write content rules that run in Cloud