You are viewing limited content. For full access, please sign in.

Question

Question

How to properly assign users or teams to projects

asked on January 5 Show version history

Hi,

Since BPs don't have access rights in the Cloud and to not have all BPs in Global team, I am trying to use Projects to narrow down BPs that can be started/viewed by departments/teams. 


Below is the Test project that shows for me, an admin in the home page.

I added a coworker and tested with him.


 

He sees this:



So, what I understand so far is that projects have to be created within Teams/Global. So, shouldn't the team member(s)(Participant license) be allowed to view the Project in The home page: https://app.laserfiche.com/home ?

I've been testing it with Alex and the only team(project) that shows is the Global team. The Test team doesn't show for him. I even tried doing the External Project access. It still wouldn't show for him. We tried adding the the whole team into the external access to see if that would work, it didn't.

My question, is what am I missing?
My goal is to have BPs narrowed by team, which we can only do by projects within Teams/Global in LF Cloud.

 

Added: What I also forgot to mention is that he sees only the Global team but is able to view the business processes that are exclusive to Test(project). We confirmed this by me disabling a process. It disappeared.

 

0 0

Answer

SELECTED ANSWER
replied on February 6

Hi Steve,

Thank you for explaining the starting form privacy and the external project access. I wasn't aware about the rules/workflows either.

For anyone interested:

I wanted to come back to this as I notice a Public form will show as an option to start if you just have Global, which makes sense. Not a big deal but if you about using Starting form privacy by narrowing it down to a team, public forms will always show.

I tried to figure out my initial question about how to get a participant user who is assigned to a team inside a project to have the ability to select the team. 
As you can see, the ability to select a team is not available. 

I tried looking at the license types but was not able to determine if that may be the cause.

After looking at the Projects page, I noticed this:

Since participant license users don't have access to Process Automation, that's why a project/team won't be available to be selected. I confirmed this by assigning the full user license to the same account. Gave enough access to almost everything except process automation:


With the full user account, I confirmed that the ability to Select Team is not available. I then switched it to Allow and was able to select the team. I would kindly suggest that this is pointed out in the Projects page for future users who are interested in using projects. 
 

 

0 0

Replies

replied on January 5

I wanted to add, for the Business processes that do have a Message Start Event, I found that you can narrow it down by team.


For my issue, I have scheduled forms that worked on-prem and had Event Starts

So, the only solution I thought of was to modify event start forms by replacing them with Message Start Events and adding them to a Project (team)...

But since I just found out message start event forms can be narrowed down by teams or groups, I think I will drop the project method. I will just have to rename the BP since there cannot be duplicate BP names.

I still would like to know how Projects are supposed to be work as we couldn't get the project name to show up.. 
 

0 0
replied on January 5

Hi Jasciel, If you put the BP in a Project, it is still only limited by the Starting Form Privacy as you assigned in the picture above, by Team or User. So even though it is in the Global area, it is limited to those in the Team. The External Project access is limiting who can see the Project resources to edit, not to run the process.

FYI, there are currently some design considerations that have to be taken into account before attempting to use Projects, especially around the use of Workflow. Currently, Workflow has the following restrictions: A Workflow cannot Invoke a BP that is within a Project (the BP must be in the Global area), the Run Rule activity in a workflow does not see Rules created inside a Project. A Rule created in the Global area, cannot use a data lookup table source that is inside a project. These may require you to continue to build your processes in the global area until addressed by Laserfiche.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.