diff --git a/docs/best-practices/shared-environment.md b/docs/best-practices/shared-environment.md index cd399e95b5584cb0f6d0d318c89369aaa1819918..9320b76c839e842fba3414cc7b272c3b71abda89 100644 --- a/docs/best-practices/shared-environment.md +++ b/docs/best-practices/shared-environment.md @@ -9,10 +9,10 @@ When you create a new project, make sure you edit the permissions to limit who c **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.** 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..."  -1. Click "Add" to add bring up the group selection menu.  -1. Select the group for your team and click "Add".  -1. Click the check boxes for Read, Update, Delete, Execute, and Change Permission.  +1. Right-click on a project folder and click "Permissions..."  +1. Click "Add" to add bring up the group selection menu.  +1. Select the group for your team and click "Add".  +1. Click the check boxes for Read, Update, Delete, Execute, and Change Permission.  1. Click Save. ## Namespace Projects With Your Group Name @@ -25,4 +25,4 @@ Example: "DoIT-AIS-Enterprise-Integration - Salesforce Integrations" This structure allows you to search your group name in the project explorer to only see a list of your group's projects. You can create subfolders within a project if further organization/hierarchy is needed. -Your group name was sent when you were granted access to IICS and you can find the name of your group by editing the permissions for a project. \ No newline at end of file +Your group name was sent when you were granted access to IICS and you can find the name of your group by editing the permissions for a project.