source: .forge/client/dependencies.md · generated — edit the markdown, not this file

Empire Teas CRM — What the Project Needs from Empire Teas

Prepared by Altrium for Empire Teas (Pvt) Ltd Scope: every account, access right and piece of information the Altrium team needs from Empire Teas to build the CRM. Each item is needed before the work it makes possible, and development stops if it is missing.

If an item arrives late, the work that needs it moves later by the same number of days. This is the position agreed in the proposal.


1. Accounts and access

1.1 AWS hosting — Empire Teas’ own AWS account (✓ opened; needed ready by Fri 2 October 2026)

Updated 29 September 2026: Empire Teas chose to hold the AWS account itself. This replaces the 13 September plan, in which Altrium would have owned the account and charged a fixed monthly fee under SOW ET-002.

The AWS account belongs to Empire Teas.

  • Empire Teas IT (Kavindu Anthony) holds the account.
  • It is paid with Empire Teas’ card. AWS bills Empire Teas directly, for what is used.
  • Empire Teas created an administrator login for Altrium’s DevOps engineer. The engineer builds the environments inside the account and gives each developer their own login.

The schedule assumes the account is ready, with the access the team needs, by Friday 2 October 2026. If it is ready later, every milestone moves by the same number of days.

Region: US East (N. Virginia, us-east-1). It was chosen on 1 October 2026 for two reasons:

  • It is AWS’s lowest-priced region, so running costs stay at or below the proposal’s figures.
  • The web-search service that lead research may use is offered there.

Where Amazon Bedrock processes an AI request depends on its Bedrock route. Processing in any of Amazon’s commercial regions was accepted on 4 November 2026 (Questions for Empire Teas, Q18, answered and closed).

Users reach the applications through CloudFront, Amazon’s worldwide network, so pages load quickly wherever the region is.

All data stays inside Empire Teas’ own AWS account. It is never kept in a shared or third-party store, and it is never used for any other purpose. Altrium works in the account on Empire’s behalf, as its data processor.

For reference, these are the AWS services the CRM uses:

Service Used for
ECS Fargate + ECR Running the backend application (the API and its background worker)
Elastic Load Balancing Sending traffic to the backend, over a secure connection
RDS (PostgreSQL) The database
S3 File attachments, and the files of both web applications
CloudFront + Certificate Manager Serving both web applications at their own addresses, with security certificates
SQS The queue of background jobs
EventBridge Scheduler All work that runs at set times (alerts, ending prices, keeping mailbox links alive)
Amazon Bedrock The AI layer. Anthropic’s Claude models (Haiku 4.5 and Sonnet 5.5, and Haiku 5.5 once it is on Bedrock), called from inside the project’s AWS account. Altrium turns on model access and asks for the limits it needs during setup. Updated 26 October 2026: AWS gives a new account lower AI limits until it has a few months of use and spending. AWS has also not yet made Sonnet 5.5 available on Empire Teas’ account. So every AI feature runs on Haiku 4.5 until AWS raises the limits after its own review. Empire Teas does not need to do anything for this.
Amazon SES System email. Updated 12 November 2026: the capture app sends no email; its notifications appear inside the app. A new AWS account starts with limited sending. Altrium asks AWS for full sending during setup, which takes a short time to approve.
Secrets Manager Passwords and keys
CloudWatch + AWS Budgets Logs, measurements and alarms, including cost alerts
Amazon SNS Sending those alarms. Error alarms email the delivery team as soon as something needs attention. Cost alerts are AWS Budgets alerts, set up by the people who look after the AWS bill.
IAM, VPC Access control and networking

Access. The Altrium team needs an administrator-level login and a view of the bill. The administrator login was given to Altrium’s DevOps engineer ✓. After Foundation it is narrowed, and each person has their own login with multi-factor sign-in.

Cost alerts. Empire Teas receives the AWS bill. So the AWS budgets and cost alerts, and who receives them, are set up by the people at Empire Teas and Altrium who look after that bill. Both acceptance rounds run in one temporary test environment. It appears on the bill from November to January, and then it is removed. (Updated 18 November 2026.)

AI billing. Claude runs through Amazon Bedrock in the project’s AWS account. So Empire has no separate AI account or AI bill. AI use appears on Empire Teas’ AWS bill, charged for what is used. The expected running costs are in the Product Requirements document.

1.2 Microsoft 365

