Merge pull request #1942 from n8n-io/pay-1403-update-owner-permissions

Small docs update to explain additional permissions for instance owners/admins
This commit is contained in:
Deborah 2024-03-04 08:52:52 +00:00 committed by GitHub
commit e973ab8c65
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 7 additions and 1 deletions

View File

@ -70,3 +70,9 @@ For example, you have two n8n instances, one for development and one for product
### Infisical version changes
Infisical version upgrades can introduce problems connecting to n8n. If your Infisical connection stops working, check if there was a recent version change. If so, report the issue to help@n8n.io.
### Only set external secrets on credentials owned by an instance owner or admin
Due to the permissions that instance owners and admins have, it's possible for owners and admins to update credentials owned by another user with a secrets expression. This will appear to work in preview for an instance owner or admin, but the secret won't resolve when the workflow runs in production.
Only use external secrets for credentials that are owned by an instance admin or owner. This ensures they resolve correctly in production.

View File

@ -16,7 +16,7 @@ To use admin accounts, you need a pro or enterprise plan.
* Add and remove users, including admin users
* Upgrade members to admin, and downgrade admins to member
* See and share all workflows
* See and share all credentials (but not see the sensitive information)
* See, edit, and share all credentials (but not see the sensitive information)
* Delete tags
* Set up and use [Source control](/source-control-environments/)
* Admin: elevated permissions within the app.