edits from Omar's review

This commit is contained in:
Deborah Barnard
2024-05-07 09:32:43 +01:00
parent 0c13d01611
commit 7ffceda258
4 changed files with 6 additions and 11 deletions

View File

@@ -25,7 +25,7 @@ n8n may display a warning about overriding local changes. Select **Pull and over
### Workflow and credential owner may change on pull
When you pull from Git to an n8n instance, the workflow or credential owner may change.
When you pull from Git to an n8n instance, n8n tries to assign workflows and credentials to a matching user or project.
If the original owner is a user:

View File

@@ -7,11 +7,7 @@ description: Set up and use role-based access control (RBAC) in n8n.
# Role-based access control (RBAC)
/// info | Feature availability
RBAC is available on all plans except the Community edition. Different plans have different numbers of projects and roles:
* Starter: one project, with admin role.
* Pro: three projects, with admin and editor roles.
* Enterprise: unlimited projects, with admin, editor, and viewer roles.
RBAC is available on all plans except the Community edition. Different plans have different numbers of projects and roles. Refer to n8n's [pricing page](https://n8n.io/pricing/){:target=_blank .external-link} for plan details.
///
/// note | Role types and account types

View File

@@ -5,11 +5,7 @@ description: Understand how n8n uses project for RBAC. Learn how to create and m
---
/// info | Feature availability
RBAC is available on all plans except the Community edition. Different plans have different numbers of projects and roles:
* Starter: one project, with admin role.
* Pro: three projects, with admin and editor roles.
* Enterprise: unlimited projects, with admin and editor roles.
RBAC is available on all plans except the Community edition. Different plans have different numbers of projects and roles. Refer to n8n's [pricing page](https://n8n.io/pricing/){:target=_blank .external-link} for plan details.
///
n8n uses projects to group workflows and credentials, and assigns [roles](/user-management/rbac/role-types/) to users in each project. This means that a single user can have different roles in different projects, giving them different levels of access.
@@ -26,6 +22,8 @@ To create a project:
## Add and remove users in a project
Project admins can add and remove users.
To add a user to a project:
1. Select the project.

View File

@@ -27,6 +27,7 @@ You can browse and search workflows on the **Workflows** list. The workflows in
* **Home** lists all workflows you can access. This includes:
* Your own workflows.
* Workflows shared with you.
* Workflows in projects you're a member of.
* If you log in as the instance owner or admin: all workflows in the instance.
* Other projects: all workflows in the project.