Skip to content
Snippets Groups Projects
Commit 0328b936 authored by Jared Kosanovic's avatar Jared Kosanovic
Browse files

Add best practices containing project structure and permissions recommendations

parent 22524f13
No related branches found
No related tags found
1 merge request!7Add best practices containing project structure and permissions recommendations
*.idea
.vscode
\ No newline at end of file
.vscode
.DS_Store
# Best Practices
Here are some recommended best practices for designing integrations in IICS.
## Working In a Shared Environment
UW-Madison operates under a single shared IICS org for each environment (test and production).
This means that you might see other objects in IICS, such as projects, connections, and schedules, that belong to other areas of the university.
### 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.**
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)
1. Click "Add" to add bring up the group selection menu. ![Project permissions menu without group](./images/add-group.png)
1. Select the group for your team and click "Add". ![Group selection menu](./images/select-group.png)
1. Click the check boxes for Read, Update, Delete, Execute, and Change Permission. ![Project permissions menu with permissions applied.](./images/apply-permissions.png)
1. Click Save.
### Namespace Projects With Your Group Name
Even though you might not have any permissions on a project, you are still able to see that the project exists when exploring all projects.
To help organize the constantly growing list of projects, we recommend that you to prefix your group name before the name of the project: `{group name} - {project name}`
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
docs/images/add-group.png

163 KiB

docs/images/apply-permissions.png

153 KiB

docs/images/right-click-permissions.png

59.1 KiB

docs/images/select-group.png

152 KiB

0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment