Use case · Compose a project workspace

Product launch and operations: combine development, data and websites

For a SaaS feature launch, bring requirements, launch pages and post-release metrics into one workspace. The team switches between entry points while keeping discussions, files and deliverables in their respective work items.

Set up the project workspace

Create a “Self-service analytics launch” workspace and invite product, engineering and operations members. An authorized member installs the development, data assets and website suites, connects repositories and data sources as needed, and gathers product copy, screenshots and brand assets.

One workspace, three entry points

In Configure views, enable Development, Data assets and the Site console, then arrange them for the team’s routine. Use Work items for individual matters and keep Activity if useful; Files and Scheduled tasks remain visible. The cards below link to each responsibility.

Development → Delivery tracking

Open Development from workspace navigation to review development records and follow repositories and PRs in this workspace. Create a “Deliver self-service analytics” development work item with requirements, authorized repositories and acceptance criteria. Its development view focuses on that item’s records and discussions.

Data assets → Release outcomes

Find authorized traffic, signup and feature-usage data in Data assets and create a “Two-week launch review” analysis work item. Agree metric definitions, dates and sources before asking the Agent to examine traffic-to-signup and signup-to-usage changes. Keep charts, reports and questions to verify. Missing tracking or data must be supplied; enabling a view does not connect data automatically.

Site console → Launch page

Create a website work item, “Self-service analytics landing page,” with benefits, screenshots, target audience and call-to-action copy. Ask the Agent for a preview, then inspect content and versions in the Site console. The owner confirms facts, links and release timing before publishing.

Turn a launch into ongoing collaboration

Before release, check development acceptance and page content. After release, review metrics in the analysis work item and turn findings into new development or website work items. For recurring checks, define scope and timing before creating a scheduled task. Combining views provides shared entry points; it does not automatically chain code changes, analysis conclusions and site publication.

Shared navigation, existing permissions

Workspace visibility and order are shared with members who can access it; only authorized members can change them. Members can open hidden views from Configure views. Opening a view does not grant external-system or business-data access. Each work item has independent view settings, and sorting does not change its default view.

Related guides

Follow the workspace view settings guide

Install suites and configure connectors