Map what your product does into features, then add useful screenshots with an approved agent.
A feature tree groups capabilities under product areas. For example, Reporting can contain Scheduled exports and Saved filters. Zentrik uses these records to connect feedback and work to the relevant capability.
The agent reads your approved product sources in its own environment. Send only approved product descriptions and images to Zentrik; do not upload the codebase.
Prepare safe access
Use an agent that can access the Zentrik MCP connector and the product sources you approve. This may be Codex, Claude Code, Cursor, or another MCP client with codebase and browser access.
Give the agent:
- the exact Zentrik workspace and product name
- read access to the product codebase
- official product, help, API, and release documentation
- an approved local, staging, or production browser session
- the product areas that are in or out of scope
Keep credentials in environment variables or the browser session. Do not paste API keys, tokens, source files, customer records, internal URLs, or unapproved excerpts into prompts or feature descriptions.
Build and review the tree
Build the feature tree
Read the existing feature tree before changing it. Use shipped behavior first, then code and tests, official documentation, and approved requirements.
Group features by real product areas or workflows. Add child features when they describe distinct capabilities. Preserve existing linked records, and avoid using libraries, setup steps, or marketing claims as feature names. The prompt below prepares a change list for review.
Copy-ready feature-tree prompt
Build or repair the Zentrik feature tree for:
- Workspace: <exact workspace name>
- Product: <exact product name>
- Codebase: <repository or local path>
- Official documentation: <URLs or local paths>
- Scope: <included and excluded product areas>
Confirm the connected workspace and exact product first. Read the current
product context and complete feature hierarchy before proposing changes.
Inspect the running product when available, plus navigation, permissions,
release notes, help content, API documentation, and approved product material.
Keep credentials, source files, private URLs, personal data, and customer data
that is not approved for Zentrik out of feature names and descriptions.
Create a tree that reflects how users get value:
- roots are real product areas, workflows, modules, or surfaces
- the product itself is not a root feature
- parents are concise signposts
- leaves are specific capabilities
- use the product's own vocabulary
- preserve valid existing records and relationships
- merge overlapping meanings
- split broad nodes only when they hide independently useful capabilities
- do not target a fixed count or depth
Write concise leaf descriptions that explain who uses the capability, the job,
what the user can do, what the product enables, and any boundary needed to
prevent confusion. Do not add source inventories, development notes, delivery
status, unsupported outcomes, or filler.
Before writing, return:
1. current-tree assessment
2. proposed final hierarchy
3. compact change list: keep, create, update, move, merge, or remove
4. evidence for material changes
5. areas that still need confirmation
Wait for approval. Then re-read the tree, apply only the approved delta, create
parents before children, and read the complete hierarchy back after each batch.
Never remove or rename linked nodes without explicit confirmation.
Finish with feature and root counts, duplicate names, invalid parents, remaining
overlap, and any part of the product map that still needs clarification.Review and apply
Use MCP for the normal agent workflow:
get_product_contextget_product_featurescreate_product_featureandupdate_product_featurebulk_create_product_featuresandbulk_update_product_featuresfor approved batches of up to 50
Create parents before children and use exact product and parent names. Feature names must be unique within the product for reliable name-based updates and screenshot attachment.
Treat removal as a separate decision. Existing feature IDs may already connect to evidence, ideas, studies, or initiatives.
Add feature images
Add feature images
After reviewing the tree, capture the smallest product state that demonstrates each capability. Use approved sample data and descriptive filenames. Reuse an image only when it shows each linked feature accurately.
Inspect images for secrets, personal data, password screens, and unrelated browser content before uploading. Add a mobile image when it demonstrates relevant behavior.
Copy-ready screenshot prompt
Populate screenshots for the approved Zentrik feature tree.
- Product: <exact product name>
- Product environment: <approved URL>
- Image location: <approved folder or asset library>
Read the complete tree first. For every feature, identify the smallest real
product state that proves the capability. Reuse an image only when the same
screen truthfully demonstrates each linked feature.
Use an approved account and populated sample data. Capture mobile only when responsive
behavior is part of the feature. Exclude secrets, personal data, password
screens, unrelated browser content, and customer information that is not
approved for this use.
Prepare a mapping with the exact product name, exact feature name, and image
filename. Show the mapping for review before upload.
After approval, attach each image to the exact product and feature. Check whether
an upload succeeded before retrying, and do not attach the same image twice.
Inspect the feature panels in Zentrik and report missing, repeated, irrelevant,
stale, or privacy-sensitive images.Available upload methods
An MCP-connected agent can use attach_product_feature_image after the tree and
image mapping are approved. The External API also supports feature creation,
updates, and image upload for teams that manage product context through an
automated workflow.
Use PNG, JPEG, WebP, or GIF files up to 10 MB. Keep API credentials in your approved secret store, verify each result before retrying, and inspect the finished feature in Zentrik.
Verify the result
Read back the complete tree. Check names, parent relationships, duplicates, capability descriptions, and image attachments. Leave uncertain capabilities for review. Confirm that images match the approved mapping and contain no unapproved data.
Troubleshooting
The proposed tree looks generic
Ask the agent to cite the shipped behavior or product documentation behind each material node. Remove capabilities that could describe any product in the category.
A feature cannot be updated by name
Check for duplicate feature names in the product. Resolve ambiguity before name-based MCP updates or screenshot attachment.
A screenshot may expose private information
Do not upload it. Recreate the state with approved test data, mask the sensitive value in the product when supported, or leave the feature without an image until a safe capture exists.
Continue from here
Related guides
Did this guide answer your question?
Your response helps us prioritize missing or unclear documentation.
Still stuck?
Send your question to Zentrik support. This guide will be included automatically.