studio.workspaces.create plus workspace_creation configuration.
Configuration
Who receives access?
Automatic joining applies only to the default workspace and authenticated users authorized bystudio.view in the current tenant. It does not make files public or add users to private additional workspaces. Such users share this default library, so give studio.view only to users who should enter it.
The initial membership level follows existing Spatie authorization: users allowed to manage members receive Owner; users with write access receive Member; others receive Viewer. No Spatie role or permission is assigned automatically. All file operations retain their separate permission checks.
Removing a membership is persistent: reopening Studio does not automatically add that user back. An authorized person must explicitly restore their membership. Revoking Spatie permissions also continues to block the corresponding operations.
If your application manages membership itself, disable automatic joining:
enabled to false.
Rename or change the default
An owner withstudio.workspaces.manage can use the workspace’s … menu to rename it or choose Set as default on another workspace in the same tenant. The current default appears first on a fresh opening without an explicit workspace URL. Explicit links keep opening their selected workspace.
Choosing a different default changes which workspace eligible users automatically join. Use this for a shared library, not for a private project that should remain invitation-only.
The current default is protected by a database foreign key against deletion. Choosing another default releases that protection on the previous workspace. Workspace settings supports a confirmed move-or-delete workflow; see workspace retirement.
Existing private workspaces are not automatically converted into a shared default. The automatic default starts as a separate empty library.
API
isDefault. The React transport exposes optional updateWorkspace and makeDefaultWorkspace methods; custom transports can implement them to enable the corresponding sidebar controls.
Create and personalize a workspace
The full-screen creator walks through purpose, name/icon, access and review. Nothing is created until the final confirmation. Team invitations are optional and sent with a separate explicit action after creation (up to ten per wizard). Creating a team does not automatically admit everyone in the host tenant. Personal workspaces have one member and cannot accept workspace invitations or become the shared default. Individual file sharing remains separately authorized. Existing workspaces keep their current memberships and use the team type. Run package migrations to add the nullableemoji and kind columns. Emoji
selection uses native glyphs, localized search, categories, skin tones and a
virtualized list. The independently built workspace-emoji.js is requested only
when the picker opens. Serve that asset alongside studio.js; there are no emoji
image/CDN requests. Clear the icon to restore the folder.
Native discovery advertises workspaceIdentity: true. Custom transports can
opt into the identity screens with this flag once they persist the optional
third argument to createWorkspace(name, signal, identity). Older transports
keep the name-only contract and do not offer unsupported personal/emoji controls.
Workspace responses use workspaceType (personal/team), distinct from library
scope kind. Updating an icon uses the optional fourth argument of
updateWorkspace(id, name, signal, {emoji}).