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

Discussion

Posted to Laserfiche Cloud

Discussion

Feature Request: Safer Default Starting Form Privacy for New Business Processes

posted on September 24

When creating a new Business Process in Laserfiche Cloud, the Starting Form Privacy appears to default to Public when the process is first published.

For organizations that have external users in their Laserfiche Cloud environment, I think this creates an unnecessary security/privacy risk.

We create a large number of business processes, and each time a new process is created, the designer has to remember to configure the Starting Form Privacy appropriately. In our environment, we have external users alongside our internal users, so we need to be especially careful that a newly created process isn't accessible to users who shouldn't have access to it.

A form could potentially contain sensitive or internal information, and forgetting to configure this setting on a newly created process could expose that form more broadly than intended.

I think it would be safer if new processes followed a more restrictive default. For example, Laserfiche could:

  • Default new processes to Private, potentially requiring the designer to explicitly configure who can start the process.
  • Prompt the designer during the initial publish to review/configure Starting Form Privacy before publishing.

I'm not necessarily advocating for a specific implementation, as Laserfiche may have a better approach. The main request is to avoid having the least restrictive option be the default and relying on every process designer to remember to change it.

For organizations that create many processes and have external users in the same Laserfiche Cloud environment, this becomes something that is very easy to overlook and potentially has significant privacy risks.

4 0
replied on September 30

Hi Jose,

When you first create a Business Process, it already defaults to Private but as allow all registered users to start this process which would include any registered users in your Cloud account:

Can you elaborate further if the "public" that you are referring to above is the "Public: Users can access the starting form of this process without signing in" or a different definition? I noticed you mention you have external users along with your internal users and thus I'm assuming you may be asking not for the very first option in my screenshot but under Private, "Allow specific users, teams, or groups to start this process"

 

Thanks!

0 0
replied on September 30

Hey Tessa! Yes, I should have specified that better. You're correct that it defaults to Private. The concern is that within Private, it also defaults to “Allow all registered users to start this process.”

In our environment, we onboard external users with more restricted roles, so “all registered users” can include users we wouldn't necessarily want starting a newly created process. Because of that, there's a risk that a process designer could publish a new process without realizing that the default includes those external registered users.

Thank you!

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

Sign in to reply to this post.