Settings

Settings is where you manage the workspace itself, rather than its content: its name and look, which browsers and phones can sign in, the job queue, exports and backups. Open it from the workspace menu or the user menu (both at the edges of the sidebar), or from the command palette (⌘ K).

Common tasksCopy Anchor Link

• Connect your phone: Settings → General → Devices → Connect a device (on a local install also in the user menu). In cloud mode it signs the phone in as you. See Phones & tablets.
• Sign out a lost device: find it under Devices and sign it out.
• Back up your data: Settings → Backups shows the commands for Staqly Community Edition (staqly serve backup <file>, or docker exec staqly server backup /data/backups/<file> with Docker); on Plus and above it creates and lists downloadable backups (on Starter it points to the data-only export). See Backup & restore.
• Download everything: Settings → Data & privacy → Export workspace (on the Starter plan without the media files).
• See what the server is doing: Settings → System → Queue lists publishing and schedule jobs with a Retry for failed ones.
• Connect an agent: open Integrations (under Automation in the sidebar) for copy-ready setup steps.
• Change how you sign in: Settings → Account → Sign-in methods (cloud). See Accounts.

Settings tabsCopy Anchor Link

Settings has these tabs: General, Members (cloud, for owners and admins), Account (cloud), Plan & usage (with the billing in cloud mode), Data & privacy, Backups and System. Alerts have their own page, Alerts in the sidebar (see Alerts).

GeneralCopy Anchor Link

How long a post on your own automation may wait for a result is a collection setting (Fail publishing if nothing is reported within in Collection settings); without one, the server's PROCESSING_TIMEOUT (default 1 hour) applies.

Every browser signs in once, also in the Community Edition (with the access token, a link or a QR code), so Devices lists every browser that signed in, this computer included.

Members and Account (cloud)Copy Anchor Link

Members lists who can open the workspace with their role, and the open invitations. Invite people opens a short form (an address and a role). Plans are priced per user: while the workspace pays, the card says how many seats are billed and the form says what one more person costs ("Each person you add is billed €29/month on Plus (prorated)."). Account shows your sign-in methods (add Google, add a passkey, change your email address, each in a small dialog) and, for the account owner, the account's workspaces. See Accounts. Its Notifications card picks which events reach you by email and in the bell; see Your notifications.

Plan & usageCopy Anchor Link

The workspace's plan and where it stands (trial with the days left, active, payment failed, ending), this month's usage, and in cloud mode for owners and admins the billing: the price per user, the seats and the next payment, add-ons, extra X posts, the card on file and the invoices. Change plan opens the plan picker. See Plan & usage.

Data & privacyCopy Anchor Link

In cloud mode on the Starter plan, Export workspace builds a data-only ZIP: the same files without the media files (media.ndjson still lists each file by id, name and type). A note under it says that files, backups and the activity log export come with Plus and above, and the Activity log card is not shown.

See Data export.

BackupsCopy Anchor Link

In the Community Edition, the Backup & restore card shows the commands for a consistent copy of the database and the uploads, in two tabs:

• staqly serve: staqly serve backup ~/staqly-backup.db (pass the same --data you run Staqly with), then copy the uploads folder of the data directory.
• Docker: docker exec staqly server backup /data/backups/staqly-backup.db, docker cp to copy it out, and a tar of the uploads from the data volume.

In cloud mode on a paid plan, the Backups card lists the workspace's backups (GET /v1/workspace/exports). Create backup builds a ZIP of the whole workspace (collections, posts, channels, schedules, events and media); when it is ready, Download works for 24 hours. On Starter the tab says that backups come with Plus and above and links to the data-only export in Data & privacy.

See Backup & restore.

SystemCopy Anchor Link

See Monitoring.

IntegrationsCopy Anchor Link

Integrations (under Automation in the sidebar) has these tabs: Setup (how to connect an agent), Agents & activity (who is connected and what they did) and, in cloud mode, API keys.

On Setup:

• Connection: your instance's agent URL and a Test connection button (it checks /health and your session through the dashboard proxy and shows the version, workspace and who you are signed in as). The Community Edition points agents at this computer with its access token over HTTP (or STDIO inside the Docker container, without one); cloud mode points them at its own address with an API key. The Community Edition never uses cloud API keys.
• Access token Community: the token agents, scripts and n8n send as Authorization: Bearer, masked, with Copy and Rotate. Rotating makes a new token: the old one stops working at once, every other browser is signed out (this one stays) and your agents need the new token. See the access token.
• Tabs Claude Code, Codex, OpenCode, n8n and REST & MCP, each with a copy-ready snippet using your instance's real URL (with $STAQLY_API_KEY for the access token locally, and in cloud mode the API key you just created) and a Full guide link to these docs. ?tab=codex opens a tab directly; ?view=agents opens Agents & activity.

On Agents & activity:

• Agents (MCP clients) and API connections (REST clients): everything that talked to this workspace (see Agents).
• Recent activity: the latest agent events (in cloud mode: events triggered with API keys). Select one to see only its events; Show all goes back. View all opens Activity.

API keys cloud (/integrations/api-keys):

• Create API key: a name (required), a set of scopes and an expiry: 1 hour, 8 hours, 1 day, 1 week, 1 month (the default), 1 year, or a day you pick up to a year ahead. A key never lasts longer than a year. Presets fill in the scopes for you:

  Preset	Scopes
  Content agent (default)	collections:read, posts:read, posts:write, posts:publish, media:read, media:write
  Publisher automation	posts:read, posts:publish (reports results for your own automation)
  Read-only agent	collections:read, posts:read, channels:read, events:read
  Full access	Every scope, including admin

  Only Full access can delete: tick posts:delete (posts and media) or collections:delete yourself for a key that should clean up.

  The raw key is shown once.

• Each key shows its state: Active, Expired or Revoked.

• Rotate a key: revoke it and issue a replacement with the same name and scopes; the new key is shown once.

• Revoke a key.

• API keys are for agents and automation: people sign in to the dashboard with Google, an email code or a passkey, never with a key. In a workspace without an account, the key from signup, Admin key (or Admin key (recovered) after a recovery), is listed here too; don't revoke your last admin key unless you still have the recovery key.

Snippets on the integration pages include the key you just created. It is kept only in memory in that browser tab, never in local storage.

WebhooksCopy Anchor Link

Webhooks has its own sidebar entry: create, edit, test and delete endpoints, and browse the delivery history with manual retry. Each webhook is one row that starts with its Active / Paused switch (a paused webhook sends nothing; events in the meantime are skipped). The timeout is set in seconds. Click a delivery to see its full error and the receiver's response. See Webhooks.

Forms and messagesCopy Anchor Link

These conventions hold across the dashboard (posts, collections, channels, schedules, webhooks, alerts, API keys):

• Forms open in a drawer on the right; short ones (a name, an address, a code) in a dialog. Closing a drawer with changes you haven't saved (Esc or ×) asks Discard your changes? first; after a save it closes without asking.
• Required fields are marked with a red * after their label.
• Invalid fields turn red, with the message right under the field. Server-side errors (for example a name that is already taken) appear on the field they belong to.
• Messages (toasts such as Webhook created or an error) appear at the bottom right and close on their own; each has a close button (×) to dismiss it right away.

Next stepsCopy Anchor Link