Community support routing
Community Support Routing
Section titled “Community Support Routing”Community participation is best effort and does not provide guaranteed response times, private support, entitlement handling, license recovery, security intake, or behavioral enforcement.
Use the Day Shift Discord for optional public community discussion and peer learning. Use the routes below whenever the question needs an authoritative answer, private information, or formal handling.
Choose the correct destination
Section titled “Choose the correct destination”| Need | Destination |
|---|---|
| Shipped product behavior or workflow guidance | Read the canonical documentation and check day-shift --help. |
| Account, purchase, or entitlement handling | Use the website’s support entry point. |
| License delivery or recovery | Use the private recovery route. |
| Security reports or private support details | Email request@tnsds.tech. |
| Privacy questions | Review the privacy route. |
| Conduct or moderation reports | Follow the server’s posted rules and email request@tnsds.tech privately. |
| Release behavior or licensing terms | Check release notes or licensing terms. |
Keep sensitive material out of community channels
Section titled “Keep sensitive material out of community channels”Discord is a third-party public community service. Do not post secrets, license keys, purchase or entitlement details, private repository content, personal data, or security reports in community channels.
When in doubt, remove sensitive details and use the private destination above. A community response cannot grant an entitlement, recover a license, accept a security report, or promise a moderation result.
Fallback
Section titled “Fallback”If Discord or its invite is unavailable, use the community orientation for the boundary summary, continue with the canonical documentation, or choose the private support route that matches the need. No core Day Shift journey depends on Discord.