Dear Community, I'm trying to understand the permissions levels for pipelines. My goal is for my user group to load a file into a dedicated project space and execute a pipeline in a second project space where they can execute, but not edit any pipelines. I gave the user group 'Read & Execute', but they can still edit the pipeline. SnapLogic documentation makes it appear that this would be the correct permission. Have I set this up correctly?
Hi Tom, What you’re trying to achieve is correct in principle, but the behavior you’re seeing usually comes from how permissions are combined across project spaces in SnapLogic. Permissions are additive, meaning a user can end up with higher privileges if they inherit them from another role, group, or parent project space. So even if you explicitly grant “Read & Execute” on the target project space, users can still edit pipelines if they also have: “Write” or “Full Access” on the same project space (via another group), or
Higher permissions inherited from a parent project space
User being an Org admin
What to check
Project Space hierarchyEnsure the target project space is not inheriting broader permissions from a parent space.
Group memberships, Verify the users are not part of another group that grants Write or higher access.
Direct vs inherited permissions : Even if “Read & Execute” is set locally, inherited permissions can override your intention (Propagate permission check box, if you're using project folders).
Thank you!
You're welcome!
