Content Policy

What's Allowed

• ✓Honest reviews of software, SI partners, AMS vendors — even harsh ones. Negative feedback is valuable.
• ✓General descriptions of system behavior, bugs, and configuration approaches.
• ✓Salary and compensation data shared anonymously.
• ✓GIFs and memes via Giphy or Tenor links. Keep the community fun. Standard emojis welcome.
• ✓Casual language and conversational profanity. We're professionals, not robots.
• ✓AI use cases, tips, and prompt templates that help others.

What's NOT Allowed

• ✗
  No screenshots of software. Screenshots of proprietary vendor UIs, configuration screens, or dashboards are prohibited. This protects you and SSC from copyright and licensing claims. Describe the issue in writing instead — it's more searchable anyway.
• ✗
  No client-specific data. No order numbers, transaction IDs, inventory counts, customer PII, or any data that identifies a specific company's operations.
• ✗
  No licensed vendor documentation. Don't reproduce vendor manuals, training materials, or proprietary documentation verbatim.
• ✗
  No NDA violations. Don't share information you're contractually prohibited from disclosing. Liability rests with the poster.
• ✗
  No personal attacks or targeted harassment. Criticize companies and products, not individuals. No name-calling, slurs, or threats.
• ✗
  No personal information. Email addresses, phone numbers, and other PII are automatically blocked from posts.

How We Moderate

• •Automated checks scan content before it's posted. PII, screenshot links, and obvious violations are blocked instantly with a clear message explaining why.
• •Community flagging lets any member report content that violates policy. Flagged content is queued for admin review.
• •Vendor replies let companies respond to reviews publicly. We don't remove negative reviews — we give vendors a voice to tell their side.
• •Takedown requests require a specific reason and policy basis. Every decision is documented. We don't remove content just because someone doesn't like it.

Vendor Transparency

Vendor accounts are always visibly labeled. A vendor praising their own software is transparently identified as such. An in-house professional praising the same software carries different weight. This asymmetry is intentional — it's what makes SSC trustworthy.

Liability

SSC is a platform for user-generated content. We do not endorse, verify, or take responsibility for the accuracy of individual posts and reviews. Users are responsible for ensuring their contributions don't violate any contractual obligations they may have. We respond to legitimate takedown requests in good faith and comply with applicable law.