Growth and enterprise features

insideCRM includes automations, webhooks, a public API, booking pages, web forms, insights, teams, proposals, and enterprise SSO. Features are shown only when enabled for your organisation and permitted by your role.

Teams and visibility

A record can be private, team-visible, or organisation-visible. Private records are visible only to their owner; team records only to members of the assigned team. Exports, search, automations, and APIs apply the same rules. Ask an administrator if an assignment is missing.

Automations, forms, and bookings

Administrators create versioned rules and publish forms only after legal approval. Public forms require the configured consent and apply spam/rate-limit protection. Bookings are idempotent and reject a slot that is already occupied. Failed automations are audited and disabled after repeated errors.

Open Management → Web forms to start from a template, review the live preview and publish under a stable link. See Create and embed web forms for the full WordPress and iframe workflow.

Proposals and e-signatures

Open Proposals & signatures, select an active versioned template, the opportunity, and optionally a recipient. Custom placeholder values must be a JSON object. Finalizing creates an immutable PDF snapshot with an integrity hash; later template edits never alter existing proposals. Download and review the snapshot before sending it for signature.

Confirm the signer's name and email before sending. Idempotency prevents the same request from being sent twice accidentally. Statuses distinguish sent, delivered, signed, declined, voided, and failed envelopes. The signed document becomes downloadable only after the Signed status. Administrators maintain DocuSign credentials and the webhook secret in the settings tab and enable the integration only after legal approval.

Enterprise SSO

Administrators configure OIDC or SAML with allowed email domains and a default role. New users can be provisioned automatically within the licence limit. Password accounts are never silently converted into SSO accounts. For login failures, an administrator checks the domain, licence, IdP metadata, and SSO audit status.