# General preferences General preferences define shared assumptions for your workspace.\ They affect how values are displayed, how contact data is interpreted, and how forecast calculations work. These settings are global and apply to all users inside the workspace. Watch this short YouTube video showing how to configure general preferences in Fluid CRM: *** ### Currency The currency setting defines how deal values are displayed across Fluid. This affects: * Deal values on the Deals board * Pipeline totals * Forecast calculations * Average deal size Currency does not convert existing values.\ It only changes how numbers are labeled and displayed. *** ### Phone country code The phone country code is used as the default prefix for phone numbers. This helps: * Normalize phone numbers * Reduce manual formatting * Keep contact data consistent You can still enter full international numbers manually when needed. *** ### Average sales cycle The average sales cycle defines how long deals typically take to close, measured in days. This value is used by: * The Forecast page * Three-month revenue projections * Expected close timing calculations It does not force deals to close on a specific date.\ It is a timing assumption used only for forecast math. If your sales process changes, updating this value improves forecast accuracy. *** ### Saving changes Changes in General preferences take effect immediately after saving. They: * Do not modify existing deals directly * Do not overwrite deal-level values * Influence calculations and defaults going forward *** *** ### What General preferences are for General preferences are designed to: * Set shared defaults * Reduce repeated configuration * Improve forecast accuracy * Keep data consistent across the workspace They are not meant for per-user customization. *** ### What to read next * Forecast – how sales cycle and probabilities affect projections * Data field management – customizing deal fields * --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fluid-crm.gitbook.io/fluid-crm-docs/settings/general-preferences.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.