Transform Community
Simple guidelines to keep the Transform Community helpful, welcoming, and safe.
Overview
The Transform Community provides a shared space for product questions, bug reports, and feature ideas.
Community channels complement support. They are best for general workflow questions and shared patterns.
Key Concepts
Community: public discussion space hosted outside Transform
Channel: topic-based area used to route questions
Support: private channel for account-specific or urgent issues
How It’s Used
Use community channels for workflow questions and best practices.
Use support for urgent, billing, security, and access issues.
Benefits
Faster answers through shared patterns
Reduced duplicate questions through searchable threads
Better product feedback through structured ideas and bug reports
Setup Steps
Request a community invitation: help@transform.ai.
Read the Transform Community Guidelines.
Post an introduction in the general channel.
Route posts using the channel directory.
Don’t share passwords, API tokens, or client/customer PII. Redact screenshots before posting.
Best Practices
Keep one topic per post.
Include scope and reproduction steps for bugs.
Follow up with the resolution when an answer works.
Summary
Start here:
Overview
Community guidelines keep support and discussion productive.
They protect sensitive information and maintain respectful collaboration.
Key Concepts
Channel: topic-based area used to route posts
Thread: follow-up discussion that keeps channels scannable
Moderation: enforcement of guidelines for safety and usability
How It’s Used
Use these guidelines for every community post.
Use support instead of community channels for urgent or account-specific issues.
Benefits
Faster answers through better routing and clearer posts
More usable channels through thread hygiene
Reduced risk through consistent data handling
Setup Steps
Route posts to the correct channel type (help, bugs, ideas).
Use threads for follow-ups.
Keep one topic per post.
Redact sensitive information in screenshots.
Quick routing
Post in the right place for faster answers.
How-to questions → help channel
Bugs and errors → bugs channel
Feature ideas → ideas channel
Be professional
Be respectful.
Assume positive intent.
Disagree on ideas, not people.
Protect data
Don’t post confidential client information.
Don’t share passwords, API tokens, or credentials.
Redact screenshots before posting.
Don’t share client or customer PII in community channels. Redact before posting.
No spam or unwanted self-promotion
Don’t send unsolicited DMs.
Don’t post affiliate links.
Don’t aggressively self-promote.
Share resources only if they help. Add context when you do.
Keep channels usable
Use threads for follow-ups.
Search before starting a new post.
Keep one topic per message.
Moderation
Transform moderators may remove content that breaks these rules.
Repeated issues may result in removal from the community space.
Summary
Guidelines optimize for routing, professionalism, and safe handling of sensitive data.
Overview
Channel routing improves response time and keeps discussions searchable.
Use this directory to select the correct channel type.
Quick routing
Start in the right channel for faster answers.
Intros and general chat → general channel
“How do I...?” questions → help channel
Bugs and errors → bugs channel
Feature requests → ideas channel
Transform updates (read-only) → announcements channel
Not sure? Start in the help channel.
Key Concepts
General channel: introductions and broad discussion
Help channel: workflow questions and setup guidance
Bugs channel: defect reports with reproduction steps
Ideas channel: product improvements and feature requests
Announcements channel: product updates (read-only)
How It’s Used
Route posts to the channel type aligned to the intent.
Escalate urgent issues to support instead of community channels.
Benefits
Faster responses through better routing
Cleaner channels through reduced off-topic noise
Better searchability for repeated questions
Setup Steps
Pick the channel type based on intent.
Keep one topic per post.
Use threads for follow-ups.
Channel directory
General channel
This is the main community hub.
Use it for:
Introductions and meeting other Transformers
General Transform questions and discussions
Wins, launches, and success stories
Tips and tricks
Off-topic chat (keep it professional)
Intro content can include:
Role and delivery context
What Transform supports in current work
Topic areas of interest
Announcements channel
Transform team announcements only.
Expected content:
Product updates
Release notes and improvements
Company news
Replies belong in threads. New posts are restricted.
Use the general, help, or ideas channel instead.
Help channel
Ask “how do I…” questions and get workflow guidance.
Use help when the category is unclear.
Target response time for Transform responses: within 1 business day.
Business hours: Mon–Fri, 8am–6pm Mountain Time (MT).
Full guide: Get Help
Bugs channel
Report broken features, errors, and technical issues.
Full guide: Report a Bug
Ideas channel
Suggest enhancements and vote on what you want next.
Full guide: Submit Ideas & Feature Requests
Quick norms
When routing is unclear, start in the help channel.
Use threads for follow-ups.
Use reactions for voting and confirmation when supported.
Mark resolution clearly when supported.
Don’t share passwords, API tokens, or client or customer PII. Redact screenshots before posting.
Summary
Channel routing improves response time and keeps community content searchable.
Last updated