Skip to main content
All CollectionsCollaborationWorkspace
Understanding Workspace Owners and Members
Understanding Workspace Owners and Members

This article covers workspace roles and configurable user restrictions in Studio.Design's paid plans.

Saika avatar
Written by Saika
Updated today

Workspace Roles and Permissions

With Studio.Design's "Workspace" feature, you can manage multiple projects (sites) together, centralizing member invitations, permission management, and plan payments.

When using the workspace feature, you'll assign users either an "Owner" or "Member" role. Each role has different operational capabilities, allowing you to set appropriate roles based on responsibilities.

In paid workspace plans, you can restrict the operational scope for workspace members and guests on an individual basis.

This article explains the operational scope for owners and members, and the permission restrictions available in paid workspace plans.

For specific instructions on inviting members, changing roles, and editing permissions, please refer to Inviting and Managing Workspace Members.

Operational Scope by Workspace Role

Both workspace owners and members can access all projects linked to the workspace.

Owners can manage the workspace, while members have some restrictions on workspace configuration operations. See the list below for details.

Operational scope by role:

Access to Workspace

Access to All Projects within Workspace

Access to Workspace Settings

Add Projects to Workspace

Invite Members to Workspace

Invite Guests

Change Roles of Workspace Members

Change Roles of Guests

Change Permissions of Members/Guests

Remove Members/Guests

Owner


(Only in Paid Plans)

Member

×

×

×

×

×

×

×

×

Workspace Member Permission Restrictions

In paid workspace plans, owners can restrict permissions for members and guests to limit their operations.

For example, if "Restrict Form Response Viewing" is enabled, only form response viewing is restricted while editor, CMS, and publishing operations remain unrestricted.

These permissions are set per user. This means permissions cannot be changed for individual projects, and users will have the same permissions across all projects managed within the workspace.

Tips: For guests, permissions can be restricted on a per-project basis.

Permission Restriction Details

You can grant or restrict permissions for the following four operations:

  • Restrict publishing settings

  • Restrict editor editing

  • Restrict CMS operations

  • Restrict form response viewing

1. Restrict Publishing Settings

This prevents operations related to the published site.

Restricted Operations

Allowed Operations

  • Publishing, updating site, and setting custom domains

  • Generating and deleting live preview URLs

  • Setting publication scope for individual pages

2. Restrict Editor Editing

This limits editing work in the editor to Content Editing Mode operations.

3. Restrict CMS Operations

This restricts certain operations in the CMS Dashboard.

Restricted Operations

Allowed Operations

  • Adding/removing models- Editing model names/icons

  • Creating new collections

  • Editing collection names

  • Creating/deleting properties

  • Editing property names

  • Creating/editing/changing status of items

  • Editing/reordering existing properties

  • Adding items/changing status in existing collections

4. Restrict Form Response Viewing

This prevents viewing form response results from the published site.

Restricted Operations

Allowed Operations

  • Viewing form response results from the published site

  • Placing and editing forms in the editor

  • Configuring form settings (global and individual)

  • Testing form functionality using live preview

  • Viewing responses submitted through live preview

  • Downloading CSV data for responses submitted through live preview only

Did this answer your question?