CRM settings, integrations and connected apps
Find Fulcrum CRM account and organisation settings, connected apps, integrations, AI credits and tool logs, and verify the access each workflow needs.
Find the right settings
| Area | Purpose |
|---|---|
| Profile & Security | Your identity and account security |
| Business Details | Organisation information |
| Teams & Members | People, team assignment and access |
| Custom Fields | Structured information on records |
| Lead Forms | Enquiry capture |
| Objectives | Configured business objectives |
| Connected Apps | Application access and related credentials |
| Product Catalog | Offerings used in invoices |
| Integrations | Connections to external services |
| Public Chat | Customer-facing chat configuration |
| AI Credits | AI service allowance and usage context |
| MCP Tool Logs | Review of connected agent tool activity |
| Developer API | Integration reference for developers |
Some areas are restricted by role. See Roles and permissions before changing access to solve a missing-menu problem.
Connect an external service
- Open Integrations and choose the intended service.
- Read the access requested and authenticate with the correct provider account.
- Return to CRM and inspect the saved connection and status.
- Run a small permitted test of the exact workflow you need.
- Verify the destination record or delivery result.
Signing in, reading records and writing records can require different scopes. A connected badge is only one part of the check. If credentials are revoked at the provider, reconnect through the supported flow rather than copying tokens into chat.
Connected apps and MCP
Review each app’s purpose and access. Use tool logs to diagnose the action, target and outcome when an assistant cannot complete a task. Logs can contain customer information, so redact them before sharing. Revoke credentials no longer needed and check that dependent workflows have an alternative before disconnecting a shared integration.
Public chat
Review the customer-facing instructions, supported knowledge and available actions before embedding a chat experience. Test it in a signed-out window with fictional data and verify the resulting enquiry or record. Do not assume a public visitor has the same authority as a signed-in employee.
Keep configuration changes reviewable
Change one relevant setting at a time and verify its effect. Record the previous value when a change could interrupt a team workflow. Check the selected organisation before changing business details, integrations or shared credentials.
Last updated