We’d have a lot of different capabilities in IBM Cloud Pak for Business Automation. You can create many kinds of materials and save data in different catalogs. But some time it’s hard for us to know what access should granted to use certain functions, create, or publish some applications. This article wants to help on this area. And this article applies for production install.

First, I will describe the configuration points and repositories. Within a production workflow authoring install. There will be several components (capabilities) installed which have different repository and access controls.

Platform UI (https://www.ibm.com/docs/en/cloud-paks/1.0?topic=services-platform-ui).

The platform UI is the main entrance for all designers. Depends on the version you used. For 21.0.2 you need login with a predefined user with admin access to add LDAP and users/groups you want to use this system. This process can be done with the BA Studio post deployment tasks guide(https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=tasks-business-automation-studio). Please pay attention that in this step. You must onboard users you settled in custom resource for bastudio, workflow authoring and application engine to make sure the default admins for those components can visit system. Also don’t forget the app login user you assigned in FNCM secret.

After you login platform UI (Cloud Pak Dashboard) with correct user. You will find at least 3 links in menu.
under Design
    Business applications
    Business automations
under Administration.
    Repository and registry access 

 
Business applications

To visit Business applications and create applications. The user must have authoring access for application.
If you want to admin the applications. You must have administrator access for that.
The access can be added in Process Admin for BA Studio. You can visit that in path below. First, you need login with a user have admin access to BA Studio already. That can be the user you input in Custom Resource under bastudio section. Then open Repository and registry access, click the Process Admin Console link in this page. In the new page opened, expend User Management in left menu. Click Group Management. Search tw_authors or tw_admins based on what kind of user you want to add. Click the search result. Then click add Users to add the user you want to use.  Please pay attention that. Please don’t remove the function id from the list. That will break system functions.

 
Business Automations (Workflow)

To visit the workflow process and create workflow automation. The user must have authoring access for workflow. If you want to admin the workflow automations. You must have administrator access. This process is like the Business applications. But in different location. You need open workflow authoring process admin. The link can be found in following path. First, you need login with a user have admin access to workflow automations already. Usually that will be the user you input in custom resource under workflow authoring section. Click Business automations, in page opened click Workflow and click Administration. In the Administration view. Click Process Admin Console. In the page opened follow the same process to add users to tw_authors and tw_admins.

Case

Within workflow automation. There is another feature called Case. If your workflow automation contains Case functions. Then beside the normal repository access you granted. You need assign extra access to your user to reach the project area.  First, you need login with a user have admin access to workflow automations already. Usually that will be the user you input in custom resource under workflow authoring section. Click Business automations, in page opened click Workflow and click Administration. In the Administration view. Click Case administration client.  In the new page opened. You can manage the Project Area access with Actions View and Edit. The user you used should have Content admin access as well to modify that. Usually if you assigned the same user for the app login user in FNCM secret and user under workflow authoring. Then the user will grant that access directly. Otherwise, you need login to Filenet Content Manager acce first to manage the access and add more users. In this article I may not include the details for that. You can find FNCM access details in Knowledge center documents (https://www.ibm.com/docs/en/filenet-p8-platform/5.5.x)