Hi 🙂 did anyone encounter the situation, when an experimenter account cannot start the experiments ("You do not have permission to complete that action." message appears), while running the self-hosted version of Growthbook? Thank you in advance for any tips

Hi, Martin - does your GrowthBook instance have any projects? Every user has a global role, but that role can be overridden for individual projects. So I've seen this happen when a user has a project-specific role that doesn't provide permission to start experiments.

Hi, @billions-xylophone-11752. Thank you for your reply. Yes, our GH instance has projects, but I've already investigated that option. User is unable to start the experiments both with project-specific roles and with global role only.

@nice-electrician-61157 Would you be able to send me a screenshot outlining the user's roles, along with a screenshot of the experiment that shows the project? That will help me troubleshoot. Also, can you verify which version of GrowthBook you're running. You're welcome to message me privately.

Hi, @billions-xylophone-11752 🙂 sorry for the late reply. Answers: • version: Build: 6db3cf0 (2023-11-27) • screenshots attached

Hey Martin - no worries. Would it be possible to get a view of the user's role modal like this screenshot? The

experimenter

role (along with the

engineer

role have an additional dimension that can be added to them that restricts permissions to specific environments. I can't quite tell from the first screenshot, but it appears that this has limited permissions to 1 environment. If the experiment is affecting an environment outside of the environment this user has permission to published experiments, that would result in the "you don't have permission" message.

Hi. Screenshot attached. Yes, the user is restricted to the PROD environment, as we don't want him to be able to run experiments in any other environment (staging). The experiment, that we are talking about, is created in the PROD environment (using the PROD SDK and targeting the prod URL)

Thank you, Martin! I think I may've found the issue. I'm syncing with the team to discuss.

Thank you for the proposal. I will try the fix and in a meantime, I will be waiting for your message 🙂