Security and permissions
Leadinfo runs on a JavaScript tracking snippet placed on your site, either directly or through Google Tag Manager, and account security starts with controlling who can edit that snippet's settings versus who just works the lead list. Leadinfo's account structure separates Admin users, who manage billing, install integrations, and add or remove team members, from standard Users, who typically browse leads, apply filters, and set up personal notifications without touching account-wide configuration.
Practical Details
Each connected website gets its own profile inside the account, so permissions can be scoped per brand or per domain rather than applied to the whole organization at once. Leadinfo also tracks which leads were viewed, tagged, or assigned to which team member, which matters when sales teams hand off leads between SDRs and account executives, and integration credentials for CRM and Slack connections are managed centrally so a departing employee's access can be revoked without breaking automations for everyone else.
Actionable Considerations
- Limit Admin rights to the people who actually manage billing and integrations, not everyone who works leads day to day.
- Use per-website profiles to keep lead visibility scoped to the right brand or domain.
- Revoke a departing user's access promptly, since CRM and Slack integrations are tied to the account rather than a single personal login.