Use this guide when you need to change how TuitionFlow behaves for the whole organisation. Settings control identity, branding, billing, scheduling, onboarding, forms, lists, integrations, developer access, and other shared configuration.

Only owners and appropriate admins should change organisation-wide settings. A settings change can affect future invoices, lessons, onboarding forms, portal views, emails, integrations, or reports. If you are unsure whether a change should apply to one record or the whole organisation, test on a small workflow first.

Organisation overview settings define the basic business identity used across TuitionFlow. Keep company name, contact details, and public-facing information accurate. These details can appear in invoices, portals, policy pages, emails, and customer-facing journeys.

Branding settings control logos and visual identity. Upload clear light and dark logo variants where available. Preview branded sidebar or top bar behaviour before inviting families and tutors, because branding is one of the first things portal users notice.

Scheduling, billing, cancellation, and onboarding policies should be configured before you start live operations. Changing policies later is sometimes necessary, but it can make old records harder to explain if the team is not clear about what changed and when.

Forms and custom fields are powerful, but too many fields make onboarding harder and data quality worse. Ask for information that drives a real operational decision: teaching support, safeguarding, billing, matching, communication, or reporting. Keep master lists tidy so filters and dropdowns stay useful.

Integrations such as Stripe, QuickBooks, Google Calendar, Zoom, Teams, and other providers should be connected by the person who owns that external account. Before connecting, decide what the integration should do and who will monitor failures or sync issues.

Branches, API access, webhooks, and developer settings should be managed carefully. Treat API keys, webhook endpoints, and integration credentials as sensitive operational access. Remove anything that is no longer used.

If a setting does not appear, check your role and plan. If a setting appears saved but the app still behaves differently, refresh and check whether the affected workflow uses a separate policy or record-level override. If an integration fails, check the external account, permissions, and callback configuration.

Good settings make everyday work predictable: staff know what information to collect, parents see the right brand and billing details, tutors follow the right workflows, and integrations behave consistently.