Get to your first evidence-backed decision

You need:

• a Zentrik workspace
• an Owner or Admin for workspace settings, integrations, and invitations
• one product or product area to use as the first scope
• one approved source of customer evidence, such as a call, support ticket, research note, document, or pasted text
• a teammate who can review whether the extracted learning is accurate

Use approved test or customer data and follow your organization’s privacy rules. Do not upload credentials, secrets, or material that your workspace is not allowed to process.

Open Settings → Workspace context and add the smallest set of facts needed to interpret the first source:

1. Describe the company and the product in plain language.
2. Add the product, relevant personas, goals, and important constraints.
3. Add or confirm the relevant product feature or product area.
4. Save names that teammates already use. Avoid creating a parallel vocabulary only for Zentrik.

Context is not a place to paste every internal document. Keep durable facts and definitions here; bring source material in as evidence or a context document when it needs provenance.

Use Workspace context for the difference between flat context, named records, documents, goals, and product features.

Open Settings → Team and invite the people who will review evidence or make the first decision.

• Use Owner sparingly for workspace ownership.
• Use Admin for teammates who must manage settings, integrations, API keys, or invitations.
• Use Editor for day-to-day product work without workspace administration.
• Use Viewer for read-only access.

The invitation appears under Invitations until it is accepted. Confirm the email and role before resending or copying an invitation link.

See Workspace administration for role boundaries, billing visibility, API keys, and offboarding.

Choose one controlled path:

• connect an approved provider under Settings → Integrations
• upload or paste a call transcript, ticket, research note, or document
• use the Signals API when the source is produced by another system

Start with one or a small batch. Confirm the source title, product scope, account or participant context, and processing result before scheduling a large import.

Evidence to insights covers manual and connected imports. Engineers can use the Signals API quickstart.

Open the processed signal in Discovery and check:

1. The source content is complete enough to support a claim.
2. The signal is attached to the correct product and account context.
3. Each suggested insight says something the evidence actually supports.
4. The wording separates an observed customer problem from a proposed solution.
5. Incorrect or duplicate learnings are edited, rejected, merged, or left unapproved.

AI output is a proposal. A useful first result is one trustworthy learning with a visible link back to the source—not the largest possible number of generated insights.

Decide what the reviewed learning needs next:

• Link related insights into an opportunity when they describe the same problem, unmet need, or strategic bet.
• Create or connect an idea when the team has a possible answer worth exploring.
• Start a study when the idea needs evidence before commitment.
• Promote validated work to an initiative when the team is ready to define scope, success, and delivery.

Keep the source trail intact. The purpose of the workflow is not to move every item downstream; it is to make the next decision explainable.

• Build the discovery habit with Insights to opportunities.
• Add classification only when volume requires it with Taxonomy and themes.
• Validate a solution with Idea Studies.
• Commit, sequence, and communicate work with Priorities, planning, and roadmaps.
• Turn the decision into reviewed artifacts with Documents and delivery.

The first setup is useful when:

• product vocabulary and goals are understandable to the teammates who use them
• the right teammates have the least access they need
• one approved source is processed under the correct product scope
• at least one reviewed insight links back to that source
• the team can state the next decision and why it is or is not moving forward
• unanswered setup questions have an owner or a support handoff