Workspace availability and limits
workspaces.create permission. The owned
workspace limit is enforced transactionally per principal and tenant; membership
in someone else’s workspace does not consume that limit. Set enabled to false
to expose only the tenant’s default workspace, including at the API boundary.
This hides workspace switching and creation in the account menu and pickers.
Existing other workspaces and their files are retained, not deleted.
The account menu replaces the old workspace sidebar section. Owners with
workspaces.manage can rename their workspace and select its default through
Workspace settings. The settings dialog supports resumable transfer or removal of non-default
workspaces. See Workspace removal for queue requirements,
confirmation and external-source boundaries. The legacy DELETE API remains empty-only.
Provide React StudioOptions.onLogout to display a Logout action using your
host application’s sign-out flow.
Language and timezone preferences
Studio settings persist the selected language and timezone preference in the current browser, scoped to the supplied user identity. Automatic timezone is on by default and follows the browser’s IANA timezone. Turning it off reveals a searchable, grouped, virtualized HeroUI timezone selector. Dates are stored in UTC; the preference changes display and date-picker interpretation, not stored data.Settings and workspace permissions
Open Settings from the account menu. The sidebar separates personal preferences from workspace policy, in this order:- General: language and automatic or manually selected timezone.
- Appearance: light or dark theme.
- Keyboard shortcuts: Mac/Windows keycaps, recording, conflicts and reset.
- Notifications: transfer notices, browser push and subscribed event types.
- Uploads: workspace file-type restrictions and resumable-transfer limits.
- Processing: read-only conversion presets and video processing policy.
- Existing sources: incremental imports, when the adapter and access allow them.
studio.settings.view; changing workspace upload settings requires studio.settings.manage and an owner/editor membership. Assign these permissions using Spatie Laravel Permission. Configure alternative names in permissions.abilities, as shown below. Workspace ownership alone does not grant these permissions.
Uploads shows the server-allowed extensions grouped by file category. Selected
extensions narrow the global policy. Deselect every extension to reject new
uploads. Chunked uploads additionally require the server setting to be enabled.
The optional workspace size limit can only reduce the server’s chunked file limit.
Processing displays the configured image presets, format, quality and metadata
policy, plus the available video processing settings. Configure processing
presets in Laravel’s media-studio.php configuration file.
Restore a library view from its URL
Enable URL synchronization for a standalone Studio instance.Workspace member profiles
Studio reads member names, email addresses and avatar URLs from the registered principal model. Configure the attribute paths inconfig/media-studio.php; set a field to null to omit it:
HasAvatar implementation. Configure the default panel when Studio’s API runs outside a panel request. For another identity system, implement MemberProfileResolver and return name, email, and avatarUrl for the supplied authenticated model. Return null for values that should not be shown. Workspace membership is checked before profiles are returned.
Member permissions and Redis
Studio checks all private operations through Spatie Laravel Permission and Laravel’s Gate. Add Spatie’sHasRoles trait to your authenticatable model, run Spatie’s published migration, and install Studio’s permission definitions:
studio. prefix. Empty permission names are rejected. Background processing reloads the actor and checks access again before publishing its result. Configure permissions.actor_resolver when using a custom non-Eloquent identity provider.
Spatie controls its own permission cache. To use a configured Laravel Redis store:
givePermissionTo, revokePermissionTo, syncPermissions, assignRole and syncRoles methods instead of writing directly to its tables. Role and permission definitions are cached; user assignments also have in-memory relationship state. Reload user relationships when retaining the same model across permission changes.
Studio does not persist an additional cache of member authorization decisions. Every member request checks workspace access and the configured Gate permission again. Studio’s media-studio.cache.store setting is separate from Spatie’s permission.cache.store.
For Octane, Spatie provides register_octane_reset_listener when reset-cycle cleanup is needed. Applications switching tenant cache prefixes or stores within one process must reinitialize PermissionRegistrar after switching context, as described in Spatie’s cache documentation. Do not reset the whole permission cache on every Studio request.