# Help and community

> Where to get support, talk to other Cephable users, report a bug, and request a feature.

Source: https://help.cephable.com/docs/community

---

There is a real community around Cephable, and more than one way to reach us. Pick the one
that fits what you need.

## Getting support

:::cards columns="2"
:::card title="Discord" href="https://discord.com/invite/YSDpstxXb5" icon="chat"
**Our main support channel.** Ask a question and you will usually hear back within 48
hours. It is also the liveliest place to talk to other users.
:::

:::card title="Support and feature requests" href="https://forms.office.com/r/7L4mySZBbL" icon="clipboard"
Found a bug, or have an idea? This form goes straight to the team and is the best route
for anything that needs tracking.
:::
:::

## Community

:::cards columns="3"
:::card title="Slack community" href="https://join.slack.com/t/cephablecommunity/shared_invite/zt-41yz97gee-Rk7mXqgd64ocd32eY3uAvA" icon="chat"
A public community for finding help, sharing tips and tricks, and keeping up with new
developments.
:::

:::card title="Facebook group" href="https://www.facebook.com/groups/274996862002777" icon="user"
Support and networking with other Cephable users.
:::

:::card title="Use case videos" href="https://cephable.com/resources/use-cases" icon="play"
Real workflows across the apps you already use, driven by what users actually do with
Cephable.
:::
:::

:::callout type="tip" title="Which channel for which question"
**Discord** for "how do I…" and "is this thing broken?" — someone has usually hit it
before. **The form** for anything that needs to become a ticket: a reproducible bug, a
feature request, an account problem. **Slack** for a longer conversation with other users.
:::

## Organization support

If your Cephable comes through work or school on a Pro, Team, or Enterprise agreement, you
have a named support contact as well. It is listed under **Organization → Support** in the
[Cephable Portal](https://portal.cephable.com). For anything account- or licence-related,
start there rather than in a public channel.

## Reporting a security issue

Security reports go through the
[Responsible Disclosure & Bug Form](https://forms.office.com/Pages/ResponsePage.aspx?id=nXUREBN1JUCrY3YZ6NyUAARlHwrMczBIt12HSkR_1SpUQzhLQjVFVUJQNUtROVRDQ1lHTE5SMkFGSC4u)
rather than a public channel, so it reaches the right people without being visible while it
is being fixed.

## Following along

New releases, use cases, and accessibility work get posted across
[YouTube](https://www.youtube.com/@cephable),
[LinkedIn](https://www.linkedin.com/company/cephable),
[Instagram](https://www.instagram.com/cephable/),
[TikTok](https://www.tiktok.com/@cephable?lang=en),
[X](https://twitter.com/cephable), and
[Facebook](https://www.facebook.com/Cephable/).

YouTube is the one worth subscribing to if you only pick one — that is where the use case
walkthroughs land.