Projects and Project Permissions in webMethods Integration Cloud

Projects

A project is an independent entity and corresponds to a folder for organizing your assets. A project holds all the assets created as a part of that project by the logged-in user, along with the configurations associated with the assets. Any asset, for example, Integrations, REST APIs, SOAP APIs, Document Types, and Reference Data, is a part of a project.
If you are an existing tenant, your assets will be available in the Default project. You cannot delete this default project. If you are a new tenant, the Default project is not available and you need to create a new project. Once you log in, click Projects > + New Project to create a new project.
 

Project Permissions

Project permissions are used to associate permissions with projects. Integration Cloud provides a system-generated Developer project permission profile in your tenant. Any new project created is automatically associated with the Developer project permission profile. This profile has permissions to create, update, delete, and execute all assets. You cannot edit or delete this system-generated project permission profile. If a project permission profile is associated with a user on the user profile page, the user can perform only the permitted tasks in the mapped project.
 
You can associate permissions with projects from the Settings > Project Permissions > Add New Project Permission page.

If you are an existing tenant:

  • Your user's Access Profile controls global permissions as well as permissions for the Default project.
  • Your user's Project Permissions profile control permissions for other projects.
  • All existing user profiles will be associated with the Developer project permission profile.
  • All projects created have the Developer project permission profile associated with it.
  • All existing assets will be available in the Default project.
  • Manage the permissions for existing assets inside the Default project from the Project Permissions for Default Project section under Settings > Access Profiles > Administrative Permissions.
  • Manage the permissions for new assets created inside the Default project from the Project Permissions for Default Project section under Settings > Access Profiles > Administrative Permissions.
  • If you create a new project, you have to assign the project permissions from the Settings > Project Permissions > Add New Project Permission page.

If you are a new tenant:

  • The Default project is not available. There are no existing assets. Your user's Access Profile controls only global permissions.
  • The Administrator will be associated with the Developer project permission profile and can assign a project permission profile to a new user.
  • All projects created have the Developer project permission profile associated with it.
  • If you create a new project, you have to assign the project permissions from the Settings > Project Permissions > Add New Project Permission page.

Example 1

A user is assigned to two project permission profiles A and B in the user profile. Project permission profile A has the Execute Integration permission in Project X but Project permission profile B does not have the Execute Integration permission for the same Project X. The user will still be able to execute the Integration.

Example 2

In this example, we will see how you can allow an existing user U1 to create, update, delete, and execute Integrations for Project P1 but not for Project P2.
1. You must have the Access Control permission under Access Profiles > Administrative Permissions.
2. Create Project P1 and Project P2.
3. Create a new Project Permission profile PP1 under Settings > Project Permissions > Add New Project Permission.
4. On the Add New Project Permission page, add Project P1 in the mapped projects list. Assign the create, update, delete, and execute Integration permissions to the mapped Project P1.
5. Do not map Project P2.
6. Go to the Basic tab of user U1 and select only PP1.
So when U1 logs in, U1 will only be able to create, update, delete, and execute Integrations for the Project P1 but not for Project P2.

image.png