How to submit an idea to the Nexus Community Ideas Hub — and why you should search, review, and vote first

How to submit an idea to the Nexus Community Ideas Hub — and why you should search, review, and vote first

We love hearing new product and community ideas. To keep the Ideas Hub effective and actionable, please search existing ideas and review/vote on them before creating a new submission. This helps prevent duplicates, concentrates community support behind the best suggestions, and speeds routing to product teams.

Quick overview

• Step 1 — Search for similar ideas
• Step 2 — Read details and add your vote or comment
• Step 3 — Submit a new idea only if no good match exists
• Step 4 — Follow up and engage with feedback

Step 1 — Search first (how to find existing ideas)

1. Open the Nexus Community and go to the Ideas Hub.
2. Use the search box at the top — try multiple keywords (feature names, pain points, product areas). Use quotes for exact phrases and try synonyms.
3. Apply filters: Status (New, Under Review, Planned), Category, and Most Voted to narrow results.
4. Scan both highly-voted posts and recent submissions — sometimes the same idea exists but with different wording.

Step 2 — Review and vote (what to do when you find a match)

If you find an idea that matches your need, please:

• Upvote it — votes are the primary way product prioritizes requests.
• Comment with use case details or impact — concrete examples strengthen the request (number of users affected, frequency, business impact).
• Avoid posting a duplicate — instead, add any new context to the existing thread so all feedback stays in one place.

Step 3 — Submit a new idea (only if no match exists)

If your search shows no suitable match, follow this structure to create a clear, actionable idea:

1. Click Submit Idea or Create in the Ideas Hub.
2. Write a concise title that summarizes the outcome (e.g., “Add cross-region service-level alerting in Skylar Advisor”).
3. Describe the problem, your desired behavior, and the benefit. Include:
   • Concrete steps or examples of how you’d use it
   • Business impact (time saved, revenue protected, fewer incidents)
   • Any constraints or compatibility notes
4. Select a relevant category and add 2–4 tags (product area, feature type, integration).
5. Attach screenshots, logs, or diagrams if helpful.
6. Click Submit. Once posted, encourage coworkers to review and upvote if they’re impacted.

Step 4 — Engage after submission

• Monitor comments and respond to clarifying questions — product staff and community members may ask for usage details.
• If the idea gains traction, product may mark status changes (Under Review, Planned) — you’ll typically see updates in the same thread.
• Share the idea link with teammates to collect additional votes and examples.

Tips for higher-impact ideas

• Show the problem through a short, reproducible scenario or step-by-step example.
• Quantify impact wherever possible (how many users, how often, estimated cost/time saved).
• Propose a simple, realistic solution or alternative approaches — product teams appreciate practical suggestions.
• Be concise: clear titles and structured descriptions make it easier for others to read and vote.

Community guidelines & moderator notes

• Be respectful and constructive in comments — this is a public forum.
• Do not post sensitive or confidential information.
• Moderators will merge or close clear duplicates and route serious ideas to product owners.
• If your idea is complex, moderators may request a brief follow-up or an internal design doc to assist triage.

Example idea template (copy & paste)

Need help?

If you have trouble finding an existing idea or formatting your submission, reply in the Community Information Forum or contact our Community Manager Sara Leslie and we’ll help consolidate or refine your request.

Thanks for contributing — your votes and clarity help shape ScienceLogicst roadmap and make our products better for everyone.