Admin, account and security

Roles and permissions

Give each teammate the right role — admin, manager, member, or viewer — and let KudosCRM's layered, deny-wins permission engine enforce what they can see and do across the whole CRM, with per-user overrides that are audited.

Set up sales territories

Build a territory hierarchy with effective dates, priorities, and a manager plus reps, then let assignment route leads, companies, and deals to the right team — with a full assignment-history audit.

API tokens and the REST API

Read and write your CRM data from your own code over a REST API — contacts, deals and custom objects — authenticated with a token you mint and can revoke.

Change your password and secure your account

The account security you control yourself, what protects your data at the platform level, and an honest account of which enterprise controls are available and on which tier.

Custom fields and the Properties studio

Add the fields your business needs to contacts, companies, deals and custom objects. Ten field types, each with the right input and validation, and no engineering ticket required.

Integrations marketplace: what is connected

Which integrations are live today, which are still rolling out, and what to do about a tool that is not in the catalogue at all.

Module management: turning features on and off

Not every workspace needs every module. Turning off what you do not use removes it from navigation and permissions, so people see a product that matches their job.

Notification preferences

Decide what you get told about and where. The goal is a small number of notifications you actually read, rather than a stream you learn to ignore.

Outbound webhooks

Have KudosCRM POST to your endpoint the instant something changes. Every payload is HMAC-signed so you can verify it is genuinely from us, and failed deliveries are retried with backoff.

Storage and data retention

Where your files and records accumulate, what gets pruned automatically, and the retention decisions worth making deliberately rather than inheriting.

Tags administration

Tags are the fastest way to label records and the easiest thing to let sprawl. Creating, merging and retiring them deliberately is what keeps them useful.

Teams and quotas

Group people into teams, set quotas against them, and read attainment alongside the forecast so the number on the board has something to be measured against.

The audit log

A read-only record of who changed what and when, with field-level before-and-after values, filters, configurable retention and CSV export.

Workspace defaults

The settings that apply to everyone — what they control, who can change them, and which ones are worth getting right before anyone starts entering data.

Connect Claude to your CRM (MCP)

Point your own Claude at your workspace over MCP and ask it about your CRM in plain language. It uses your existing API token and inherits exactly your permissions — nothing more.