Settings overview
Your personal settings in StickyPrompts: Profile, Response Styles, Snippets, Preferences and API keys, and where each one is explained.
Your personal settings control how StickyPrompts works for you: your name and password, the styles your replies are written in, the snippets you switch on in chats, the model and style new chats start with, and the API keys for your own tools. They affect only your account. Workspace-wide rules, such as which models are allowed, are set by admins in the workspace settings.
Open settings from the user menu at the bottom of the left sidebar. The Settings page has five sections, listed on its left.
The five sections
| Section | What you do there |
|---|---|
| Profile (1) | Change your first and last name, change your password, log out or delete your account. |
| Response Styles (2) | See your own, workspace and built-in styles, copy Prompty or Chatty, and create, edit or delete styles. |
| Snippets (3) | Create, edit or delete snippets: reusable context and instructions you switch on in any chat with the puzzle button. |
| Preferences (4) | Choose what Enter does, your Preferred AI model, your Preferred AI style, and what happens when you switch model in a chat. |
| API keys (5) | Create keys for the StickyPrompts REST API and MCP server, and see your existing keys. |
Your name, password, logging out and deleting your account.
Response stylesShape every reply: Prompty, Chatty or a style you write.
SnippetsTell the AI about you, your company or a client once.
PreferencesDefault model and style, On enter and model selection behavior.
API keys and authenticationCreate a key, pick its permissions and connect.
API keys
API keys is where you create keys for the StickyPrompts REST API and MCP server, so your own scripts, or an MCP client such as Claude or Cursor, can work with your workspace as you. Select Generate key, give it a name and choose its permissions. The full key is shown only once, so copy it straight away. The page also shows the REST API and MCP URLs and the Authorization header to use.
A key acts with your access, so treat it like a password: never paste it into a chat, a shared document or source code. The full guide is in API keys and authentication.