Skip to content

Workspace settings

The Settings pages allow you to configure your workspace. You can navigate to workspace settings in the left navigation on your home page. If you belong to multiple workspaces, you can switch between them by clicking on the top left workspace avatar.

A screenshot of the left navigation with the Settings item highlighted
Click Settings to view the workspace Settings pages.

Starter and Pro workspaces

A screenshot of the settings navigation menu, listing options for General, Membership, Secrets, Databases, API Keys, and Billing
Settings for Starter and Pro workspaces.

For workspace settings in general, note that only workspace owners will see all workspace settings, since some features, such as changing workspace roles, are only available to owners.


Workspace owners can configure the workspace's account, profile, and preferences.


  • Set or change the workspace's username (which appears in the URLs of the workspace's profile and notebooks).
  • Change the workspace tier (for example, from a Starter workspace to a Pro workspace).
  • Set or change the email address to receive notifications and messaging about the workspace account.


  • Customize the workspace's avatar and banner.
  • Set the workspace's display name.
  • Write a brief workspace biography.
  • Specify workspace web sites.
  • Specify a publicly-visible email address for the workspace.


  • Choose whether or not to use Prettier to format code in all workspace notebooks.
  • Enable or disable newly-created notebooks from being private (not shared with the workspace).


Allows you to invite people to become new workspace members, change their roles, or remove them from the workspace. Current and invited workspace members appear in a list, along with their roles. If an invited workspace member has not yet accepted, their name appears with a Pending label. See the Membership page for more details.


Shared secrets for use in your workspace's private notebooks. Use secrets to store API keys and other sensitive values you don’t want to hard-code in notebooks.


Shared database connections for your workspace's private notebooks.

API Keys

Use API keys to securely load and embed private notebooks outside of Observable.


This is only visible to workspaces owners. Owners can change the subscription by altering either the tier or the billing period, and also change the payment method. The timing of your current billing cycle, and the next billing cycle are shown, as well as invoices. See the Billing section for more details.

Enterprise workspaces

The settings for Enterprise workspaces are identical to the settings for Starter and Pro workspaces, with the exception of Groups and Permissions.

Screenshot of the Permissions tab in the Settings, showing checkboxes to enable or disable team editors managing public content and file attachments.
Enterprise team options.

Protecting team assets

EnterpriseLearn more about Enterprise

In order to protect team assets, public notebooks (listed or unlisted) do not have access to secrets and database connections.

In addition, as a team owner, you can configure whether you want to limit who in the team can make content public, by checking a box in the permissions tab of your team settings, as shown earlier. For more information about this feature, please refer to this notebook.

You can also select whether you want to allow File Attachments in your team’s workspace.

Authentication and identity management

EnterpriseLearn more about Enterprise

As an Enterprise Team owner, you can require all team members to be authenticated against your domain(s). This protects your team assets from access by team members after they leave the organization.

This allows Enterprise customers to require that team members authenticate against a specific domain (or a group of domains) to gain access to the Team’s content on Observable. For team members who authenticate to Observable using other providers (personal Gmail accounts, GitHub, Twitter), they will be required to authenticate to both their personal authentication provider as well as your organization before gaining access to your team on Observable.

In addition, we also regularly check for a valid domain authentication and will request re-authentication if that check fails (for example, if someone is removed from your organization).

Single sign-on

EnterpriseLearn more about Enterprise

Enterprise customers may avail of federated log-in using Gsuite and custom SSO providers.

"Single Sign-On" or SSO is the term used to describe the process where a user's identity is authenticated by an identity provider service for use with multiple applications. With SSO, users can have a single user name and password that works across all of the applications they use. Observable supports SSO using external identity provider services with built-in support for Google, GitHub, and Microsoft identity providers.

A feature available to Observable Enterprise teams allows them to associate their logins with their own additional identity provider service, like Okta Identity Cloud or OneLogin, using the standard OpenID Connect (OIDC) protocol. See the docs for more information about support for Enterprise SSO.