Skip to main content

How configuration is split

  • Workspace configuration controls security, identity, compliance, and workspace-wide behavior.
  • Project configuration controls access and operations for one project.

Workspace settings

Open workspace Settings when a change should apply to the whole workspace. Workspace members can open most settings pages. Only workspace admins can change workspace-level controls. Some items appear only when the plan or your role includes them.
Workspaces are available on Speckle Cloud and on Speckle Enterprise Server. For self-hosted setup, see Enterprise license.
Workspace settings sidebar with General selected and the Members & access, Projects, Plan & billing, AI and Automate sections
1

Open the workspace

Sign in and open the workspace. You should see Settings at the bottom of the left sidebar.
2

Open Settings

Select Settings. The sidebar expands into General followed by collapsible sections. The section that holds the current page opens.

Settings map

Items appear in this order. A section shows only when at least one of its items is available to you. A hidden item is gated by plan or permission, not missing from the product.
  • General: name, short ID, description, logo, and the AI features switch. On the Enterprise and Unlimited plans, the AI card also holds two more switches: Only workspace admins can enable AI and Disable public sharing of AI conversations. Everyone who can open Settings sees this page. Only workspace admins can save changes, turn AI features off, or change the two switches. See Turn AI features off for the workspace and Enterprise controls for AI.
  • Members & access
    • Roles: an overview of workspace roles. It appears only where it is enabled for the workspace. See Roles and permissions.
    • Security: discoverability, domain protection, SSO, and SCIM. See Workspace discoverability, Domain protection, SSO, and SCIM.
    • Tokens: workspace share tokens for read-only access to models or dashboards. Revoke one token, or use Revoke all.
    • Support: support sessions. It appears when Admin Support Mode is enabled. See Admin Support Mode.
  • Projects
  • Plan & billing
    • Usage: activity, plan limits, and AI spend. Workspace admins see it when the plan includes usage analytics. See Usage statistics.
    • Billing and plans: plan, payment, and Customer Portal. See Billing.
    • Data residency: where workspace data is stored. See Data residency.
  • AI
    • Rules: standing instructions Speckle Intelligence follows in every conversation. Members can open it; only workspace admins can change rules. See AI Rules.
    • Skills: reusable playbooks for Speckle Intelligence Chat. See Intelligence skills.
    • Conversations: the workspace-wide list of Chat conversations. Workspace admins only.
  • Automate
    • Functions: the Automate functions available to projects in this workspace, including Regenerate token…. See Speckle Automate.
On self-hosted servers, Admin Support Mode is available only on Speckle Enterprise Server. See Enterprise license — Admin Support Mode.
On self-hosted servers, Speckle Automate is available only on Speckle Enterprise Server. See Enterprise license — Automate.
Use workspace settings when policies should be consistent across all projects in the workspace. For invites and team membership, open Team in the workspace sidebar. See Invites and team membership.

Project configuration

Open a project, then Settings in the project sidebar, when your change should affect one project only. Project settings has General, Webhooks, Tokens, and Automations (when Automate is available). Workspace settings do not replace project settings.

Manage project collaborators

Projects can be shared with workspace members and, depending on workspace rules, with guest collaborators. Project visibility and membership together determine who can view and edit project content. Open Collaborators in the project sidebar to view and manage project access.

Access levels

A project can have one visibility state:
  • Workspace: Accessible to workspace members.
  • Private: Accessible only to project collaborators and admins.
  • Public: Accessible to anyone with the link in the web interface and API.

Change project visibility

Project settings Access card with Public, Workspace (selected) and Private options
To update visibility in the web interface:
1

Open project settings

Open the project, then open project settings.
2

Select visibility

Locate the visibility control and choose the target level.
3

Save

Save changes to apply new visibility.
Public projects expose project data to anyone with the link. Validate project content before switching to Public visibility.

Share tokens

Project share tokens list with Type, Label, Expires, Created and Last used columns
In Project settings -> Tokens, you can create share tokens that give read-only access. Share tokens are commonly used for:
  • Intelligence dashboards.
  • Power BI syncing.
Share tokens can be revoked from the tokens list when access is no longer needed.

Automations

In Project settings -> Automations, you can review and manage automations configured for that project. This can include:
  • Active sync automations connected to cloud integrations.
  • Automations running your custom code.
  • Enabled Speckle pre-made automations.
Use this page to check current automation status and manage what runs against project models. For setup and implementation guidance, use the developer docs: Speckle Automate and Create Automation.

FAQ

Those items are gated. Usage is for workspace admins on a plan that includes usage analytics. Skills appears when the workspace includes Speckle Intelligence Chat. Functions appears when Automate is available. The rest of Settings still opens.
Workspace admins can change workspace-level settings. Members can view most settings pages but cannot apply workspace-level changes.
Project Owners and Workspace Admins can change project visibility, collaborators, tokens, and automations in project settings.
Use workspace settings when policies should apply across all projects in a workspace. Use project settings when the change should apply to only one project.
No. Labels are for organization and filtering. Permissions are controlled by workspace role, project role, and project visibility.
No. Project labels are managed in Settings -> Project labels. Issue labels are managed in Settings -> Issue labels.
Yes, if they are explicitly added as collaborators. Private visibility blocks users who are not project collaborators.
Share tokens provide scoped read-only access for specific sharing workflows. They do not change workspace or project roles. Revoke tokens when they are no longer needed.
Not by itself. SSO handles authentication. Use SCIM provisioning for automated provisioning and deprovisioning.
Data residency is available in Speckle Cloud on Enterprise plans. If you need strict sovereignty and infrastructure control in your own jurisdiction, use an Enterprise self-hosted deployment.
Yes, on Enterprise plans. Governance controls can enforce exclusivity based on verified email domains. Confirm your operating model first if your organization intentionally uses separate regional workspaces.
Last modified on October 23, 2026