← Project memory
Source receipt

Re: Meridian - environment access

email_threadL1
Author / speaker
Nadia Haddad
Recorded date
2026-02-24T14:15:00
Position
Message 6
Document
emails/19_meridian-environment-access

Surrounding conversation

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

Priya Nair · Message 5 · 2026-02-25T09:05:00

This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button. Read access to test, yes. Not production, and not the fresh configuration, which is not theirs to look at. Is the environment able to restrict by category? Because if read access to test means read access to everything in test, that is a different conversation. Priya Nair IT Integration Lead +49 151 3307 9126 Acme Org GmbH | Hansaring 82, 50670 Köln acme-org.example Image

Ivan Petrov · Message 7 · 2026-02-24T10:30:00

This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button. Nadia, For the bakery build we need read access to the test environment for two people, myself and Ruth. Can you set that up, or does it go through Acme? Kind regards, Ivan Petrov Principal Consultant, Meridian Consulting Image +44 7700 900 942 meridian-consulting.example Ivan Petrov | LinkedIn Image

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.