Setting up Sites for Automation Server

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Sites >

Setting up Sites for Automation Server


Sites uses Bizagi's OData layer to obtain context data for the stakeholders. When you're using Sites in your Test and Production environments, you need to add Sites as an OAuth Application and add the keys to Sites for security.


What you need to do

To set up Bizagi Sites on your Testing and Production environments follow these steps:


Add Sites as an OAuth Application

Log in to the Work Portal and click the OAuth2 Applications option available under the Admin menu to grant access to Sites.




Click the option to add a new record in this table:




Define the application as follows:

Name: Sites

Grant type: All

Web Site: Sites

Allowed Scope: API, LOGIN

User: select a user that is allowed to access Bizagi Sites.

Redirect strategy: Web application.

Redirect URI: You must add the Sites Editor and the Sites root (the URL to Sites Editor without editor.html) URLs separated by a semicolon (;). The table below shows how to build the URI based on your Work Portal URL.




Automation Server


Automation Service



Token lifetime: Define the number of minutes for which a same token is valid and can be reused for another invocation. An usual or recommended setting should consider not exceeding 30 minutes. When the value is set to 0, the token never expires.




Once you are done, click Save.




Copy the access keys once the application is registered, the Client Id and Client Secret keys are essential to finish configuring your environment.


Add OAuth keys to Sites appsettings file

Now that you have the Client Id and Client Secret for Bizagi Sites, find the sites appsettings.json file located by default in the following path:



Open the file in a text editor and replace the following keys with either Client Id or Client Secret value as the table specifies:





Client Id


Client Secret


Client Id


Client Secret


Client Id


Client Secret