Skene
Product docs

Product documentation

Learn how to use Skene: workspaces, sources, milestones, widgets, and analytics.

~6 min read

Workspaces & sites

Skene is built as a multi-tenant workspace system. Each workspace has its own members, sites, sources, widgets, and analytics. Here's how it all fits together.

Core concepts

Workspace

The highest-level container. Groups sites, sources, widgets, analytics, and team members.

Members

Owners manage settings and keys. Members work with sources, milestones, and widgets.

Sites

Represent where you embed widgets: web apps, marketing sites, or other surfaces.

Workspaces: your main container

When you sign up, Skene automatically creates a personal workspace and makes you its owner. You can later create more workspaces—one per product, environment, or client account—depending on how separated you want data and settings to be.

Multi-product setup: Use separate workspaces when you need hard separation (different companies, billing). Use multiple sites in one workspace when you share a team but have multiple environments.

Owners and members

Owners

  • Change workspace settings
  • Invite and remove members
  • Manage API keys
  • Delete the workspace

Members

  • Work with sources and milestones
  • Build and publish widgets
  • View analytics

Inviting team members

  1. Go to workspace settings → team or members section
  2. Click Invite member
  3. Enter email address and choose role (owner or member)
  4. Send invitation or copy the link to share directly

When accepted, they'll join the workspace and see it in their workspace switcher. You can revoke invitations or remove members later.

Sites: mapping to your products

Inside each workspace, sites represent where you embed widgets and track onboarding. A site typically corresponds to one customer-facing URL like app.yourproduct.com.

Web app

Main product surface

Marketing site

Pricing or signup page

Sandbox

Test before rollout

When to use what?

Multiple workspaces

  • • Different companies or clients
  • • Strict access control needed
  • • Completely different billing

Multiple sites (same workspace)

  • • Same team, shared strategy
  • • Multiple environments (staging/prod)
  • • Multiple surfaces of same product

Example: A startup with staging and production uses one workspace with two sites. An agency managing five clients uses one workspace per client.

What's next?

Once your workspace and sites are set up, connect repositories so Skene can analyze your product and suggest milestones.