emails · PRIMARY EVIDENCE
Meridian - environment access
emails/19_meridian-environment-access.txt
Read the source in context.
Thread dates and speakers remain part of the record. A removed line is no longer available in this workspace.
1*** SYNTHETIC DATA. Entirely fictional. Acme Org, Meridian Consulting and every
2*** person named are invented. Generated for the RELEX challenge track,
3*** AaltoAI Hackathon 2026.
5Subject: Meridian - environment access
6From: Ivan Petrov <i.petrov@meridian-consulting.example>
7Date: Monday, March 2, 2026 9:30 AM
8To: Priya Nair <priya.nair@acme-org.example>
9Cc: Tomas Lindholm <tomas.lindholm@relexsolutions.example>; Nadia Haddad <n.haddad@relexsolutions.example>; Ana Duarte <ana.duarte@relexsolutions.example>
10Messages in thread: 7
12This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button.
14None taken, and it is the right call. We work from extracts on most engagements for
15exactly that reason.
17Kind regards,
19Ivan Petrov
20Principal Consultant, Meridian Consulting
21Image
22+44 7700 900 942
23meridian-consulting.example
24Ivan Petrov | LinkedIn
25Image
28From: Priya Nair <priya.nair@acme-org.example>
29Sent: Monday, March 2, 2026 8:45 AM
30To: Tomas Lindholm <tomas.lindholm@relexsolutions.example>
31Cc: Nadia Haddad <n.haddad@relexsolutions.example>; Ana Duarte <ana.duarte@relexsolutions.example>; Ivan Petrov <i.petrov@meridian-consulting.example>
32Subject: Re: Meridian - environment access
34This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button.
36Extracts. Slower is acceptable, the other thing is not.
38Ivan, no offence intended. It is not about Meridian, it is that I cannot explain to my
39data protection officer why a third party had read access to everything.
41Priya Nair
42IT Integration Lead
43+49 151 3307 9126
44Acme Org GmbH | Hansaring 82, 50670 Köln
45acme-org.example
46Image
49Från: Tomas Lindholm <tomas.lindholm@relexsolutions.example>
50Skickat: den 26 februari 2026 16:20
51Till: Nadia Haddad <n.haddad@relexsolutions.example>
52Kopia: Priya Nair <priya.nair@acme-org.example>; Ana Duarte <ana.duarte@relexsolutions.example>; Ivan Petrov <i.petrov@meridian-consulting.example>
53Ämne: Re: Meridian - environment access
55Realistic but not free. Roughly two weeks of setup and it needs somewhere to run.
57The cheaper option is extracts. Slower for Meridian and no risk on the fresh side.
59Med vänliga hälsningar,
60Tomas Lindholm
61Solution Architect Bild borttagen av avsändaren.
62+46 70 118 44 92
63tomas.lindholm@relexsolutions.example
64Vasagatan 7, 111 20 Stockholm
65Bild borttagen av avsändaren.
66relexsolutions.example
69From: Nadia Haddad <n.haddad@relexsolutions.example>
70Sent: Thursday, February 26, 2026 11:40 AM
71To: Priya Nair <priya.nair@acme-org.example>
72Cc: Ana Duarte <ana.duarte@relexsolutions.example>; Ivan Petrov <i.petrov@meridian-consulting.example>; Tomas Lindholm <tomas.lindholm@relexsolutions.example>
73Subject: Re: Meridian - environment access
75Honest answer: read access is read access. There is no category level restriction in the
76current configuration.
78So either they see the fresh configuration, or we create a separate environment, or they
79work from extracts we prepare.
81Tomas, is a separate environment realistic?
83Nadia Haddad
84Solution Consultant Image
85+46 76 552 30 18 | CET
86n.haddad@relexsolutions.example
87Vasagatan 7, 111 20 Stockholm
88Image
89Plan better. Sell more. Waste less
90relexsolutions.example
93From: Priya Nair <priya.nair@acme-org.example>
94Sent: Wednesday, February 25, 2026 9:05 AM
95To: Nadia Haddad <n.haddad@relexsolutions.example>
96Cc: Ana Duarte <ana.duarte@relexsolutions.example>; Ivan Petrov <i.petrov@meridian-consulting.example>
97Subject: Re: Meridian - environment access
99This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button.
101Read access to test, yes. Not production, and not the fresh configuration, which is not
102theirs to look at.
104Is the environment able to restrict by category? Because if read access to test means
105read access to everything in test, that is a different conversation.
107Priya Nair
108IT Integration Lead
109+49 151 3307 9126
110Acme Org GmbH | Hansaring 82, 50670 Köln
111acme-org.example
112Image
115From: Nadia Haddad <n.haddad@relexsolutions.example>
116Sent: Tuesday, February 24, 2026 14:15
117To: Ivan Petrov <i.petrov@meridian-consulting.example>
118Cc: Ana Duarte <ana.duarte@relexsolutions.example>; Priya Nair <priya.nair@acme-org.example>
119Subject: Re: Meridian - environment access
121It goes through Priya, since it is Acme's environment.
123Priya, can Meridian have read access to test? Two users.
125Nadia Haddad
126Solution Consultant Image
127+46 76 552 30 18 | CET
128n.haddad@relexsolutions.example
129Vasagatan 7, 111 20 Stockholm
130Image
131Plan better. Sell more. Waste less
132relexsolutions.example
135From: Ivan Petrov <i.petrov@meridian-consulting.example>
136Sent: Tuesday, February 24, 2026 10:30 AM
137To: Nadia Haddad <n.haddad@relexsolutions.example>
138Cc: Ana Duarte <ana.duarte@relexsolutions.example>; Priya Nair <priya.nair@acme-org.example>
139Subject: Meridian - environment access
141This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button.
143Nadia,
145For the bakery build we need read access to the test environment for two people, myself
146and Ruth. Can you set that up, or does it go through Acme?
148Kind regards,
150Ivan Petrov
151Principal Consultant, Meridian Consulting
152Image
153+44 7700 900 942
154meridian-consulting.example
155Ivan Petrov | LinkedIn
156Image