AI assistant

AI assistant (/admin/ai-assistant) connects signplume to an AI assistant that supports MCP connectors, such as Claude, ChatGPT, Microsoft Copilot (Copilot Studio), Gemini CLI, Claude Code, Cursor or VS Code. You then manage your organisation's signatures by asking: set up a new organisation, add and invite people, pick templates and rules, update your brand, run banner campaigns and read their clicks, check billing and who is signing.

Connect

The screen shows signplume's MCP address, with a Copy button, and the steps for each assistant. Paste the address where your assistant adds connectors. The first time, it sends you to signplume to sign in and approve. The public guide at /ai-assistant has the same steps, for anyone without an admin screen.

Your assistant also offers ready-made conversations: look for set_up_signplume, onboard_new_hire and banner_campaign among the connector's prompts.

What it can and cannot do

Your assistant acts as you. It can do what your role allows and nothing more, every change it makes is recorded on Activity as yours, and it never sees your password or your two-factor codes.

A few things stay on the signplume screens, because they handle a credential or your own sign-in: the Google Workspace and Microsoft Entra ID connections, the Outlook add-in key, the relay's credentials, IP ranges, header secret and route, your two-factor sign-in, and the billing portal.

Connected assistants

The screen lists the assistants you have connected, when each was connected and last used, and what they did recently. Disconnect removes one straight away.