06 — Developer Workspaces
Developer onboarding, workspace ownership, members and permissions.

Becoming a Developer
Becoming a Developer
Nord Forge uses a customer-first account model.
A normal account does not automatically receive a developer workspace.
When the user activates the developer flow, Nord Forge creates:
A developer workspace
The user as workspace Owner
A store associated with that workspace
If the user already owns or belongs to a non-customer workspace, the existing developer workspace can be reused.

Workspace Roles
Workspace Roles
The current team management flow exposes the following main roles.
Owner
The workspace owner has full workspace control.
Owner permissions include all workspace capabilities and owner-only actions.
Developer
Intended for product and release development.
Main permissions include:
Workspace view
Product management
Download/release management
Documentation management
License viewing
Analytics viewing
Support
Intended for customer support.
Main permissions include:
Workspace view
Support management
License viewing
Customer viewing
Viewer
Read-focused workspace access.
Main permissions include:
Workspace view
Documentation view
Analytics view
Owner-only team management
The workspace owner controls invitations, member role changes, member removal and workspace ownership transfer.

Workspace Lifecycle
Workspace Lifecycle
Workspaces can be active or archived.
Archive
Archiving keeps the workspace and its data but removes it from normal active operation.
Restore
An archived workspace can be restored by its owner.
Delete protection
A workspace cannot be deleted normally while it still has customer/license relationships that require it to be preserved.
In that case, archive the workspace and resolve active customer access first.
Ownership transfer
Workspace ownership can be transferred to another authorized member through the workspace ownership flow.