Foundaro

Foundaro Front Docs

Settings

Settings covers your personal preferences and workspace-level configuration for Foundaro Front — notification rules, default behaviors, and integration settings.

Last updated:

Settings

The Settings section covers your personal preferences within Foundaro Front and, for Admins, workspace-level configuration that affects all users.

Account Settings

Account settings are personal to you and do not affect other team members.

Key fields:

  • Display name: Your name as shown in author credits and comments.
  • Email: The email address associated with your account. This is managed in the Foundaro Hub workspace settings.
  • Avatar: Your profile photo. Used in author bios, comments, and the activity feed.
  • Timezone: Your local timezone. Used for displaying dates and times in the editor.
  • Language: The interface language for Foundaro Front (if multiple languages are enabled).

Notifications

The Notifications section controls when and how Foundaro Front alerts you to activity.

Notification triggers:

  • Review assigned to me: Notify when a content item is assigned to me for review.
  • Review request approved: Notify when a review I submitted is approved.
  • Review request rejected: Notify when a review I submitted is rejected with feedback.
  • Comment on my content: Notify when someone comments on content I authored.
  • Comment reply: Notify when someone replies to a comment thread I participated in.
  • Content published: Notify when content I authored goes live.
  • Scheduled item missed: Notify when a scheduled item did not publish at the expected time.

Notification channels:

  • In-app: Bell icon notifications visible in Foundaro Front.
  • Email: Email to your registered address.

Tips:

  • Disable notifications you do not act on — notification fatigue causes important alerts to be ignored.
  • Enable the Scheduled item missed notification if you run time-sensitive campaigns.

Default Content Settings

Admin-only settings that pre-configure defaults for new content items.

Key fields:

  • Default site: The site pre-selected when creating new content.
  • Default author: Whether new content defaults to the logged-in user or a specific author.
  • Default review required: Whether all new content requires review before publishing.
  • Default reviewer: Who is assigned as reviewer when review is required.
  • SEO defaults: Default meta description template and OpenGraph image fallback.

Why it matters:

Sensible defaults reduce friction for authors. If 90% of content goes to one site, presetting that site means authors never have to change it.

Integrations

Admin-only settings for connecting external services.

Available integrations:

  • Analytics tracking: Paste your Google Analytics 4 measurement ID, Plausible domain, or Fathom site code. Applied to all sites unless overridden at the site level.
  • Webhook: Configure a webhook URL to receive a POST request when content is published, updated, or deleted. Useful for triggering CDN purges, search index updates, or custom pipelines.
  • Search: Connect an Algolia or Meilisearch instance for site search functionality.

Tips:

  • Site-level analytics settings override workspace-level settings. Use workspace-level for a default, and per-site settings for exceptions.
  • Test webhooks with a service like RequestBin before connecting to a production pipeline.