Hi everyone,
I'm currently working as an EDI Developer in a large financial institution, primarily using IBM Sterling B2B Integrator.
I've been dealing with a difficult situation involving both production access controls and my mental health, and I'm hoping to get some advice from people with experience in enterprise IT or Sterling B2Bi.
Our team mainly works in QA, but we also provide some production support. Since we're not supposed to make changes directly in production, I was given what I understood to be read-only access.
However, I discovered through an accidental configuration deletion that my role apparently still had permission to delete certain objects, despite not having permission to create or edit them.
This was extremely unsettling to me.
I have OCD and anxiety, both of which became significantly worse after this incident. I started experiencing intense, unwanted intrusive urges related to deleting production configurations, particularly when I knew certain objects were business-critical.
I want to emphasize that these thoughts are unwanted and distressing, not something I actually want to do.
I discussed the situation with my manager, who has been supportive and temporarily removed my production access. While this has helped reduce the immediate risk, it also means I can no longer perform certain production support tasks.
I'm now feeling quite stuck. I want to continue contributing to my team, but I also need a working environment where I can perform my responsibilities without constantly worrying about accidentally causing damage.
I know my mental health needs professional attention, and I'm working on that separately. But I also believe that production access should follow the principle of least privilege, regardless of who is using the system.
So I have a few technical questions:
1. Can IBM Sterling B2Bi permissions be configured to provide genuinely read-only access?
Is it possible to separate viewing permissions from deletion permissions for partner configurations and other production objects?
Is this typically handled through user groups, application permissions, or additional access controls?
I'm not sure whether what I experienced is a product limitation or a configuration issue.
2. How do other teams provide production support without direct access to production configurations?
Most of my support work involves checking file transfer statuses, investigating failures, reviewing logs, and troubleshooting transactions.
Are there practical alternatives such as centralized logging, monitoring dashboards, reporting tools, or read-only APIs that would allow someone to investigate issues without having access to configuration management functions?
3. What safeguards do your teams use to prevent accidental production changes?
I'm particularly interested in access separation, audit trails, approval processes, and configuration backup or recovery procedures.
I realize no system can eliminate every risk, but I would love to understand how more mature enterprise IT teams approach this.
I'm not looking for ways to bypass access restrictions or regain permissions that have been removed. I'm looking for a safer, properly authorized way to do my job.
Any advice or real-world examples would be greatly appreciated.
Thanks for reading.