How email works in the CRM. Updated 17 October 2026.

  • When a salesperson signs in to the CRM, their work mailbox is connected automatically. There is nothing to press, because the IT administrator’s one-time approval (below) covers everyone.
  • The CRM shows the mailbox live from Microsoft. It keeps only the emails with buyers. Those emails appear on the matching lead, contact and account, and on deals from Phase 2.
  • Calendar and contact sync come in Phase 2.
  • Before 17 October, the plan was for each salesperson to connect their own mailbox with a one-time “allow access” step, and for every email to be copied.

The shared inquiries address (for example info@…). Updated 24 September 2026.

  • In this version, the shared address stays outside the CRM. Inquiries that arrive there are forwarded to the rep who covers them. That rep’s connected mailbox then brings them into the CRM.
  • If Empire Teas prefers, info@ can be added as an ordinary CRM user. This works only if it is a licensed mailbox that can sign in to Microsoft. A Microsoft 365 shared mailbox cannot sign in, so it cannot be used. Anything done while signed in as info@ is recorded as info@, not as a person.

This is the same way Pipedrive works today, and it keeps the same privacy. Each person’s mailbox stays their own. Colleagues see only the conversations linked to CRM records, under the CRM’s sharing rules.

The IT administrator needs only a few minutes for all of the following:

Item In plain terms
One-time approval by the IT administrator ✓ given 10 September 2026 Before any app can read or send a person’s email, Microsoft needs the company’s IT administrator to approve it once, for the whole company: “this app may use mail, calendar and contacts when a user allows it”. Altrium sent the approval link and the list of permissions (read and write mail, send mail, read and write calendar, read and write contacts), and the administrator approved it. Since 17 October, each salesperson’s mailbox connects when they sign in to the CRM. No IT ticket is ever needed for each person.
Test logins ✓ provided Test Microsoft 365 accounts in Empire Teas’ own system, each with a working mailbox: CRM01–05@empire.lk. Our environment record holds the full list. All testing uses these accounts, never a real employee’s mail. Some act as salespeople and one as a sales manager, so who can see what is tested on Empire Teas’ real setup. Updated 24 September 2026: crm01@empire.lk is also the first administrator account (the only account in the IT Admin role) on the test and development systems. Daily development uses a built-in stand-in for Microsoft. So these accounts are used only for the live checks in each phase, and they see little traffic. They can be deleted after go-live.
The live system’s administrator email (added 24 September 2026) The live CRM starts with one account that can add people and create roles: the IT Admin account. On the test and development systems, this is the crm01@empire.lk test mailbox. On the live system, it is the work address of the person who will run the CRM. Empire Teas’ IT administrator confirms this address. It must belong to a Microsoft 365 account that can sign in. Updated 28 October 2026: the address is written in the live system’s settings. These settings are kept in Altrium’s private code repository with the system’s other settings that are not secret. The address is not stored as a secret. The system needs this account each time it is set up again, so the best choice is a person, or a shared admin mailbox, that will stay in use. The live system cannot start until this address is given.
Login certificates (two) ✓ added 24 September 2026 Empire Teas’ Microsoft setup does not allow password-style app keys (client secrets), so sign-in uses a security certificate instead. Altrium creates each certificate and sends its public half to the IT administrator, who adds it to the CRM app. There are two certificates: one for the live system, and one shared by the test and development systems and by testing on a developer’s computer (see the last row). Both were added to the CRM app on 24 September 2026 and are valid until 23 September 2028. The private keys stay with Altrium, in secure storage, and are never shared. Before a certificate expires, Altrium sends a new one. The IT administrator adds the new one, and only then removes the old one, so sign-in never stops.
Return addresses for connecting a mailbox ✓ added to the CRM app 24 September 2026 When a mailbox is connected, Microsoft sends the salesperson back to the CRM at a fixed address. Microsoft only allows addresses that the IT administrator has listed on the CRM app. Sign-in already had its three addresses. Connecting a mailbox needed three more, one for each environment, each added as a Web address: https://api.crm.empire.lk/authorized/microsoft-mailbox, https://api.uat.crm.empire.lk/authorized/microsoft-mailbox and https://api.dev.crm.empire.lk/authorized/microsoft-mailbox. This takes a few minutes in the Azure portal. Calendar, contacts and the trade-show app need no more addresses.
Testing from a developer’s computer ✓ agreed; addresses added to the CRM app 24 September 2026 So that sign-in and mailbox connection could be tested on Empire Teas’ real Microsoft setup before the cloud environments existed, the CRM app has two temporary return addresses: http://localhost:8080/login/oauth2/code/microsoft and http://localhost:8080/authorized/microsoft-mailbox. They use the test-and-development certificate, so no extra certificate is needed. Only the test accounts are used. Both addresses are removed before go-live.

1.3 Pipedrive (✓ exports received 13 and 28 September 2026)

