adornConversations with room to think
Write with rich text, quotes, code, tables, and attachments. Keep reply context and revision history close to the conversation.
The Adorn product
A customer community that keeps work moving.
Give customers a place to talk, find answers, and help shape your product. Give your team the context and ownership to follow through.
Start for freeHarbor community
Search conversationsLatest conversations
All spaces- 4 replies
Can I share one dashboard across three teams?
Questions & answersMaya Chen
Answered - 12 replies
A shared view across every workspace
Product feedbackAlex Rivera
- 8 replies
A few things worth knowing before your first rollout
Getting startedJamie Lee
- 6 replies
What’s the best way to bring a new team on board?
Questions & answersSam Taylor
Answered - 3 replies
Weekly digests for the conversations I follow
Product feedbackMaya Chen
A real community. A useful place to return to.
Make room for everyday discussions alongside questions, announcements, and feedback. Spaces, tags, and search help people find their way. New and unread views help them pick up where they left off.
Questions with a next step
From the open queue to a useful answer.
See unresolved questions together. Put an owner on the next step, then leave an accepted answer the next customer can find.
Harbor community
Search conversationsQuestions that need an answer
Across your spaces and products
How do we connect our new workspace?
- Owner
- Jamie Lee
- Status
- Unresolved
- Product
- Harbor Cloud
Can we export a report for each team?
- Owner
- Unassigned
- Status
- Unresolved
- Product
- Harbor Analytics
Who can change our account permissions?
- Owner
- Sam Taylor
- Status
- Unresolved
- Product
- Harbor Cloud
Harbor community
Search conversationsQuestions & answersAnswered
Can I share one dashboard across three teams?
Maya Chen
Acme · Customer operations
We’re bringing three teams into Harbor. How can we keep projects separate without losing the bigger picture?
Assigned to Jamie Lee· Harbor team
Accepted answer
Jamie Lee · Harbor team
Yes. Keep each team’s projects in its own workspace, then bring them together in a shared dashboard.
Accepted by Maya Chen
4 repliesBookmarkedFollowing
Built for participation
The details that make a community work.
Attention people can control
Follow a conversation, choose major updates, or mute it. Keep email preferences separate and save useful posts with bookmarks.
Moderation with a record
Review reports, inspect the reported revision, and record a decision. Move, split, or merge conversations as the community develops.
Knowledge people can find
Search across the content each person can access. Make public conversations discoverable with readable URLs and search-engine metadata.
Built around your customers
Keep the relationship connected to the work.
Customer accounts, products, and access are part of the community. Keep that context with a support handoff, a product request, or a private conversation.
Customer accounts
Connect members to the companies they work with, including people who support more than one account.
Private spaces
Bring a customer’s team together with manually managed membership and private access. Automated entitlement access is planned.
Product feedback · Planned
Keep related requests, customer evidence, decisions, and updates together. Planned for every tier.
Your existing tools
Connect your customer login with JWT SSO on Pro and above. Developer APIs, webhooks, and tool integrations are planned.
Build your customer community.
Give your customers a place to ask. Give your team a way forward.