Skip to content

Update contend.md #1241

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Aug 3, 2023
Merged

Update contend.md #1241

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c55e250
Update contend.md
Fr4ng Aug 3, 2023
e658695
Updated according to reviewer's feedback: sentence removed
Fr4ng Aug 3, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/arduino-cloud/01.getting-started/09.arduino-cloud-for-business/contend.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,8 @@ There you will find the complete list of all members who have access to your Sha

There are multiple role types in Arduino Cloud for Business to allow the admin to have full control of the rights/permissions each user has in the Shared Space. In this way, the admin can set up Role-Based-Access-Control (RBAC) by assigning profiles and sharing with any number of users.

By default the member who has activated the plan and created the workspace is set as Admin. The Role-Based-Access-Control can support multiple Admins with same permissions.

The table below reports the list of supported roles and corresponding permissions.

| | Admin | Editor | Service Account |
Expand All @@ -138,8 +140,6 @@ The table below reports the list of supported roles and corresponding permission

\[1\] It can add/remove only Editors.

Thus, the only role with full permissions is the *Admin*, which corresponds to the owner of the Arduino Cloud for Business plan.

In addition to editor role, we added a Service Account, which should be one dedicated to the creation and maintenance of API Keys Tokens. We recommend having at least one Service Account for each Shared Space and linking it to a non-personal email account. In this way, API Keys do not risk getting lost with the cancellation of a personal email address.

#### Add A New Member
Expand Down