Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default error workflow via env #3421

Closed
wants to merge 1 commit into from
Closed

Default error workflow via env #3421

wants to merge 1 commit into from

Conversation

rfehling-mittwald
Copy link

@CLAassistant
Copy link

CLAassistant commented Jun 2, 2022

CLA assistant check
All committers have signed the CLA.

@n8n-assistant n8n-assistant bot added community Authored by a community member core Enhancement outside /nodes-base and /editor-ui labels Jun 2, 2022
@janober
Copy link
Member

janober commented Jun 2, 2022

Thank you very much for your contribution. is very appreciated! But as n8n now has support for different users, is it now sadly a little bit more complicated. After all, will not all users have access to all workflows anymore.

@rfehling-mittwald
Copy link
Author

But an error workflow should not have any ACL, right?

Guess its possible to check if the linked workflow has an error trigger.
Or just forbid to set restrictions when an workflow has an error trigger/is linked as error workflow?

We are currently not very deep in user handling 😅

@janober
Copy link
Member

janober commented Jun 2, 2022

For sure possible but not sure if that is how it should work. Would have def. been something we could have merged pre-user-management quite fast but now needs for sure some proper thinking and planning.

@fcecagno
Copy link
Contributor

Hi @janober would it be possible to have this solution when user management is disabled (while there's a definitive solution that works with user management enabled)?

@neoromantic
Copy link

@janober Could we take a second look on this problem? Seems like @fcecagno suggestion is reasonable?

@rfehling-mittwald rfehling-mittwald closed this by deleting the head repository Feb 20, 2023
@dkindlund
Copy link

@janober , can an n8n specify a workflow to be globally visible to all users and then make that one the default error workflow? Like, don't let other users alter that workflow, but make it sort of "read-only". Would that solve this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Authored by a community member core Enhancement outside /nodes-base and /editor-ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants