From 15e038cdab49fab33c6b698d228b67e38aa043bb Mon Sep 17 00:00:00 2001
From: Rebecca Wheeler <rebecca.wheeler@wisc.edu>
Date: Thu, 26 Jan 2023 11:32:07 -0600
Subject: [PATCH] Update docs/tutorials/README.md,
 docs/best-practices/shared-environment.md

---
 docs/best-practices/shared-environment.md  | 2 +-
 docs/{tutorials.md => tutorials/README.md} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename docs/{tutorials.md => tutorials/README.md} (100%)

diff --git a/docs/best-practices/shared-environment.md b/docs/best-practices/shared-environment.md
index 9320b76..0df982a 100644
--- a/docs/best-practices/shared-environment.md
+++ b/docs/best-practices/shared-environment.md
@@ -6,7 +6,7 @@ This means that you might see other objects in IICS, such as projects, connectio
 ## Use User Groups to Control Access
 
 When you create a new project, make sure you edit the permissions to limit who can view and change the assets within the project.
-**If no permissions are configured on a project or the assets within it, anybody who has access to IICS will be able to view, change, run, and delete the contents of the project.**
+**If no permissions are configured on a project or the assets within it, anybody who has access to IICS will be able to view, change, run, and delete the contents of the project. If ONE specified user has permissions on the project or asset, NO OTHER PERSON can view, change, run or delete the contents.**
 Use the group that was sent when you were granted access to IICS to control who can access the contents of the project.
 
 1. Right-click on a project folder and click "Permissions..." ![Project right-click menu](images/right-click-permissions.png)
diff --git a/docs/tutorials.md b/docs/tutorials/README.md
similarity index 100%
rename from docs/tutorials.md
rename to docs/tutorials/README.md
-- 
GitLab