Account and security
Maintain your account and handle company credentials without exposing secrets.
Keep personal account maintenance, company administration, and integration credentials in clear role-aware workflows.
Why it matters
Separating personal identity from company-wide controls reduces accidental operational changes and makes sensitive actions easier to understand. Agents can maintain their own access while Firm admins manage the settings and credentials shared by the company.
See it in HoneyFalcon
Personal profile and password actions remain separate in Account navigation.
Choose the security surface that matches the task
Personal account controls
Profile and password actions belong to the signed-in user. They update personal details or credentials without granting access to company-wide routing, connector, or subscription settings.
Company administration
Member roles, account and profile state, lead eligibility, intake keys, CRM connectors, company settings, and subscription actions belong to Firm-admin workflows.
Give only the access needed
Use Agent for teammates who receive and work leads. Grant Firm admin only to people who need to configure the company. Lead eligibility remains a separate operational control and should be enabled only for members who should receive offers.
Treat saved secrets as protected values
Webhook keys and CRM credentials can be entered through their dedicated flows, but HoneyFalcon does not turn the editor into a full credential store. Reusable secrets are shown in full only at the safe creation or provider-copy moment defined by the feature.
Use the focused guide for the action
Open Profile and password for your identity, Webhook keys for inbound credential lifecycle, or Data visibility and secrets for company isolation and safe support evidence.
A practical access scenario
A new sales agent needs access to offers and owned leads but should not change allocation rules or CRM credentials. The Agent role keeps daily work available, while the operations lead retains Firm-admin control over shared configuration.
This clear separation lets the team move quickly without making every user responsible for sensitive company settings.
Use the narrowest role that supports the person's real work. Lead eligibility, Firm-admin access, and buffer responsibility solve different operational needs.
Access is clear when
- Users can identify which settings affect only their account and which require firm-admin access.
- Agents can complete their work without unnecessary company-wide permissions.
- Sensitive actions use the dedicated creation, confirmation, rotation, or revocation flow for that surface.
- No reusable credential is copied into screenshots, notes, or support messages.