Find the right connection settings in Brixit CRM
Connection settings are split by purpose. Use this map before changing an account or service configuration.
| Where | What belongs there | Guide |
|---|---|---|
| Integrations → Apps | Advertising channels, WhatsApp, Google Calendar and other enabled apps | How integrations work |
| Integrations → Portals | Brokerage portal accounts and publishing/lead connections | Portal integrations |
| Settings → Zapier & n8n | Automation connections to external workflows | Automation, n8n, Zapier |
| Settings → Services & Credentials | Company-managed services and service availability | Email delivery, Turnstile |
| Avatar → Profile Settings | Your personal mailbox and profile | |
| Avatar → AI connections | Your assistant’s connection to the CRM | AI connections |
Review Services & Credentials
Open Settings → Services & Credentials. The page groups services by who manages them: Provided by your company, Provided by Brixit, Managed by this installation and Disabled services.
Choose the relevant service, read its ownership and status, and follow its dedicated setup guide. Shared Brixit-managed applications and company-managed services have different setup responsibilities. If a provider-managed service is unavailable, use the status message and support path rather than entering unrelated company settings.
Configure an app or portal
Open the app or portal card, complete the supported connection flow and return to Brixit to verify the connected account. For lead intake, finish field mapping and select an assignment strategy for each relevant form. A connected account alone does not finish form routing.
For publishing, connecting a portal is the setup step. Agents publish each property from its Portals tab using the listing publication guide.
Troubleshoot in the correct place
Check the service owner, connected account, enabled state, your permissions and the specific error. Personal mailbox issues belong to the user’s connection; system-email issues belong to company delivery; listing rejection belongs to the portal publication. Include the error and time when escalating a failed connection.