How teams use settings & admin
Teams usually review settings & admin when they want to improve a specific operating motion, not just add another isolated feature. In practice, that means turning related capabilities such as Team Management, Activity Logs, AI Agent Configuration, Database Types into one clearer workflow that reps, managers, and operators can actually use every day.
For most buyers, the real question is how this category changes execution. Common evaluation paths include manage users and ownership, audit important changes, standardize crm data, where the value comes from cleaner ownership, faster next steps, and better visibility into what should happen after each customer interaction.
A strong rollout usually starts with one high-value use case, then expands into reporting, automation, and team inspection once adoption is consistent. That is why this category page groups related modules together first and then links into deeper feature pages for more specific evaluation.
Explore modules
Settings & Admin features
Pick a module to see details, workflows, and how it fits into the CRM.
Common use cases
Where teams use settings & admin
Practical workflows built from the features in this category, grouped around the outcomes teams usually care about first.
Use these examples to decide whether you need one focused capability or a broader category rollout. In most teams, adoption improves when the first workflow is concrete and tied to a measurable operational problem rather than a broad feature wish list.
Manage users and ownership
Set teams, roles, and responsibilities so work lands with the right people.
See workflowAudit important changes
Use activity logs to inspect configuration changes, user actions, and operational issues.
See workflowStandardize CRM data
Use database types, stages, and templates to keep reporting clean as usage grows.
See workflowConfigure AI safely
Set agent behavior, tone, and guardrails before teams scale AI-assisted work.
See workflowSuggested workflow
Turn features into a working motion
Start with a focused setup, connect the next action, and expand once the team has a repeatable rhythm.
Step 1
Start with the core workflow
Use Team Management as the first workspace so the team has one clear place to begin.
Step 2
Connect the next action
Layer in Activity Logs to turn the workflow into repeatable daily execution.
Step 3
Scale what works
Use AI Agent Configuration to refine adoption, coaching, and team visibility as usage grows.







