Skip to main content
A workspace is the central container for everything your team does in Moonshadow. It holds your integrations, members, API keys, and automation rules. Most teams use one workspace per organization, but you can create additional workspaces to separate environments or teams.

What Is a Workspace?

When you sign up for Moonshadow, you are prompted to create your first workspace. Every API request, integration, and event is scoped to a workspace, so choosing the right structure early keeps your data organized and your API keys isolated. Each workspace has:
  • A unique identifier used in API paths
  • Its own set of integrations with external tools
  • Members with roles that control access
  • API keys for programmatic access
  • Automation rules triggered by events

Creating a Workspace

Via the Dashboard

  1. Log in to Moonshadow and open the workspace selector in the top navigation.
  2. Click Create Workspace.
  3. Enter a name and optionally invite members.
  4. Confirm to create the workspace and land on its settings page.

Via the API

You can also create a workspace programmatically. Pass your Bearer token in the Authorization header.
Example response:

Listing Your Workspaces

Retrieve all workspaces you have access to with a GET request.
Example response:

Workspace Settings

Open a workspace’s settings page from the dashboard to manage:
  • Name and description: Keep the workspace identifiable for your team.
  • API keys: Generate and revoke keys for programmatic access.
  • Members: Invite teammates and assign roles.
  • Billing: View usage and manage the subscription plan.

Multiple Workspaces

You can belong to many workspaces and switch between them from the top navigation. This is useful when you want to separate production and staging environments, or when different teams need isolated integrations and members.
API keys are scoped to a single workspace. Requests made with one workspace’s key cannot access resources in another workspace.

Members and Roles

Every workspace has members, and each member has a role that determines what they can do. Roles range from full administrative access to read-only viewing. For a detailed breakdown of each permission, see Permissions and Roles.