Empire Teas CRM — Who Can Do What
Prepared by Altrium for Empire Teas (Pvt) Ltd Revised 19 November 2026: A-45 now says an account’s email arrives through its contacts, because an account has no email address of its own. Revised 16 November 2026: the Settings permission is described as built — one permission for each Settings page (Users, Roles, the three tag pages and Email templates), since 30 October 2026 (Rule 3, Sections 4.4, 4.6 and 5.6). The older change notes are under Change history at the end. Revised again 16 November 2026: rewritten in simpler English; no access rule changed. Status: DRAFT — every line in this document is a proposal until Empire Teas confirms it. Companion to the Product Requirements (Client Edition) and Questions for Empire Teas. This document is the full, checkable answer sheet for Q1 of that question list (“what should each of the six roles hold on day one, and who reports to whom?”), restates the plan in Q3 (below-floor quote approval), and records how Q2 (adding and removing users) and Q6 (the shared inbox) have now been decided, so everything about access lives in one place.
Why we are asking you to read this
The permission system is one of the first things we are building, because it shapes every screen in the CRM. It decides what a user sees and which buttons they can press. It also decides which records appear in their lists and search results. If we get it right the first time, nobody is blocked from their work in week one. And nobody can see or change something they shouldn’t.
You confirmed six roles with us on 3 August 2026, along with three ground rules. These are settled. We restate them here only so that the document is complete:
- The six roles: Sales Representative · Sales Manager · R&D / Sample Owner (Taster) · Tea Room (Pricing) · Administrator · Executive / Management (read-only).
- The pricing rule: representatives quote freely at or above the required gross-profit margin. A quote below the floor is held for the Managing Director’s approval. A person sets every price. The system computes the margin, and the AI never prices. (Section 5.7 says how the approval is set up.)
- The AI rule: every AI output is a draft that a person reviews and approves. The AI never sends, never approves and never decides.
What changed on 7 September 2026: you asked for roles you can configure, not fixed roles. So the system now comes with a list of everything a user could be allowed to do. An Administrator builds roles from that list. You also asked for a reporting line. With it, a manager can follow their own team’s work. The system does not treat the whole company as one pool.
What changed on 11 September 2026: we removed two layers you would otherwise have had to learn. This keeps the system simple.
- There are no role templates. The system was to come with one built-in role only, the system Administrator. (On 24 September an ordinary starting role replaced it — see below.) Your Administrator creates every other role, with our team alongside at go-live. The six roles above are our recommended first set. You can change them, or add roles, whenever the business changes.
- Each person holds one role. Someone doing two jobs gets a role built for exactly that.
- AI help is no longer a separate kind of permission either (Rule 3).
What changed on 24 September 2026: we made the permission system simpler again, and settled several points that were still open.
- No built-in roles. The system starts with one ordinary role, IT Admin, held by one named account. Your Administrator signs in with it and builds every other role (A-31).
- Each area has two permissions, View and Manage. There are also a few named permissions that stand alone. The three kinds of permission (view / edit / act) are gone (Rule 3).
- Nobody gets in unless an administrator has added them. There is no invitation email (Section 8).
- People are deactivated, never deleted. And nobody is deactivated while they still own records or have people reporting to them (A-42).
- Shares can be passed on by anyone who can manage the record. Any of them can remove a share (A-34, A-37).
- The Managing Director’s approval and the Tea Room’s publishing are the recommended set-up. They are not rules the system enforces against an administrator. Every change to who holds them is recorded (A-43).
- Every change, sign-in and sign-out is recorded (Section 7).
- The shared
info@inbox stays outside the CRM in this version. Inquiries are forwarded to a rep (A-44).
Every assumption this changes is marked Changed 24 September 2026, with what we proposed before. So you can see exactly what moved.
What changed on 27 September 2026: one more simplification. You no longer choose a reach for each permission. A person always reaches three sets of records:
- the records they own;
- the records shared with them;
- the records of everyone below them in the reporting line.
Each area that has owners has one extra tick, “all records”. It lets a role reach every record in that area, including records nobody owns (Rule 2). A role now reaches the same records for View and for Manage. Three things follow from that:
- A manager can no longer see their team’s records without being able to change them (A-6).
- A rep given all records can work every record, not only see it (A-9).
- Anyone with people reporting to them reaches those people’s records. So recording a manager is itself an access decision (Section 2).
The assumptions this changes are marked Changed 27 September 2026.
What changed on 30 September 2026: two corrections.
- Anyone who can manage a record can hand it to a new owner. That is its owner, or a colleague it was shared with whose role manages that kind of record. It is also a manager above either of them, or a role with all records. Any of them can also share the record and remove its shares (A-38). The representative’s profile said a rep “cannot reassign records they do not own”. That was wrong for a record shared with them.
- The migration now gives every imported lead one named owner. So no lead in this version is left without an owner. The rule for leads without an owner stays as a safeguard (A-7).
The assumptions this changes are marked Changed 30 September 2026.
What changed on 2 October 2026: one clarification about sharing. Sometimes a record is shared with someone who is later deactivated. The share stays on the record. But it gives nobody access while that person is deactivated. So their manager does not keep reaching the record through it (Section 2, sharing, “Where you see it”).
So this document now asks a different question. It no longer asks you to fix each role forever. It asks: what should each of the six recommended roles hold on day one, and who reports to whom? If those two things are right, the system is useful from the first morning. Your own Administrator can still change everything here afterwards. This document is our proposed answer, assumption by assumption, for you to confirm or correct. We based it on the prototype you approved, the product requirements, and how we understand your teams to work. Where we were unsure, we chose the safer, narrower default.
Correcting anything here is cheap, and cheaper now than before. Almost every line below is a setting your Administrator can change in the role editor. A few lines are fixed rules of the system, and they say so:
- nobody reads another person’s mailbox;
- at least one person can always administer users and roles;
- nobody is deactivated while they still own records.
What is still expensive is finding out in testing that the starting point was wrong all along. Training, testing and the first weeks of use all assume it. That is why we wrote this document.
How to review it
-
Every section ends with numbered assumptions — A-1, A-2, … — each with a tick box.
-
Reply in whatever way is easiest for you:
- tick and return this document;
- send a one-line email for each correction (“A-20 — managers should also be able to do this”);
- go through it with us on a call.
-
If we do not hear otherwise, we go ahead with the defaults written here. You can still change them afterwards. We ask now so that you are confident, not to lock anything in.
-
The last page has a sign-off block. It also asks you for three things:
- a table of who at Empire Teas starts on each role;
- the reporting line (who reports to whom);
- the email address of the administrator account on the live system.
Filling those in is as valuable to us as the sign-off itself.
1. How access control works — five plain rules
Rule 1 — your role decides what you can see and do, and roles are yours to shape. Every user holds one role, which an Administrator gives them. A role is a named list of permissions. The permissions come from everything the system can do, grouped by area: leads, accounts, the standards book, deals, quotes and samples. Each area has a permission to view it and a permission to manage it. There is also a short list of named permissions that stand alone (Rule 3).
We kept the list deliberately coarse (simplified 13 September 2026, and again on 24 September). So the role editor is a list you can read and check. It is not a grid of hundreds of ticks, where one wrong tick is found only after go-live.
There are no built-in roles. The system starts with one ordinary role, IT Admin, held by one named account. Your Administrator creates the rest. The six roles confirmed on 3 August are our recommended first set. Sometimes two people with the same title need different access, or one person does two jobs. Then an Administrator makes a role that holds exactly the permissions that person needs. Nothing comes back to us.
Rule 2 — ownership and the reporting line decide which records. Leads, accounts, deals, quotes and samples each have one owner. The contacts, notes, tasks, files and emails on a record follow that record. Changed 27 September 2026: you do not choose a reach for each permission. A permission on one of those areas always reaches:
- the records the person owns, or that have been shared with them; and
- the same records for everyone below them in the reporting line, all the way down. So a manager reaches their team’s records, with nothing extra to set.
Each area has one extra tick, “all records”. It widens the role’s View or Manage on that area to every record, including records nobody owns.
So a Sales Representative’s role and a Sales Manager’s role can hold exactly the same permissions. The representative has nobody below them, so they reach their own records. The manager reaches their team’s records as well. An Administrator’s role and an Executive’s role tick all records. Whoever sees a record can do on it what their role allows. View reads the record, and Manage works it. So a role reaches the same records for both. No permission ever opens another person’s mailbox. This is a fixed rule, not a setting. Previously proposed: each permission had one of three reaches — own, team or everyone’s — chosen for each permission.
Anyone who may manage a record can hand it to a new owner. For example, they might do this when someone is on leave or leaves the company. The new owner must be an active user whose role can view that kind of record. Section 2 covers the reporting line and sharing.
Rule 3 — each area has View and Manage, plus a few named permissions. Changed 24 September 2026: this replaces the three kinds of permission (View / Edit / Act) we proposed on 11 September.
| Permission | What it grants |
|---|---|
| View (one per area) | See that area’s records and screens, within the person’s reach (Rule 2) |
| Manage (one per area) | View, plus every action in that area (note 1 below) |
| All records (one per area that has owners) | Widens the role’s View or Manage on that area to every record, including records nobody owns (note 2 below) |
| Named permissions (stand alone, no reach) | Publish the weekly prices · Use the capture app · Approve a below-floor quote · Settings · Your own mailbox (notes 3 and 4 below) |
Notes on this table:
-
Manage covers create, edit, archive and restore. It covers sharing and removing a share, and handing a record to a new owner. It covers asking the AI for a draft. It also covers that area’s own steps: submitting a quote, moving a deal between stages, and generating the ERP handoff.
-
All records is offered for leads and accounts, and in the second phase for deals, quotes and samples. It widens the reach from the person’s own and team’s records to every record, including records nobody owns. The role editor offers it only once View or Manage is ticked for the area.
-
The named permissions are:
- Publish the weekly prices.
- Use the capture app — full use of the trade-show capture app. Putting a captured lead into the CRM also needs Manage on leads (added 12 November 2026).
- Approve a below-floor quote. It arrives with quotes, in the second phase.
- Settings — see note 4.
- Your own mailbox — connected automatically when you sign in. You can read it, send from it, and link its emails to records. It is only ever your own.
-
Settings is one permission for each page under Settings (changed 30 October 2026). From 26 October it was one permission, “Manage settings, users and roles”. The role editor shows one Settings row with the pages under it. Ticking the row ticks all the pages. The pages are:
- Users — adding people, giving each their role, the reporting line, deactivating and reactivating, and offboarding;
- Roles — building and changing roles;
- Account tags, Contact tags, Lead tags and Email templates.
A later Settings page adds its own permission. Examples are reference data, imports, AI feature switches, and in the second phase pipelines and custom fields. In this document, System settings means all these Settings permissions together, as the IT Admin and Administrator roles hold them. Whoever holds Users or Roles can reach every page, because they can give themselves any permission. The role editor says so.
The areas are:
- Leads;
- Accounts, with their contacts, notes, tasks, files and timeline, and that customer’s standards with the final price;
- the standards book — every buying standard with its costs, margin floor, full price working and published prices;
- in the second phase, Deals (with product briefs, export documents and the ERP handoff), Quotes and Samples.
Anyone who can see the standards book sees the costs and margins in it. We propose, for you to confirm, that an account page shows that customer’s standards with only the final price (A-10, A-39).
There is no separate permission for dashboards, search, tasks or exports. Each one shows only what the person’s area permissions reach. Every export is recorded. Reading the dropdown lists (reference data) needs no permission.
Where the AI fits. AI help is not a separate permission. It comes in two kinds.
- AI that runs by itself in the background — scoring and triaging inquiries, extracting details from an email, preparing the morning read. Whoever may view the record sees the result. Your Administrator switches each of these features on or off for the whole system, under System settings.
- AI help a person asks for — draft this reply, brief me on this account before a meeting, check this quote. It comes with the permission it assists. For example, an account briefing comes with managing accounts (21 October 2026). Whoever may manage a record may ask for a draft on it. Drafting an email comes with your own mailbox.
The AI itself holds no permission at all. An AI draft always waits for a person whose role allows the action. No AI output can reach a buyer, a price or the ERP unless a person presses the button. No role you build can change that.
Rule 4 — special approvals are named permissions, not job titles. The below-floor quote approval is one named permission. By default, only the Managing Director’s role holds it. Handing it to a stand-in during leave is a settings change. Nothing needs to be rebuilt. Section 5.7 covers the arrangement. It explains that this is a default your Administrator could change, and that every such change is recorded.
Rule 5 — what you cannot use is either hidden or greyed out, with a reason.
- If a user’s role holds no permission for an action at all, the control is hidden. For example, an Executive’s role holds no permission to edit a deal. Read-only users get clean screens, not a wall of grey buttons.
- If the block depends on the situation, the control is greyed out with a plain-language reason. For example, the quote is missing a checklist item, or the deal belongs to someone outside their team. A reason reads like this: “This quote is below the margin floor and needs approval from someone who holds the below-floor approval permission.”
Nobody is left guessing why a button doesn’t work.
Under all five rules: every change is recorded. The record shows who did it, to what, and when. Every sign-in, sign-out and export is recorded too. Viewing is not recorded. One audit trail holds stage moves, price publications, quote approvals and configuration changes. It also holds role and permission changes, shares, reassignments and every AI approval. Oversight never depends on memory. There is no audit screen in this version. The trail is kept in the database, and we answer audit questions from it on request (Section 7).
An effective-permissions view answers “why can this person see this?”. Whoever holds user and role administration can use it. It shows:
- the person’s one role;
- the permissions that role grants;
- for each area, whether they reach every record, or their own and their team’s — naming the people below them.
Assumptions to confirm:
- [ ] A-1 — Changed 24 September 2026: Your Administrator can configure roles. The system starts with one ordinary role, IT Admin, held by one named account (A-31). Your Administrator signs in with it. They create the six roles below, with us alongside at go-live, set exactly as Sections 4 and 5 describe. Previously proposed: the system came with a built-in system Administrator role.
- [ ] A-2 — Each person holds one role. Someone doing two jobs (for example Tea Room and Sales Manager) gets a role built to hold both sets of permissions. Your Administrator creates it.
- [ ] A-3 — Controls are hidden or greyed out as Rule 5 describes. Read-only roles get clean screens, not disabled buttons everywhere.
2. The reporting line and sharing — who sees whose work
Each user’s account can record their manager. The chain of managers is the reporting line. In this document, team means that chain: a manager’s team is everyone below them in it. Changed 27 September 2026: every permission reaches down the reporting line (Rule 2). So recording someone’s manager is itself an access decision. It lets that manager see the person’s records, in every area where the manager’s role can see records. At go-live your Administrator enters the reporting line from the list you give us (Section 9), with our team alongside. After that, your Administrator keeps it up to date when someone joins, moves or leaves.
Having a reporting line raises four questions. Here is the answer we will build to for each one.
How far down does “team” reach? Settled 24 September 2026: all the way down the chain, not only direct reports. Suppose a Director’s team includes a Sales Manager. Then the Director also sees the records of that Manager’s representatives. “Team” also includes records shared with anyone in the team.
May a manager edit their team’s records, or only see them? Changed 27 September 2026: a manager can do on their team’s records exactly what their role allows on their own.
- With Manage on an area, they edit and reassign their team’s leads, deals, accounts and tasks. They also review their team’s AI drafts. This is the unblocking work managers do today. Manage is our default for Sales Managers.
- With only View on an area, they read their team’s records and their own, but change neither.
No manager can ever open a team member’s personal mailbox. No permission opens another person’s mailbox. Previously proposed: an alternative in which managers see their team’s records but edit only their own. We withdrew it, because it needed a separate reach for viewing and for managing.
Who sees records nobody owns? Changed 30 September 2026: in this version every lead has an owner.
- Inquiries to
info@are forwarded to a rep, who creates the lead (Section 7). - A lead from the trade-show app reaches the CRM only when someone converts it. Whoever converted it owns it (changed 12 November 2026; before that, whoever captured it owned it).
- The migration gives every imported lead to one named person, who hands them on. (Previously: a migrated lead whose Pipedrive owner had no CRM account would have had no owner.)
The rule for a lead without an owner stays as a safeguard. Changed 24 September 2026: such leads are visible only to roles with all records ticked for leads. Those roles see them through an Unassigned filter on the lead list, until someone is given ownership. A manager who sees only their team does not see them. Previously proposed: every manager and Administrator saw them too, in an Unassigned list at the top of the lead triage queue.
What happens when a manager leaves? The CRM refuses to deactivate a person who still has people reporting to them, until those people have a new manager. The same applies while the person still owns records (A-42). Changed 24 September 2026: we withdrew the alternative of moving the team automatically to the manager above. It could silently widen what that manager can see.
Assumptions to confirm:
- [ ] A-4 — You will give us the reporting line (who reports to whom) with the sign-off. Your Administrator enters it at go-live, with us alongside. They keep it up to date afterwards.
- [ ] A-5 — Changed 24 September 2026: “Team” reaches all the way down the chain. It includes records shared with anyone in it. Previously proposed: an alternative of direct reports only. We withdrew it, and the system does not offer a one-level team.
- [ ] A-6 — Changed 27 September 2026: Managers can edit and reassign their team’s records, and review their team’s AI drafts. A manager’s role works their team’s records exactly as it works their own. Nobody ever opens another person’s mailbox. Previously proposed: an alternative in which managers view their team’s records but only the owner edits. We withdrew it.
- [ ] A-7 — Changed 24 September 2026: Leads nobody owns are visible only to roles with all records ticked for leads. By default those are the Administrator and the Executive. They see such leads through an Unassigned filter on the lead list, until someone is given ownership. Changed 30 September 2026: no lead in this version is left without an owner. The migration gives each imported lead to one named person. So this rule is a safeguard, not an everyday case. Previously proposed: visible to managers and Administrators, and listed as Unassigned at the top of the triage queue.
- [ ] A-8 — Changed 24 September 2026: The CRM refuses to deactivate a manager until their reports have a new manager. Previously proposed: an alternative in which the team moves automatically to the manager above. We withdrew it.
Sharing a record with a colleague
Added 16 September 2026, from your 9 September request: “the owner can share a lead or deal with a colleague, and that colleague then sees everything on it.” Revised 24 September 2026.
The reporting line handles up and down: a manager sees their team’s work. Sharing handles sideways. You can share a lead, account, deal or quote with a named colleague. This lets them see that one record. For example:
- a rep in one region shares an inquiry with the rep who covers another region;
- a rep brings a taster onto a specific deal.
A manager never needs a record shared with them. They already see their team’s records through Rule 2.
The colleague’s own role decides what they can then do, not the share. When you share, there is no “view or edit” choice. You put the record within their reach, and their role decides the rest. Someone whose role only views deals will view the deal. Someone whose role manages deals can work it. This is deliberate. What a person may do stays a property of the role your Administrator built. A colleague never hands it out record by record. This also covers the common case of a colleague standing in during leave, with nothing extra to set up.
What a share includes. The record and everything on it: notes, tasks, samples, quotes, files, and the emails linked to that record. The colleague sees these exactly as a manager already sees them. A share never opens anyone’s mailbox (Section 7). So sharing a deal shows that deal’s conversation and nothing else from anyone’s inbox.
Who can share and remove a share. Changed 24 September 2026: anyone who can manage the record can share it on. That means:
- its owner;
- a manager above the owner;
- a colleague it has been shared with, whose role manages that kind of record.
Any of them can remove any share. A colleague whose role only views that kind of record sees it, but cannot share it. Every share and every removal is recorded, with who did it and when. So you can always trace where someone’s access came from. If the record later gets a new owner, the shares stay with the record. Previously proposed: only the owner or a manager above could share. A colleague who had been shared a record could not pass it on. Only the owner, whoever created the share, or a manager above could remove a share.
Who can be picked. The share list offers only active colleagues whose role can see that kind of record, and who do not already see this one.
- People who already see the record are not listed — as its owner, through the reporting line, or through an earlier share. The record’s “shared with” list shows the existing shares, each with Remove.
- People whose role cannot see that kind of record are not listed either, because a share would give them nothing.
So a rep can bring the Tea Room onto a specific deal only if the Tea Room’s role can view deals (A-21).
Where you see it. The record itself shows its shares, for example “Shared with Nuwan, Priya — by Kasun, 12 September”. So it is always visible who has been brought in, and by whom. Sometimes a person a record was shared with is later deactivated. The share then stays on the record, marked as deactivated, and it can be removed. Changed 2 October 2026: while that person is deactivated, the share gives nobody access — not them, and not their manager. It works again if they are reactivated.
Assumptions to confirm:
- [ ] A-34 — Changed 24 September 2026: Anyone who can manage a lead, account, deal or quote can share it with a named colleague. This includes a colleague it was shared with. That colleague can share it on if their role manages that kind of record. Previously proposed: only the owner (or a manager above them) could share, and the colleague could not pass it on.
- [ ] A-35 — A share has no separate “view or edit” setting. The colleague can do whatever their own role allows.
- [ ] A-36 — A share covers the record and everything attached to it, including the emails linked to that record. It never covers a personal mailbox.
- [ ] A-37 — Changed 24 September 2026: Shares stay with the record when its owner changes. Anyone who can manage the record can remove any share. Previously proposed: only the owner, whoever created the share, or a manager above could remove it.
3. The six recommended roles at a glance
| Role | Built for | In one line |
|---|---|---|
| Sales Representative | The reps who run buyer relationships day to day | Works their own leads, accounts, deals, quotes, sample requests, tasks and email. Uses AI drafts. Quotes freely at or above the margin floor |
| Sales Manager | Sales leadership | Everything a rep can do, across their team’s records. Also reassigns owners, sees team dashboards, and oversees quotes and AI output |
| R&D / Sample Owner (Taster) | The tasting and blending team | Runs the sample workflow end to end (prepare → dispatch → deliver → feedback → outcome). Reads the briefs and deal context shared with them. Does not touch pricing or quotes |
| Tea Room (Pricing) | The weekly bulk-pricing team | Owns the standards book (standards, costs, the margin floor) and the weekly price publish. By default sees only the pricing screens |
| Administrator | The one or two people who run the system | Full data access plus all configuration: users, roles and the reporting line, pipelines, custom fields, reference data, templates, AI settings, imports |
| Executive / Management | Directors and management oversight | Sees everything, changes nothing: dashboards, pipelines, forecasts, quotes, accounts, reports |
The Managing Director has a role of their own. It gives the Executive’s read-only view of everything. It adds the one permission that, by default, nobody else holds: approving a below-floor quote (Rule 4). Throughout Section 4, read the Executive column for the MD, with that single addition. Section 5.7 explains it in full.
IT Admin is the role the system starts with, before any of the six exist. It holds every Settings permission (Users, Roles, the three tag pages and Email templates) and nothing else. One named account holds it (A-31). It is an ordinary role. Your Administrator can edit it, keep it, or delete it once nobody holds it.
These roles are starting points. Your Administrator creates them with us at go-live. They can add more roles at any time, such as “Senior Representative”, “Regional Director” or “Export Coordinator”. Each role holds exactly the permissions it needs. There is no template layer to maintain: what a role holds is what its people can do.
4. The starting access map
How to read the tables:
| Mark | Meaning |
|---|---|
| Manage | View, create, edit, archive and every other action in that area ⁷ |
| View | Read only |
| (own) | Records they own, or that are shared with them. A role without all records reaches these for someone with nobody below them |
| (team) | The same, for them and everyone below them in the reporting line. The same role reaches these for a manager (Section 2) |
| (all) | The role ticks all records for that area: everyone’s records, including records nobody owns |
| — | No permission (hidden) |
Named permissions are written out in words. Nothing is deleted in this version. Records are archived instead. Archiving keeps their history and can be undone. Archiving is part of Manage.
4.1 Sales records
| Sales Rep | Sales Manager | R&D / Taster | Tea Room | Executive | Administrator | |
|---|---|---|---|---|---|---|
| Leads (triage queue) | Manage (own) — work the queue: approve and send reply, convert to deal, archive, share, hand over | Manage (team) — including reassigning within the team | View (own) ⁸ | — | View (all) — including the Unassigned filter | Manage (all) — including the Unassigned filter · triage rules under System settings |
| Accounts (organisations), with their contacts, notes, tasks, files and timeline | Manage (own) — including archiving, sharing and handing over their own accounts ⁷ | Manage (team) ⁷ | View (own) ⁸ | — ¹ | View (all) | Manage (all) ⁷ |
| Deals & pipeline boards | Manage (own) — including moving their own deals between stages | Manage (team) — including moving and reassigning any of the team’s deals | View (own) ⁸ | — | View (all) | Manage (all) |
| Activities (tasks & calendar) | Follow the record they belong to. Whoever may manage a lead, account, deal or sample may add, assign and complete its tasks. Whoever may view it sees them |
¹ Buying standards belong to particular clients. So the Tea Room’s pricing screens must show client names against each standard. They do not show the account screens themselves. See 5.4.
⁷ Records are archived, never deleted. This covers leads, accounts, contacts, deals, quotes, samples and product briefs. Manage covers create, edit and archive (and restore). An archived record disappears from the everyday lists. But it keeps every note, email, sample and quote that refers to it, and it can be brought back. Archiving loses nothing, so a rep can archive their own records too. A permanent delete is not in this version. If you need one, we would plan it as a change. Manage also covers handing a record to a colleague. A rep can hand a lead, account or deal they own to someone better placed to serve that buyer. A manager can reassign any record in their team. Giving a colleague access without handing the record over is sharing (Section 2).
⁸ R&D see a lead, account or deal when a colleague shares it with them. Their role holds View without all records. So a taster with nobody below them reaches only the records they own or that are shared with them. This replaces “linked to their samples”, which the permission system cannot express. The system reaches records only through ownership, the reporting line and sharing. See A-40.
4.2 Tea workflows
| Sales Rep | Sales Manager | R&D / Taster | Tea Room | Executive | Administrator | |
|---|---|---|---|---|---|---|
| Samples (multi-round tracker) | Manage (own) — request a sample on their deals and follow it | Manage (team) | Manage (all) — work every sample: prepare, dispatch (courier + tracking), deliver, log feedback, record outcome · send the AI feedback-chase email from their own mailbox ⁴ | — | View (all) | Manage (all) |
| Product briefs (private label) — part of the deal | Manage (own deals) | Manage (team) | View (own) ⁸ — their comments go on the sample, which they manage | — | View (all) | Manage (all) |
| Certification-mismatch check — part of the deal | View (their deals) | View (team) | View (own) ⁸ | — | View (all) | View (all) + maintain the certification list (System settings) |
| Export-document checklist — part of the deal | View + tick items assembled (their deals) | View + tick (team) | View (own) ⁸ | — | View (all) | Manage (all) + configure the document rules (System settings) |
4.3 Standards, pricing and quotes
| Sales Rep | Sales Manager | R&D / Taster | Tea Room | Executive | Administrator | |
|---|---|---|---|---|---|---|
| The standards book ¹⁰ — every buying standard, with its costs, margin floor, full price working and published prices | — ⁹ | — ⁹ | — | Manage — create, edit and archive standards; set costs and the margin floor; import the weekly price workbook | View | View ² |
| A customer’s standards on their account page — with the final price only | View (own) — comes with Accounts; attach to their deals; fills in their bulk quotes automatically | View (team) | View (own) ⁸ | — | View (all) | View (all) |
| Publish the weekly prices (a named permission) | — | — | — | Yes — publish each week; manual override between auctions (recorded) | — | — ² |
| Quotes | Manage (own), including submitting once the 8-item checklist passes and the margin is at or above the floor. They see only pass or fail against the floor | Manage (team) — oversight of the team’s quotes | — | — ³ | View (all, including margins) | Manage (all) |
| Approve a below-floor quote (a named permission) | — | — | — | — | The Managing Director’s role only (5.7) | — by default ² |
² By default, the Tea Room publishes and the Managing Director approves below-floor quotes. Administrators hold neither permission. You may want an Administrator as a fallback publisher, for leave cover. That is one settings change: say so on A-22. Administrators view the standards book but do not manage it. So by default the Tea Room alone sets the floor (A-23). These are defaults, not rules the system enforces. Whoever holds user and role administration can give any permission to any role, their own included. Every such change is recorded (5.6, 5.7).
³ This is the default from Q1: the Tea Room sees only the pricing screens. The alternative is read-only sight of quotes, deals and accounts for context. It is one tick away: A-21.
⁹ Reps and managers do not hold the standards book. It carries costs and margins, and a role sees it whole or not at all. Instead they see each of their accounts’ standards, with the final price, on the account page. A bulk quote fills in from it automatically (A-10, A-39).
¹⁰ The standards book is the one sellable record, for bulk and private label alike. Each standard has its names, grades, origins, brand and held certifications. There is no separate products catalogue (decided 15 September 2026). Every past price is kept on record. There is no separate price-history screen (11 October 2026).
4.4 Email, sequences and AI assistance
| Sales Rep | Sales Manager | R&D / Taster | Tea Room | Executive | Administrator | |
|---|---|---|---|---|---|---|
| Your own mailbox (a named permission) ¹¹ | Yes | Yes | Yes ⁴ | — | — | — (add it if your Administrators also write to buyers) |
| Mail linked to a record — shows on the record to anyone who can view that record | Their own records | Their team’s records — never a team member’s mailbox | Records shared with them ⁸ | — | Every record ⁵ | Every record · the company-wide email block list (System settings) — never a personal mailbox |
| Email templates | Use the shared library when writing an email. Writing templates, including one’s own, needs the Email templates permission under Settings (changed 26 October 2026) | Same | Same | — | — | Same + look after the shared library and keep their own (the Email templates permission) |
| Outreach sequences (multi-step cadences) — a sequence runs on a lead or deal, so it follows that record’s permission | Enrol their own leads and deals. A person approves every AI-drafted step before it sends | Enrol across the team | View (own) ⁸ | — | View (all) | Manage (all) + shared sequences (System settings) |
| AI assistance — background scoring, extraction and briefings show to whoever may view the record. Asked-for drafts come with the permission they assist (Rule 3) | Ask for drafts on their own records. Approve and send their own | Same, across the team | Drafts on the samples they work (the feedback chase) | — | Sees the AI summaries the system produced. Asks for nothing (read-only) | Same as a manager, everywhere + AI settings (System settings: per-feature on/off, model choice, monthly spend ceiling) |
⁴ The R&D team’s one outward action is the sample feedback-chase email. The AI drafts it for overdue samples, and the taster sends it from their own mailbox. The mailbox permission is the same for every role. So it also lets them send other email from their own mailbox inside the CRM, as they can in Outlook today (A-19). If chases should go through the deal’s sales rep instead, say so on A-19.
⁵ “Read-only across everything” (Q1’s default) includes the communication history shown on accounts and deals. Personal inboxes stay private, exactly as in Pipedrive. No permission opens another person’s mailbox. So what others see is the mail linked to records they can reach, never each other’s inboxes. The shared info@ address stays outside the CRM in this version (Section 7).
¹¹ Your own mailbox is your own Microsoft 365 mailbox, connected when you sign in. With it you read, write, reply and send, from records and from the in-CRM inbox. It is only ever your own.
4.5 Visibility, search and data
| Sales Rep | Sales Manager | R&D / Taster | Tea Room | Executive | Administrator | |
|---|---|---|---|---|---|---|
| Dashboard, KPIs & forecast | No separate permission. Every tile shows only records within that person’s reach. A rep sees their own book, a manager their team, R&D their samples, an Executive the whole company | |||||
| AI morning briefing & “what’s stuck” | Their own book | Their team | Their samples | — | Company-wide (read) | Company-wide |
| List views & saved filters | On every screen they can see: save their own views, share them with everyone who can see that screen, use views others share | Same | Same (their screens) | Same (pricing screens) | Same (their screens) | Same + remove a shared view left by someone who has left |
| Bulk actions on a selection | Own records: edit a field, add a task, enrol in a sequence, hand over, export | Team records, including reassigning the owner and archiving | — | — | — | All |
| Export a list to Excel/CSV | No separate permission. Anyone can export a list they can see, and every export is recorded ⁶ | |||||
| Import spreadsheets | — | — (A-15) | — | — | — | Import + configure mappings (System settings) |
| One-time Pipedrive migration | — | — | — | — | — | Runs it (with our team) |
| File attachments | Follow the record they are on. Add and manage files on records they manage. View and download files on records they can view | |||||
| ERP handoff document (on a won deal) | Generate (their won deals — part of Manage on deals) | Generate (team) | — | — | View | Generate + configure the template (System settings) |
| Effective-permissions view (“why can this person see this?”) | — | — | — | — | — | Everyone’s (System settings) |
⁶ Changed 24 September 2026: export follows View. Anyone can take a list they can see into Excel, including Executives and R&D. Every export is recorded. See A-27.
4.6 Administration
| Sales Rep | Sales Manager | R&D / Taster | Tea Room | Executive | Administrator | |
|---|---|---|---|---|---|---|
| Users (add a person with their one role, set who they report to, deactivate and reactivate — never delete) | — | — | — | — | — | Users (a page under Settings, with its own permission) |
| Roles (create, rename, choose permissions, delete one nobody holds) | — | — | — | — | — | Roles — the role editor, a page under Settings, with its own permission |
| Colleague list (names and roles only, for choosing who to share with, hand a record to, or report to) | Everyone who can sign in | |||||
| Pipeline & stage configuration (stages, win %, idle-deal thresholds) | View the board structure | View | View | — | View | System settings |
| Custom fields (add fields to any record type) | Use them | Use | Use | Use | View | Define (System settings) |
| Reference data (certification list, export-document rules, packaging/Incoterm/grade dropdowns, activity types) | Use | Use | Use | Use | View | Maintain (System settings). The account dropdowns (customer type, region, packaging, Incoterms) are the exception. In this version we fix them, and change them with a small update on request |
| AI settings (per-feature on/off, model, spend ceiling) | — | — | — | — | — | System settings |
| Audit trail | No audit screen in this version. Every change, sign-in, sign-out and export is recorded. History that is part of a record shows on the record to anyone who can view it, such as the account timeline or who approved a quote. A standard’s price history shows in the Tea Room’s weekly round. We answer anything else from the stored trail on request |
4.7 The trade-show capture app
The capture app is a companion mobile app for exhibition floors. Someone at the fair photographs a card or scans a badge, and can add a note. The app then reads, researches and scores the lead. It notifies the sales team inside the app, and sends no email (updated 12 November 2026). Updated 12 November 2026: a captured lead then waits in the app until someone reviews it. Converting it puts it in the CRM’s leads. Rejecting it keeps it in the app only.
| Who | What | |
|---|---|---|
| Use the app (capture, notes, see captures, review them, plan a show) | Anyone whose role has the capture app’s own permission, Use the capture app (changed 12 November 2026). Sales Reps and Sales Managers hold it by default (A-41) | They sign in with their normal CRM account. Without the permission, the app says so and offers only sign-out |
| Captured leads | Wait in the app for someone to review them. Convert puts the lead in the CRM’s leads ¹². Reject keeps it in the app only ¹² (changed 12 November 2026) | Once converted, the same triage rules and ownership as Section 4.1 |
| Notifications | Shown inside the app to the person using it, for the leads they work on. The app sends no email (updated 12 November 2026) | |
| Configuration | System settings (the Administrator) |
¹² Converting also needs Manage on leads (added 12 November 2026). The converted lead is tagged with the trade-fair source and owned by whoever converted it. The rep who captured it is shown as captured by. Rejecting takes an optional reason and note. A rejected lead can be moved back for review.
- [ ] A-41 — Changed 12 November 2026: using the capture app has its own permission, Use the capture app. It gives full use of the app, and can be added to any role. Sales Reps and Sales Managers hold it by default. A lead reaches the CRM only when someone converts it. So capturing no longer creates a CRM lead on its own. Converting also needs Manage on leads, because the converted lead becomes theirs. Previously proposed (24 September 2026): using the capture app came with Manage on leads (without all records). That was because every capture created a lead owned by the person who captured it. Someone attending a fair needed a role that could manage leads. Before that (until 24 September 2026): a separate capture permission that could be added to any role.
5. Role by role — what, and why
5.1 Sales Representative
Can:
- manage their own leads, accounts (with their contacts, notes, tasks and files), deals and quotes
- move their deals along the pipeline
- request samples, fill in product briefs, and tick off export documents
- send and receive email from their own mailbox, from records and the in-CRM inbox, with templates
- enrol their own leads and deals in sequences
- use every AI assist on their own records, and approve and send their own AI drafts
- submit quotes that pass the checklist at or above the margin floor, without waiting for anyone
- generate the ERP handoff for their own won deals
- share their own records with a colleague, and hand a record they own to a colleague. They can do the same for a record a colleague has shared with them.
- search, filter, save views and export within their own book
Cannot:
- see the standards book (its costs, floor and price working). They see their accounts’ final prices on the account page.
- publish prices
- approve a below-floor quote. Their below-floor quotes go into a held state, with a clear reason.
- hand over, share or remove a share on a record outside their reach — one they neither own nor have had shared with them. (changed 30 September 2026: this line said “reassign records they do not own”. That was wrong for a record shared with them — A-38.)
- import spreadsheets
- configure pipelines, fields, reference data, users, roles or AI
Why this shape: reps work in the system all day. Anything that makes them wait costs response time — quote approvals above the floor, AI drafts, sample requests. Response time is the number-one measure this CRM exists to improve. So the role gives a rep full speed inside their own book. It draws the line exactly where money, compliance or someone else’s records begin. Nothing is deleted in this version. Records are archived, which keeps their history and can be undone. So a rep can archive their own records without risk.
Assumptions:
- [ ] A-9 — Reps see only their own records by default, not the team’s. If your reps work as one pool and should all see everything, tell us. It is one setting on the role (all records for that area). Changed 27 September 2026: with that setting a rep can also work every record, not only see it. This is because a role reaches the same records for View and Manage.
- [ ] A-10 — Changed 24 September 2026: Reps see each of their accounts’ standards with the final price on the account page. Their bulk quotes take their price from it automatically. Reps also see the computed margin % on their own quotes, which they need to know the quote passes the floor. They do not see the standards book, which carries the costs and the floor. Previously proposed: reps viewed the whole standards book without its costs. Now a role sees the book whole, costs included, or not at all.
- [ ] A-11 — A rep’s at-or-above-floor quote goes out without any approval step. (Confirmed 3 August. We restate it because the approved prototype still showed the older flow, where a manager approves every quote. The build follows this rule, not the prototype.)
- [ ] A-12 — Changed 24 September 2026: Nobody deletes records in this version. Records are archived and can be restored. Archiving is part of Manage, so a rep archives their own leads, accounts, contacts and deals. Previously proposed: reps could archive but not delete, while managers and Administrators could delete. There is now no delete to hold back.
- [ ] A-38 — Changed 24 September 2026: A rep can hand a lead, account or deal they own to a colleague. Handing over is part of Manage. A manager can reassign any of these in their team. The new owner must be an active user whose role can view that kind of record. Changed 30 September 2026: anyone who can manage the record can hand it over. That is its owner, or a colleague it was shared with whose role manages that kind of record. It is also a manager above either of them, or a role with all records. This matches exactly who can share the record and remove its shares (A-34, A-37). The shares stay with the record when its owner changes. So a colleague who hands over a record shared with them still sees it. Previously proposed (earlier on 24 September): accounts only.
5.2 Sales Manager
Can: everything a rep can, across their team’s records:
- edit, move and archive any of the team’s leads, accounts, contacts, deals and tasks (archived records keep their history)
- reassign owners within the team (for leavers, leave cover, and balancing the load)
- see every quote of the team’s, with its margin
- oversee and approve the team’s AI drafts
- enrol the team’s records in sequences
- see team dashboards, the team forecast, and mail linked to the team’s records
- export the team’s data
Cannot:
- open a team member’s mailbox (no permission can)
- see the standards book — the costs and the floor figure (A-39)
- publish weekly prices or edit standards (that is the Tea Room’s work)
- approve below-floor quotes (by default only the Managing Director does — 5.7)
- import spreadsheets, or change anything under System settings, users and roles included (A-15)
- see leads nobody owns (A-7)
Why this shape: the manager’s job in the system is oversight and unblocking. They reassign the dormant account, rescue the stuck deal, and review what the AI is sending out. So their reach is “the team”, following the reporting line you give us. If Empire runs sales as one team under one manager, “team” and “everyone” are nearly the same. If there are several managers or a regional structure, each sees their own people by default. Two boundaries, money and configuration, stay outside this role on purpose. Pricing authority lives with the Tea Room and the MD arrangement. System configuration lives with Administrators, so pipeline set-up does not change informally.
Assumptions:
- [ ] A-13 — Managers see and work their team’s records (following the reporting line). This includes quotes with margins, and mail linked to records. Alternative: every Sales Manager sees the whole sales organisation, whatever the reporting line. That is one setting on the role (all records).
- [ ] A-14 — Managers do not hold the below-floor approval (5.7). While the Managing Director is away, cover comes from naming a deputy for a period (A-32), not from widening the permission.
- [ ] A-15 — Changed 24 September 2026: Importing spreadsheets sits under System settings, together with reference data, shared templates and AI settings. So the recommended Sales Manager role does not import or edit shared templates. An Administrator imports for them. Alternative: give the Sales Manager role System settings, which brings all of those with it. Since 26 October 2026 it also brings user and role administration. Previously proposed: managers import and edit the team’s templates, and reps do not.
- [ ] A-39 — Changed 24 September 2026: Managers see whether each quote passes the floor, and each account’s final prices. They do not see the floor figure itself. The floor sits in the standards book, which also carries costs. A role sees the book whole or not at all. Alternative: give the Sales Manager role View on the standards book — costs, margins and the floor together. Previously proposed: managers viewed the floor but not the costs.
5.3 R&D / Sample Owner (Taster)
Can:
- see every sample across the company, and work its whole lifecycle. They mark it prepared, dispatch it with courier and tracking, and mark it delivered. They log buyer feedback and record the outcome (approve / revision / reject). A rejection automatically opens the next round.
- read the leads, accounts and deals a colleague shares with them. This includes the product brief, the deal context and the mail linked to those records (A-40).
- add their comments on the sample
- attach files (tasting notes, spec sheets) to samples
- keep tasks on samples
- send the AI-drafted feedback-chase email from their own mailbox, when a buyer has gone quiet on a sample
- export a list they can see (every export is recorded)
Cannot: create or edit deals, accounts or quotes; see the standards book, quotes or margins; import; or configure anything.
Why this shape: moving a sample forward is R&D’s job, so they hold the buttons that move it on. Sample progress automatically moves the linked deal’s stage. So this is the one place where a non-sales role moves the sales pipeline, by design. Everything else is read-only context. A taster needs to know what the buyer asked for (brief, deal, feedback history). They do not need to edit the commercial record. Costs and margins are deliberately hidden here. Tasters should blend to the specification, not to the margin. At most they see the final price on an account that has been shared with them.
Assumptions:
- [ ] A-16 — R&D sees all samples as one shared queue, not a separate list for each taster. Each sample still has a named owner.
- [ ] A-17 — Changed 24 September 2026: R&D read the briefs and deal context on deals shared with them, but do not edit briefs. The brief is part of the deal, and editing it means managing the deal. Their comments go on the sample, and sales updates the brief. If your tasters should edit briefs directly, their role needs Manage on deals. That also lets them edit the deal itself. Previously proposed: R&D read every brief and commented on the brief itself.
- [ ] A-18 — R&D never sees quote or margin information.
- [ ] A-19 — Changed 24 September 2026: R&D’s one outward action is sending the sample feedback-chase email, from their own mailbox. The mailbox permission is the same for every role: connect, read, send. So it also lets them send other email from their own mailbox inside the CRM. Alternative: chases go through the deal’s rep, and R&D hold no mailbox permission. Previously proposed: R&D could send the chase and no other email.
- [ ] A-45 — Added 17 October 2026: For everyone whose role includes the mailbox permission, the mailbox is connected when they sign in. Any email to or from a known buyer address, in any connected mailbox, is linked automatically to that buyer’s lead or contact, and so reaches their account. (Updated 19 November 2026: before, this said “lead, contact or account”. An account has no email address of its own, so its email arrives through its contacts.) This includes email from the past 12 months. Anyone who can see that record can read it. The CRM keeps only these linked emails. It shows the rest of the mailbox live and never copies it. Each person can block addresses or domains (for example personal correspondence), so that they are never linked. Your Administrator can keep a company-wide block list. (Blocking arrives in Phase 2; it moved from Phase 1 on 11 November 2026.) This is why we recommend the mailbox permission only for the roles that write to buyers, not for Executives or Administrators. Please confirm, and tell your team before go-live that their mailboxes are read in this way.
- [ ] A-40 — Changed 24 September 2026: R&D see a lead, account or deal — with its brief and linked mail — when a colleague shares it with them. A rep who requests a sample shares the deal with the taster. R&D see a customer’s standards (with the final price) on a shared account’s page. They do not see the standards book, which carries costs. Alternative: R&D view every deal and account (all records ticked). This also shows them the mail linked to every one of those records, and each account’s final prices. Previously proposed: “View (linked to their samples)” and a view of the standards book. The permission system reaches records only through ownership, the reporting line and sharing. So it cannot express a link through a sample.
5.4 Tea Room (Pricing)
Can:
- own the standards book (Manage): create, edit and archive buying standards. These are each client’s specifications, bulk and private label alike. Each has a running number that is never reused. Archiving a standard keeps its price history and takes it out of quoting.
- set each standard’s buying cost, and set the required margin floor
- import the weekly price workbook
- hold the publish permission: enter and publish each auction week’s prices. There is one price per standard, the same for every destination (agreed 9 September 2026).
- apply a manual override between auctions when needed (recorded)
- see the full price history for each standard
- search, filter and export within the pricing screens
Cannot (by default): see accounts, deals, quotes, samples, dashboards or email — anything outside pricing. One detail cannot be avoided. A buying standard belongs to a client, so the pricing screens show client names (for example “BS-004417 — Hamburg Tea Trading”). The standards make no sense without them.
Why this shape: weekly prices are the most commercially sensitive numbers in the company. The cleanest control is a small role that owns them completely. By default nobody else can publish, and the Tea Room touches nothing else. So its account cannot be the source of an accidental change elsewhere. The floor lives here too, because it is a pricing decision. This “pricing screens only” default is the narrow reading of what you told us on 3 August. You asked us to check whether they should see more, and we would rather you choose than we guess (Q1).
Assumptions:
- [ ] A-20 — By default only the Tea Room publishes weekly prices and edits the standards book (standards, costs, floor). Reps and managers use the published prices. Nobody else edits them. (This is a default, not a rule the system enforces — see A-43.)
- [ ] A-21 — Tea Room sees pricing screens only (the Q1 default). Alternative: also give them read-only sight of quotes, deals and accounts for context. Tick here to choose the wider option. Only with the wider option can a rep share a specific deal or account with them. That is because a share reaches only people whose role can see that kind of record.
- [ ] A-22 — No fallback publisher by default. Someone may need to cover the Tea Room during leave. If so, your Administrator can add the publish permission to a named person’s role for that period. Tick to have that set up from day one.
- [ ] A-23 — Changed 24 September 2026: The Tea Room sets the margin floor. Setting the floor comes with Manage on the standards book, which also edits standards and costs. So by default the Administrator views the book and does not set the floor. Alternative: give the Administrator’s role Manage on the standards book. Previously proposed: an Administrator could also change the floor, while only viewing standards and costs.
5.5 Executive / Management
Can: see everything, and change nothing. They see:
- dashboards and KPIs, the AI morning briefing and “what’s stuck”
- both pipeline boards and every deal
- all accounts, with contact details and communication timelines
- every quote, including margins
- samples, tasks and files
- the standards book with published prices (A-26)
- search on each list
They can export any list they can see to Excel (recorded). The Managing Director’s role is this view plus the single permission to approve below-floor quotes (5.7).
Cannot: create, edit, archive, move, send, approve, publish, import or configure anything. Edit controls are hidden entirely, so the screens read as clean reports, not forms with disabled buttons. Executives also run no AI actions. The AI summaries they see (morning briefing, stuck-deal reads) are the ones the system already produced for the team.
Why this shape: you asked for management oversight without edit rights. A true picture of the pipeline for leadership was one of the reasons you gave for Pipedrive falling short. With read-only access to everything, a director can answer “what’s really happening with this buyer?” first-hand. Nobody has to prepare a report, and there is no chance of a stray edit. Margins are included because forecast oversight without margins is half a picture. But it is a choice, so it has its own tick box.
Assumptions:
- [ ] A-24 — Executive read-only access really does cover everything, including quote margins and customer contact details (Q1’s default).
- [ ] A-25 — …including the communication history on records (never anyone’s private, unlinked inbox).
- [ ] A-26 — Executives see the standards book read-only (costs, floor, published prices). Alternative: no standards book. They then see only the final prices on each account page.
- [ ] A-27 — Changed 24 September 2026: Executives can export what they can see, and every export is recorded. Export follows View for every role. So an Executive who can view in the app but cannot export is not available. Previously proposed: an alternative of viewing in the app only, with no export.
5.6 Administrator
Can: Manage on every area, with all records ticked. They are the fix-it role. Records are archived rather than deleted. They also hold System settings, which means all the Settings permissions together (Rule 3). These cover the two groups below. (changed 26 October 2026: until then the two groups were two separate permissions.)
- User and role administration:
- add a person and give them their one role, or change it
- set who they report to
- deactivate and reactivate people (never delete them)
- release mailbox connections
- build roles in the role editor: create a role, rename it, add or remove permissions, and delete a role nobody holds (active or deactivated)
- use the effective-permissions view for any user
- Configuration:
- reference data (certification list, export-document rules, dropdowns, activity types)
- shared email templates and sequences
- AI settings (per-feature on/off, model choice, monthly spend ceiling)
- mail sync settings
- imports, including the one-time Pipedrive migration
- the ERP handoff template
- when they arrive in the second phase, pipelines and stages (names, order, win %, idle-deal “rotting” thresholds) and custom fields
They view the standards book (A-23).
Cannot (by default): approve a below-floor quote (the Managing Director’s — 5.7), or publish weekly prices (the Tea Room’s, per A-20 and A-22). Never: open anyone’s personal mailbox. No permission can.
What the system enforces, and cannot be switched off:
- At least one active person always holds both the Users and the Roles permissions (changed 30 October 2026). The system refuses any change that would leave nobody holding both. Such changes are: deactivating that person, changing their role, removing the permission from their role, or deleting their role.
- Nobody can deactivate themselves.
- Nobody is deactivated while they still own records or have people reporting to them (A-42).
What the system does not enforce: whoever holds System settings can give any permission to any role, their own included. Examples are the below-floor approval and weekly publishing. The system does not block this. It records it, with who made the change and when (A-43).
Why this shape: somebody has to be able to fix anything. Examples are the wrong owner after someone leaves, a broken import, a dropdown set wrongly, or a role that locked a team out. It is safer for that power to sit in one or two clearly audited accounts than in pieces across many roles. An Administrator account is powerful: it can grant itself any permission. So who holds one is the real control, and the sign-off table at the end asks you to name them. By default the account does not carry the below-floor approval or weekly publishing (5.7).
Assumptions:
- [ ] A-28 — Changed 24 September 2026: At least two named people at Empire Teas hold a role with System settings, which includes user and role administration. Then access can always be fixed when one of them is away. During the build and support period, Altrium’s delivery accounts hold it too. You can remove them at any time. Previously proposed: one or two.
- [ ] A-29 — Administrators can see and edit all sales data, not only settings. (The alternative is a settings-only admin. It is possible, but then nobody can fix data without borrowing a manager account.)
- [ ] A-30 — Changed 24 September 2026: Only people who hold System settings see the user list, the reporting line and the roles. Everyone else sees a simple list of colleagues’ names and roles. The pickers use this list (share with, hand to, reports to). Previously proposed: managers could view the user list and their team’s reporting line.
- [ ] A-31 — Changed 24 September 2026: There are no built-in roles. The system starts with one ordinary role, IT Admin, which holds System settings. (changed 26 October 2026: until then it held a separate user and role administration permission, now part of System settings.) One account holds IT Admin. On the test and development systems, that account is
crm01@empire.lk, one of your test mailboxes. On the live system, it is the address your IT confirms (Section 9). Your Administrator signs in with it and creates every other role, with us alongside at go-live. IT Admin can then be edited, kept, or deleted once nobody holds it. Previously proposed (11 September): one built-in system Administrator role. It always existed, and could not be deleted or stripped of its permissions. We withdrew it on 24 September 2026. Before that (7 September): six built-in templates, copied when a role was created. We withdrew them on 11 September 2026. - [ ] A-42 — Changed 24 September 2026: A person cannot be deactivated while they still own leads, accounts, deals, quotes or samples, or while anyone reports to them. Your Administrator reassigns those first, using a reassignment screen that moves them in bulk. Deactivation ends the person’s sessions at once and releases their mailbox connection. Nobody can deactivate themselves. People are never deleted, so everything they did stays attributed to them. Previously proposed: deactivation blocked sign-in straight away, and a leaver’s records stayed in place until an Administrator reassigned them.
5.7 The Managing Director and below-floor quotes
We restate Q3’s plan here, so you can sign it off in one place with everything else:
The plan: by default only the Managing Director approves a below-floor quote. The MD holds a role of their own. It shows everything the Executive view shows, read-only: every deal, every quote with its margin, every account, and the standards book with costs and published prices. It adds that one permission. By default Administrators and Sales Managers do not hold it. Any below-floor quote is held, with a clear on-screen reason, and appears in the Managing Director’s approval queue. Every approval records the approver’s name, email and time, permanently.
Changed 24 September 2026: this is the recommended set-up, not a rule the system enforces. Whoever holds System settings could give the approval permission to any role, their own included. Every such change is recorded with who made it and when, so it cannot happen unnoticed. The same holds for weekly publishing (A-20). That is why we recommend that at least two named people hold System settings (A-28). It is also why the sign-off asks you to name them.
Why this shape: it is what you told us on 3 August. By default it separates the two halves of the control: the Tea Room sets the floor, and the Managing Director approves against it. So no role in the recommended set can both lower the floor and approve a quote against the lower figure. The one cost is availability. While the MD is away, below-floor quotes wait, unless a deputy has been named.
- [ ] A-32 — Confirm: the Managing Director alone approves below-floor quotes, with no deputy by default. Or: name a deputy who may approve while the MD is away: ____________________. An Administrator adds the permission to their role for a period, and the change is recorded. Also tell us whether the MD works in the system day to day (as a Sales Manager or Administrator). The default is no. If yes, the MD’s role is built to include those permissions as well (one role per person — A-2).
- [ ] A-43 — Changed 24 September 2026: The Managing Director’s approval and the Tea Room’s publishing come as the recommended configuration. They are not rules the system enforces against an administrator. Every change to who holds them is recorded. Previously proposed: Administrators could not approve, so no single account could lower the floor and then approve.
6. The screens, one by one
This table lists every screen in the system, and what each role can do there:
- work = use it fully (within their reach)
- view = read-only
- — = not visible to that role
| Screen | Sales Rep | Sales Manager | R&D / Taster | Tea Room | Executive | Administrator |
|---|---|---|---|---|---|---|
| Sign-in (company Microsoft account — the only sign-in method, decided 4 Sep 2026; only people an administrator has added can sign in) | all roles — every user signs in the same way | |||||
| Dashboard (KPIs, AI briefing, what’s stuck, funnel, forecast) | work (own book) | work (team) | view (samples) | — | view (company) | work |
| Lead triage queue (with the Unassigned filter for roles with all records on leads) | work (own) | work (team) | view (shared with them) | — | view (all, incl. unassigned) | work (all, incl. unassigned) |
| Pipeline boards & deal detail | work (own) | work (team) | view (shared with them) | — | view | work |
| Accounts & contacts | work (own) | work (team) | view (shared with them) | — | view | work |
| Samples board & table | work (own requests) | work (team) | work (all) | — | view | work |
| Quotes | work (own) | work (team) | — | — | view · MD: + approve below-floor | work |
| The standards book (standards, costs, floor, price working, published prices) | — (final prices on the account page) | — (final prices on the account page) | — | work | view | view |
| Weekly price publish | — | — | — | work | — | — |
| Activities & calendar | work (own records) | work (team) | work (samples) | — | view | work |
| Inbox & compose | work (own mailbox) | work (own mailbox) + team record mail | work (own mailbox) + mail on shared records | — | view (record mail) | view (record mail) + company-wide email block list (Phase 2) |
| Outreach sequences | work (own) | work (team) | view (shared with them) | — | view | work + configure |
| Import / export & Pipedrive migration | export (own) | export (team) | export (what they see) | export (pricing) | export (what they see) | work |
| Users & reporting line | — | — | — | — | — | work |
| Roles (the role editor) | — | — | — | — | — | work |
| Effective permissions (“why can this person see this?”) | — | — | — | — | — | work |
| Pipeline configuration | view | view | view | — | view | work |
| Custom fields & reference data | use | use | use | use | view | work |
| AI settings (features, models, spend ceiling) | — | — | — | — | — | work |
| Audit trail | no audit screen in this version — on-record history only, for everyone who can view the record | |||||
| Trade-show capture app | work | work | — | — | — | configure |
Sharing is an action, not a screen. The Share control sits on the lead, account, deal and quote detail screens (Section 2). Whoever may manage that record can use it: its owner, a manager above them, or a colleague it was shared with whose role manages that kind of record. A record shared with someone appears in their lists, marked as shared, alongside their own records.
- [ ] A-33 — This screen map matches how your teams should meet the system on day one. (Anything marked — is hidden for that role, as Rule 5 says.)
7. Rules that cut across everything
- Nobody gets in unless an administrator has added them. Your Administrator adds each person in the CRM with their one role. There is no invitation email. The Administrator tells the person, and they sign in with their company Microsoft account. When they sign in, the CRM checks that the Microsoft account belongs to an active user it knows. The CRM refuses anyone else.
- The AI drafts. A person decides. Every AI output is labelled as AI-generated, with its confidence. This covers scores, summaries, extractions, drafted emails and sequence steps. Each output arrives as a draft, and waits for a person whose role allows the action. Approving records who approved. Each rep reviews the AI’s work on their own records. Managers can review across their team. No AI output ever prices anything. The AI holds no permission, so no role your Administrator builds can hand one to it.
- Every price is a person’s decision. Whoever holds the publish permission (by default the Tea Room) enters and publishes the weekly prices. The system computes margins from the Tea Room’s costs. The margin-floor check and the MD arrangement (5.7) govern exceptions. The planned auction-price feed (a later addition) will only ever suggest a reference to the Tea Room. It will never set a price.
- Personal mailboxes stay private, exactly as in the Pipedrive set-up you use today. No permission opens another person’s mailbox. This is a fixed rule, not a setting. Sharing a record does not widen it either (Section 2). Colleagues see the mail linked to a record they can reach, such as a deal’s thread. They never see each other’s inboxes.
- The shared
info@address stays outside the CRM in this version. Whoever readsinfo@today forwards an inquiry to the rep who covers it. The rep’s own connected mailbox brings it into the CRM, and the rep creates the lead. If you prefer,info@can be added as an ordinary CRM user. It must then be a licensed mailbox that can sign in to Microsoft itself. A Microsoft 365 shared mailbox has no sign-in of its own, so it cannot be added this way. Everything done while signed in asinfo@is then recorded asinfo@, not as the person using it (A-44). - New capabilities start switched off. A later release may add something new that the system can do. The matching permission is then added to the list, but granted to no role. It stays that way until your Administrator (or we, at the release) adds it to a role. Nothing appears on anyone’s screen by surprise. Each release comes with a short note of the new permissions, and the roles we recommend adding them to.
- Permission changes apply straight away. When your Administrator changes a role, the people who hold it see the change on their next action. They do not need to sign out.
- Everything is recorded: who, what and when. The trail records every change: stage moves, reassignments, shares and their removal, price publishes and overrides, quote submissions and approvals. It also records configuration and custom-field changes, role, permission and reporting-line changes, imports, and every AI approval. It records every sign-in, refused sign-in and sign-out, every deactivation and reactivation, and every export. Viewing is not recorded. There is no audit screen in this version. The trail is kept in the database, and nothing is removed from it in this version. We answer audit questions from it on request.
- Offboarding is safe by design. Deactivating a user is a user and role administration action, under System settings. It ends their sessions at once, blocks sign-in, and releases their mailbox connection. The CRM refuses it while they still own records or have people reporting to them. Those are reassigned first (A-8, A-42). Nobody can deactivate themselves. People are never deleted. A deactivated person stays in the reporting line and on the records they touched. Shares made to them stay on the record, marked as deactivated, until someone removes them. Disabling the person’s Microsoft account on your side is a second safeguard. Microsoft then refuses their next sign-in before it reaches the CRM. But it does not end a CRM session that is already open. That session runs until it expires. This is why deactivating the person in the CRM is the step that takes effect at once.
8. What we still need beyond this document
Some of these questions were already asked in Questions for Empire Teas, and one is new. We list them here so that this document is complete about access.
| Ref | Question | Where it stands |
|---|---|---|
| Q2 | How a new user is told they have access. (Sign-in is by company Microsoft account, so there is no CRM password to set.) What happens to a leaver’s records | Decided 24 September 2026: no invitation email. Your Administrator adds the person and tells them. Nobody can sign in unless added. Deactivation waits until their records and reports are reassigned (A-42). One role per person (A-2) |
| Q6 | The shared info@ inbox: same screen or separate, who may read it, how an inquiry gets picked up |
Decided 24 September 2026: info@ stays outside the CRM in this version. Inquiries are forwarded to a rep, whose own mailbox brings them in (A-44) |
| New | The administrator account on the live system | The email address of the account that starts in the IT Admin role on the live system, confirmed by your IT (Section 9). The live system cannot start without it. It must belong to a Microsoft 365 account that can sign in |
- [ ] A-44 —
info@stays outside the CRM in this version. Whoever reads it forwards an inquiry to the rep who covers it. The rep creates the lead from their own mailbox. Alternative: addinfo@as an ordinary user. This works only if it is a licensed mailbox that can sign in to Microsoft itself. A Microsoft 365 shared mailbox cannot. Everything done while signed in asinfo@is then recorded asinfo@, not as the person. Previously proposed:info@connected as its own inbox, belonging to no one person.
9. Sign-off
Who starts on which role? Names are as valuable as the sign-off. They become the actual accounts your Administrator creates, each holding the role named here (one line per person — A-2).
| Role | Name(s) at Empire Teas |
|---|---|
| Sales Representative | |
| Sales Manager | |
| R&D / Sample Owner (Taster) | |
| Tea Room (Pricing) | |
| Administrator (we recommend at least two — A-28) | |
| Executive / Management | |
| Managing Director (by default the only below-floor quote approver — 5.7) |
Which account starts as IT Admin on the live system? Email address, confirmed by your IT administrator: ______________________ (A-31). On the test and development systems, this is the crm01@empire.lk test mailbox.
Who reports to whom? For everyone above, give their manager in the CRM. Leave it blank for the top of the chain. An org chart attached to your reply does the same job.
| Person | Reports to |
|---|---|
Confirmation. Ticking a section confirms every assumption in it that you have not separately corrected.
| Section | Confirmed | Corrections (by A-number) |
|---|---|---|
| 1 — How access works (A-1–A-3) | ☐ | |
| 2 — The reporting line and sharing (A-4–A-8, A-34–A-37) | ☐ | |
| 3–4 — The starting access map and the capture app (A-41). Its cells are confirmed through 5.1–5.7. A-9 and A-13 set whether a role ticks all records | ☐ | |
| 5.1 — Sales Representative (A-9–A-12, A-38) | ☐ | |
| 5.2 — Sales Manager (A-13–A-15, A-39) | ☐ | |
| 5.3 — R&D / Taster (A-16–A-19, A-40) | ☐ | |
| 5.4 — Tea Room (A-20–A-23) | ☐ | |
| 5.5 — Executive (A-24–A-27) | ☐ | |
| 5.6 — Administrator (A-28–A-31, A-42) | ☐ | |
| 5.7 — Managing Director arrangement (A-32, A-43) | ☐ | |
| 6 — The screen map (A-33) | ☐ | |
| 8 — The shared inbox (A-44) | ☐ |
Signed for Empire Teas (Pvt) Ltd: ______________________ Name: ______________________ Date: ____________
Once you sign, your Administrator signs in first with the IT Admin account. With us alongside, they create these six roles from this mapping, and add the people and the reporting line. You can still make corrections after sign-off: your Administrator makes them in the role editor. But the build, testing and training will assume this baseline.
Change history
First issued 2 September 2026. The changes since then, newest first; the document above already includes each of them.
- Revised again 12 November 2026 — converting a captured lead also needs Manage on leads; the capture app also plans a show before it starts.
- Revised 12 November 2026 — the trade-show capture app has its own permission, Use the capture app, and a captured lead reaches the CRM only when someone converts it, becoming theirs.
- Revised 8 November 2026 — anyone can share a saved list view with everyone who can see that screen, not only managers; an administrator can remove a shared view left by someone who has left.
- Revised 26 October 2026 — user and role administration is now part of System settings: one permission, shown in the role editor as “Manage settings, users and roles”, opens every page under Settings, the users and roles included; the starting IT Admin role holds it; writing email templates, one’s own included, is part of it, so other roles use templates without writing them.
- Revised 21 October 2026 — an account briefing comes with managing accounts and is prepared when someone asks for it.
- Revised 17 October 2026 — your own mailbox is connected when you sign in, and email with a known buyer is linked to that buyer’s record for anyone who can see it (A-45); a company-wide email block list.
- Revised 11 October 2026 — no global search (each list searches its own records), no AI drafting of product briefs, and no separate price-history screen; their rows are removed.
- Revised 30 September 2026 — anyone who can manage a record, including a colleague it was shared with, can hand it to a new owner; no lead is left without an owner.
- Revised 27 September 2026 — no reach setting per permission: a person reaches their own records and their team’s through the reporting line, and one “all records” tick per area reaches everyone’s.
- Revised again 24 September 2026 — View and Manage per area plus a few named permissions; one starting “IT Admin” role instead of a built-in Administrator; shares can be passed on; no invitation email; the shared inbox stays outside the CRM.
- Revised 24 September 2026 — accounts and contacts are archived, never deleted; a rep may hand an account they own to a colleague.
- Revised 11 September 2026 — no templates, one role per person, AI help rides on the permission it assists.
- Revised 7 September 2026 for configurable roles.