Roles and terms
Who can do what in Leadmode, and what project, lead, outcome, pipeline and sales flow mean.
Roles in the organisation
In an organisation, each person has exactly one of three roles:
| Role | Who | What they can do |
|---|---|---|
| Admin | Whoever creates the organisation, and anyone an admin makes one | Everything. Only admins invite, assign roles and profiles, remove employees and delete the organisation. |
| Employee | Colleagues who have been invited | What their permission profile allows, and in projects, what their project role allows. |
| Partner | External partners and end clients | Only the projects and areas an admin shares, usually reports and metrics. |
When you promote someone with ‘Make admin’, Leadmode points out that the admin role cannot be taken back in the employee list.
Permission profiles
An employee has one profile. It determines which areas they may use (for example Finance, Telephony, Recruiting) and how far their rights in projects can reach at most. Leadmode ships with three profiles: Sales rep (default), Team lead and Viewer. You can adjust them and create your own. Details: Roles and permissions.
Project role
In addition, every employee has a role in each project they work on:
| Role | Intended for |
|---|---|
| Project lead | Steers the project, assigns leads, reviews reports |
| Sales | Works leads, makes calls, books appointments |
| Backup | Like Sales, steps in when needed |
| Read only | Can see, changes nothing |
What applies is always the lowest of profile, role and any restriction placed on that person in the project.
Terms
Project. An engagement or a campaign in which you work leads, for example for a client. A project has a team with roles, a sales flow, leads, appointments and files. See Projects.
Lead. A lead that you work on. A lead belongs to a project and sits in a stage there. See Leads.
Company and contact person. A lead can be a company that has several contact persons. Each contact person has a name, job title and their own email and phone channels. A person without a company is also possible. Stage, ownership and closing belong to the lead, not to the individual contact persons.
Outcome. In the sales flow it is also called Documentation entry. What you record after a call or an email, for example ‘Callback agreed’ or an appointment outcome. An outcome controls which stage the lead moves to, when it comes up again and what is counted in metrics and ranking.
Pipeline and stage. The pipeline (‘CRM pipelines’) shows, for a project, the stages that leads pass through, for example New, Outreach, Intro call, Qualified, Won, Lost. Within a stage there are substages such as ‘Callback’ or ‘No-show’.
Sales flow. The set of rules behind it, built as a tree: stage → substage → documentation entry → automation. It defines which stages and substages exist, which documentation entries (the outcomes) can be chosen in which substage, and what happens automatically afterwards. For each project you choose a template and adapt it if needed, by hand or with the AI. See Sales flow and Flows with AI.
Organisation. Your workspace with its own data storage. See Organisation.
Demo organisation. A copy with sample data for trying things out. See Demo organisation.