Get Help
Whether you have a question about a feature, need help with configuration, or want to report a problem, SetGet provides multiple support channels. This page helps you find the right resource for your situation.
Choosing the right channel
| Situation | Best channel |
|---|---|
| Learning how a feature works | Documentation |
| General question or discussion | Community forum |
| Account or billing issue | Email support |
| Bug or unexpected behavior | GitHub Issues |
| Feature idea or improvement | Feature request board |
| Urgent production issue (paid plans) | Priority email support |
| Self-hosted deployment help | Documentation + community forum |
Documentation
The SetGet documentation (where you are reading this) is the first place to look. It covers every feature, from getting started to advanced administration.
Finding what you need
- Search — Use the search bar at the top of the documentation site to find pages by keyword.
- Navigation — Browse the sidebar categories: Getting Started, Work Items, Projects, Planning, Pages, Chat, AI, Automations, Admin, and more.
- Core Concepts — If you are new, start with Core Concepts for a complete overview.
- Glossary — If you encounter an unfamiliar term, check the Glossary.
Documentation feedback
If you find an error or gap in the documentation, you can:
- Click the Edit this page link at the bottom of any documentation page.
- Submit a correction via GitHub pull request.
- Or report the issue through the community forum.
Community forum
The SetGet community forum is the best place for questions, discussions, and sharing tips with other users.
What the forum is for
- Asking "how do I..." questions
- Sharing workflows and best practices
- Discussing integrations and use cases
- Getting help from other SetGet users and team members
- Announcing community-built tools and plugins
Forum guidelines
- Search before posting — your question may already be answered.
- Provide context — mention your deployment type (cloud or self-hosted), browser, and what you have already tried.
- Be respectful and constructive.
Email support
For account-related issues, billing questions, or problems that require private communication, contact the SetGet support team directly.
| Contact | Details |
|---|---|
| Email address | support@setget.dev |
| Response time (free) | Within 3 business days |
| Response time (Pro) | Within 1 business day |
| Response time (Business) | Within 4 business hours |
| Response time (Enterprise) | Within 1 business hour, dedicated support |
What to include in your email
To help the support team resolve your issue quickly, include:
- Your workspace name or URL.
- A clear description of the problem or question.
- Steps to reproduce (if reporting a bug).
- Screenshots showing the issue.
- Browser and OS you are using.
- Deployment type — cloud or self-hosted (include version number).
TIP
The more context you provide upfront, the faster the support team can help. A good bug report with reproduction steps and screenshots can often be resolved in a single reply.
Bug reporting
If you encounter a bug — unexpected behavior, errors, or broken functionality — report it through GitHub Issues.
How to report a bug
- Go to the SetGet GitHub repository.
- Click Issues > New Issue.
- Select the Bug Report template.
- Fill in the template fields:
| Field | What to provide |
|---|---|
| Title | Short, descriptive summary of the bug |
| Description | Detailed explanation of what happens |
| Steps to reproduce | Numbered steps to trigger the bug |
| Expected behavior | What should happen |
| Actual behavior | What actually happens |
| Environment | Browser, OS, SetGet version, deployment type |
| Screenshots/logs | Visual evidence or error logs |
Bug report tips
- One bug per issue — Do not combine multiple bugs in a single report.
- Check existing issues — Search for your bug before creating a new report.
- Provide reproduction steps — The more specific, the faster the fix.
- Include error messages — If you see an error in the browser console, include it.
WARNING
Do not include passwords, API keys, or other sensitive information in bug reports. If logs contain sensitive data, redact them before posting.
Feature requests
Have an idea for a new feature or improvement? Submit it through the feature request board.
How to submit a feature request
- Go to the SetGet feature request board (linked from the GitHub repository).
- Search for existing requests that match your idea.
- If your idea already exists, upvote it and add your use case as a comment.
- If it is new, create a request with:
| Field | What to provide |
|---|---|
| Title | Clear, concise name for the feature |
| Problem | What problem does this feature solve? |
| Proposed solution | How do you envision it working? |
| Alternatives | Other approaches you have considered |
| Use case | Specific scenario where this feature helps |
How feature requests are handled
- Requests are reviewed by the SetGet product team.
- Popular requests (by upvotes and comments) are prioritized.
- Accepted features are added to the public roadmap.
- The team may reach out for clarification or additional context.
Self-hosted support
If you run SetGet on your own infrastructure, the same support channels apply with some additions:
- Deployment documentation — Covers installation, configuration, updates, and troubleshooting for self-hosted instances.
- Environment-specific issues — For problems related to your specific setup (OS, network, reverse proxy), the community forum is often the most helpful.
- Enterprise support — Enterprise customers receive dedicated support with direct access to the engineering team.
Related pages
- Troubleshooting — Solutions for common problems
- Keyboard Shortcuts — Quick reference for all shortcuts
- Glossary — Definitions of SetGet terms
- Account Settings — Manage your profile and preferences
- Introduction — Getting started with SetGet