SupportSettings
Configure the identity, people, data model, communications, integrations, and technical access for this sub-account.
How this fits into Lead360Explore the agency and client platformConnect administration, providers, users, billing, and developer access.- 01
How Lead360 helps
- 02
Choose the correct area
- 03
Use a safe workflow
- 04
Use Ask360 here
How Lead360 helps
Lead360 Settings is the administrative map for business identity, staff access, calendars, integrations, data definitions, communications, tracking, billing, and developer credentials. Starting in the correct area helps teams understand dependencies and make the smallest controlled change.
When to use this area
Use Settings when a shared sub-account behavior or administrative record must be reviewed, configured, or handed to the feature owner.
Before you begin
- State the intended outcome and affected users or customers.
- Identify dependent pages, messages, automations, reports, and integrations.
- Confirm authorization and prepare a controlled test.
Choose the correct area
- Business Info controls public identity and timezone.
- Team Members controls staff access.
- Calendar Settings and Integrations connect scheduling and external services.
- Tags, Custom Fields, Custom Values, and Objects define reusable data.
- Email Settings and Phone Settings control customer communications.
- External Tracking and Developers control measurement and technical access.
Use a safe workflow
- State the outcome before editing.
- Review downstream pages, messages, automations, imports, reports, and integrations.
- Make the smallest change possible.
- Test with controlled data.
- Confirm the customer-facing result before broader use.
Use Ask360 here
Open the exact Settings page before selecting Ask more so Ask360 receives that page scope and its allowed operations. It should explain or prepare only the requested setting, ask for missing information, wait for explicit approval where a live change is supported, and never replace the request with an unrelated report.
Confirm the result
A completed Settings workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.
- Review the saved value in its owning settings page.
- Test a representative downstream workflow.
- Confirm customer-facing and staff-facing behavior before broader use.
Troubleshooting
A change has no visible effect
Check page-level overrides, publication state, cache, integration mapping, and whether a different settings area owns the behavior.
A shared change affects too much
Restore the prior value where appropriate, identify dependent records, and replace the broad setting with a more specific configuration.
Frequently asked questions
What should I confirm before using Settings?
State the intended outcome and affected users or customers. Identify dependent pages, messages, automations, reports, and integrations. Confirm authorization and prepare a controlled test. Start with a small, reviewable change whenever the workflow can affect customers, money, published content, or shared records.
How does Lead360 help with Settings?
Lead360 Settings is the administrative map for business identity, staff access, calendars, integrations, data definitions, communications, tracking, billing, and developer credentials. Starting in the correct area helps teams understand dependencies and make the smallest controlled change.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.