How can I fix user permission issues in Pipelines?
| Cause | User interface error | CLI error |
|---|
| A job started manually by a user who is part of the organization but does not have the “execute pipelines” permission | Failed to start pipeline:
Error message: You do not have permission to run pipelines.
| [Acquia\Pipeline\Exception\PipelineClientException]
There was a server error.
Please try your request again in a few minutes.
|
| A job started manually by a user who is no longer part of the organization | Not applicable, as the user cannot access the user interface. | [Acquia\Pipeline\Exception\PipelineClientException]
There was a server error.
Please try your request again in a few minutes.
|
| A job started through a webhook with a stored credential of a user who is currently part of the organization but does not have the “execute pipelines” permission. | Not applicable, as the job cannot start. | webhook start failed to start pipeline for app [UUID].
Operation failed with the following details:
Error message: You do not have permission to run pipelines
|
| A job started through a webhook with a stored credential of a user who is no longer part of the organization | Not applicable, as the job cannot start. | webhook start failed to start pipeline for app [UUID].
Operation failed with the following details:
Error message: You do not have permission to run pipelines
|
Pipelines executes jobs using the credentials of the user who first executes a Pipelines build. If this user leaves your organization, or the user’s credentials are revoked, you may be able to start a manual build, but automated builds may fail with errors like the following:
The application you are trying to access does not exist, or you do not have permission to access it.
You can manually reset the credentials for the application.
Any user with the Execute Pipelines permission can reconfigure automated builds. For additional assistance, contact Acquia Support.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.