Troubleshooting: Why Can I Not Start an Instance? / Access to Start Event is Missing

  • Updated

If a user does not have the ability to start an event, there are a few solutions to fix the problem.  

To try the solutions in this article, you will need to have Admin user rights.  

Where can I find the start instance link?

You can start an instance either via Start new instance in the dropdown (Image 1), via the space start page (Image 2), and if the right configuration is done, you can also start instances from the List page (Image 3).

Image 1


Image 2 


Image 3

The user cannot start an instance

Does the user have access to the start event? 

Check if the user has Run permissions and which groups they belong to. 

1. Navigate to space settings and select the Members tab. Select the download button on the right side

2. This will download an excel file where you can view the space members and the groups and permissions they have.  

The excel file will contain more information; this excel file was edited for the purpose of this article.

Check which role can start the process

1. One of the main reasons why a user cannot access a start event is because they are not part of the users who are configured to start the event. Navigate to the process model of the application and go to the swim lane where the start event is located.  

2. Double-click on the user icon to see what roles are configured for this lane.  

Check the configuration for the deployed version of the process.  

1. Go to the version panel, click on the deployed version, and then select Deploy.  

2. This will bring up the configuring users window where you can see if the user or group belongs to the role that is assigned to the start event.  

3. To check if your user is in the group* configured to perform the start event tasks, navigate to the Groups tab under space settings.

Make sure the group assigned to the task is the correct group. It could be that there are multiple groups with similar names such as a parent group and a subgroup. Double-check that the correct group is assigned to the role and that the user is in the appropriate group.

The second option for checking group* configuration is to go to Participant configuration and check the users configured to the individual roles. Learn more in the article, Configure Task View.  

We strongly suggest that if the user you are looking for is not listed here that you do not just add them to the role, instead check if they are listed in the group* listed and add them there if they need to be added to the process. Learn how to add users to a group in the article, Create and Administrate Groups.  

* We strongly suggest setting up permissions with groups instead of adding individual users.

Is there an empty group on start-up?  

It will not be possible to start the instance if the group that is assigned to the role where the start event is located is empty. To fix this, add users to the group or assign a different group to the role.   



How to add a user to a group  

There are two ways to add a user to a group.   

Navigate to the Group tab under Space Settings. Select the group you would like to add the user to and then click on Add user to group.  


You can also navigate to the Members tab under Space Settings. Click on the name of the user you would like to add to a group. In the Edit user window, write the name of the group you would like to add the user to. Click on the group when it pops-up in the drop-down menu and then select the plus sign +.  

If you have tried the solutions in this article and the error is not fixed, report the problem to Please include the URL, a screenshot, and an explanation of the error along with the solutions you have tried. 



Was this article helpful?

0 out of 0 found this helpful



Article is closed for comments.