# Plugins (/docs/plugins)



Plugins are optional add-ons you can install to extend your Resytech dashboard. Each plugin adds a specific capability — an AI assistant for your staff, a two-way SMS inbox, and more over time — without you having to ask support to turn anything on.

You browse, install, configure, and enable plugins yourself from the **Plugins** menu.

<Cards>
  <Card title="Staff Assistant" href="/docs/plugins/staff-assistant" />

  <Card title="SMS Inbox" href="/docs/plugins/sms-inbox" />
</Cards>

Finding plugins [#finding-plugins]

Open the **Plugins** menu in the main navigation, then choose **Browse Plugins**. The marketplace lists every available plugin with a short description and its current status (installed, enabled, or available).

<Callout type="info">
  The **Plugins** menu only appears for users who can manage plugins, or once at least one plugin is enabled. If you don't see it, check that your role has the **Plugins** permission.
</Callout>

Installing and enabling a plugin [#installing-and-enabling-a-plugin]

Installing and enabling are two separate steps, so you can set a plugin up fully before it goes live.

1. **Install** — from the marketplace, click **Install** on the plugin you want. You're taken straight to the plugin's **setup page**.
2. **Follow the getting-started guide** — each plugin's setup page walks you through what it needs.
3. **Configure** (connectors only) — some plugins connect to an outside service and ask for credentials (for example, an API key). Enter them and save. Secrets are stored encrypted and never shown again.
4. **Enable** — once any required configuration is in place, click **Enable**. The plugin's page now appears under the **Plugins** menu for your team.

Two kinds of plugin [#two-kinds-of-plugin]

* **Feature plugins** add first-party functionality and just need to be enabled (for example, the SMS Inbox reuses your existing Twilio connection).
* **Connector plugins** link to an outside service and require configuration — usually an API key or account ID — before they can be enabled.

Disabling and removing [#disabling-and-removing]

* **Disable** turns the plugin off and hides its page from the menu, but **keeps its configuration and data**. Re-enabling restores everything.
* **Remove** uninstalls the plugin. Its configuration is cleared; you'd set it up again from scratch if you reinstall.

<Callout type="info">
  Disabling a plugin is non-destructive and reversible — use it whenever you want to temporarily switch a plugin off.
</Callout>

Permissions [#permissions]

* **Managing plugins** (installing, configuring, enabling, removing) requires the **Plugins** permission. Administrators always have it.
* Some plugins add **their own permissions** for specific actions — for example, sending a message in the SMS Inbox. These are assigned to roles like any other permission.

Per-location vs. account-wide [#per-location-vs-account-wide]

A plugin is enabled per **location**, so you decide which of your locations have it switched on. Most plugins scope their data to that location; a few (like the SMS Inbox, which uses your company's Twilio number) are shared across your whole company. Each plugin's page notes how it behaves.