← Project memory
Source receipt

Meridian - environment access

email_threadL1
Author / speaker
Ivan Petrov
Recorded date
2026-03-02T09:30:00
Position
Message 1
Document
emails/19_meridian-environment-access
This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button. None taken, and it is the right call. We work from extracts on most engagements for exactly that reason. Kind regards, Ivan Petrov Principal Consultant, Meridian Consulting Image +44 7700 900 942 meridian-consulting.example Ivan Petrov | LinkedIn Image

Surrounding conversation

Priya Nair · Message 2 · 2026-03-02T08:45:00

This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button. Extracts. Slower is acceptable, the other thing is not. Ivan, no offence intended. It is not about Meridian, it is that I cannot explain to my data protection officer why a third party had read access to everything. Priya Nair IT Integration Lead +49 151 3307 9126 Acme Org GmbH | Hansaring 82, 50670 Köln acme-org.example Image

Nadia Haddad · Message 4 · 2026-02-26T11:40:00

Honest answer: read access is read access. There is no category level restriction in the current configuration. So either they see the fresh configuration, or we create a separate environment, or they work from extracts we prepare. Tomas, is a separate environment realistic? Nadia Haddad Solution Consultant Image +46 76 552 30 18 | CET n.haddad@relexsolutions.example Vasagatan 7, 111 20 Stockholm Image Plan better. Sell more. Waste less relexsolutions.example

This is the application's current source record. Local dates from the archive retain their original timezone ambiguity. Source IDs and positions connect this passage to its document.