We asked for a full export of every record type (with custom fields, files and users), or administrator access for a guided walkthrough. This was the most valuable item on this list: it answers about a dozen design questions at once, and it lowers the risk of the data move more than anything else.

Update 6 October 2026 — done ✓.

  • Empire Teas shared Pipedrive exports of its leads (13 September 2026) and of its organisations and people (28 September 2026).
  • The data move is designed and tested against these exports.
  • Deals are not moved in Phase 1, so they were not exported. For Phase 2, we will ask for an export of deals. It will answer the open questions about your pipelines and deals.
  • We answer the other Pipedrive questions from the exports where we can, and ask you directly about the rest. So no administrator access or walkthrough is needed.

1.4 Domain and DNS

We asked for three things:

  • the web address for the CRM;
  • a second address for the trade-show capture app, which is hosted separately;
  • DNS access to add the email records that stop the CRM’s email being marked as spam (SPF, DKIM and DMARC).

DNS changes take time to spread across the internet, so naming the addresses early costs nothing and protects the email features later.

Update 30 September 2026.

  • The addresses sit under crm.empire.lk. The live system uses crm.empire.lk, api.crm.empire.lk and capture.crm.empire.lk. Development and testing use dev. and uat. versions of these.
  • The one DNS change asked of Empire IT was to hand the crm.empire.lk subdomain to Empire Teas’ AWS account. This means adding four NS records named crm in the empire.lk zone.
  • After that, every CRM address, certificate and email record is managed in AWS, with no further DNS request. The one exception: if the CRM’s email is to be sent from an @empire.lk address, we will confirm that with Empire IT.
  • The rest of empire.lk, including the website and email, does not change.

Update 1 October 2026 — done ✓. Empire IT added the four records in Cloudflare, where the empire.lk DNS is managed. crm.empire.lk now points to Empire Teas’ AWS account. The website and email on empire.lk are not affected.


2. Data and information

Item From Used for
The weekly price list for the buying standards, and each standard’s costs Tea Room The buying-standards book (there is no separate product catalogue), the margin on quotes, and how the weekly prices are published
Which certifications each buying standard holds QC The check that warns when a standard’s certifications do not match what the buyer needs
Roles and the reporting line: what each of the six recommended roles can do on day one (the Tea Room and Executive roles especially), and who reports to whom Sales leadership The roles created at go-live, and the organisation chart loaded with them

About the roles:

  • Roles can be changed in the CRM (agreed 7 September 2026). Your administrator creates them, with us alongside, at go-live. Each person has one role (decided 11 September 2026).
  • The CRM starts with one ordinary IT Admin role and account, not a built-in administrator (decided 24 September 2026).
  • Our proposed answer is the companion document Empire Teas CRM — Who Can Do What, for you to confirm or correct. Its latest revision date is at the top of that document. Q1 in Questions for Empire Teas summarises it.

All three items shape how the system is built, and that work starts in Foundation, well before the features that use them. We agree the shape of the data in working sessions in the project’s first days. So what we need is a sample in hand, not a research project.


3. Everything on one page

# What is needed What it makes possible
1 AWS hosting in Empire Teas’ own account (Section 1.1). Account opened and administrator login given ✓ (29 September 2026). Needed ready, with the access the team needs, by Fri 2 October 2026. Altrium sets up the environments, the AI layer and the region (US East) inside it. The cloud environments, the AI layer, and everything that runs on them
2 Pipedrive access (Section 1.3). Exports received ✓ (13 and 28 September 2026). The design of the data move, and answers to a dozen design questions
3 Roles and the reporting line (Section 2): what the Tea Room and Executive roles can do, and who reports to whom. Confirm the Who Can Do What proposal (latest revision dated at the top of that document). The roles created at go-live, and the organisation chart
4 Microsoft 365 (Section 1.2). Administrator approval ✓ (10 September 2026). Test accounts ✓ (CRM01–05@empire.lk set up). Login certificates, mailbox return addresses and testing addresses ✓ (24 September 2026). Still needed: the live system’s administrator email. The live system cannot start without it. Email, calendar, contacts and sign-in in the CRM; the first sign-in on the live system
5 Domain names and DNS access (Section 1.4). The crm.empire.lk handover (four NS records) ✓ (1 October 2026). The applications’ addresses; email that is not marked as spam
6 Which certifications each standard holds (Section 2) The certification check
7 The weekly price list and each standard’s costs (Section 2) The buying-standards book and quote margins

The earlier each item arrives, the more protected the schedule is for both sides.

Generated from .forge/client/dependencies.md by .claude/lib/render-docs-html.js. Markdown is canonical.