The table below provides details about the three OIT-maintained Kuali Build environments at Duke. With few exceptions, Kuali Build developers work only in the production environment. 

If your Kuali Build app requires support in the sandbox/staging environment due to an extended development life cycle or the need for version control, contact kualibuild@duke.edu. The Kuali Build service management team will grant you access to the sandbox environment and work with you to migrate the app to the staging/production environments upon request.

Kuali Build Feature/Function 

Production
duke.kualibuild.com 

Sandbox
duke-sbx.kualibuild.com 

Staging
duke-stg.kualibuild.com

Users
(can use Kuali Build, i.e. complete tasks, but cannot create apps)

Automatically provisioned with account upon login

Automatically provisioned with account upon login

Automatically provisioned with account upon login

Developers 
(can create apps, i.e. publish forms and workflows - but not integrations unless granted specific permissions (see Integrations below) 

Upon request via Kuali Build Developer Account Request

Upon request

Upon request

Spaces
(brand-able and configurable “containers” in Kuali Build for apps belonging to department/functional area)

Space and Space Administrator access granted to app developers upon request

Space and Space Administrator access granted to app developers upon request

Developers granted same access as in Sandbox

Groups (see KB0036605)

Upon request; app developers can administer native Kuali Build groups

Upon request; app developers can administer native Kuali Build groups

Upon request; app developers can administer native Kuali Build groups

API Integrations
(high-level developer — “integrator” — access to write apps that connect Kuali Build to other applications) 

Only the OIT Automation Team can develop in — or move API integrations to — the production environment.

Available to Space Administrators by default.

 

The Kuali Build service management team may grant permission to native Kuali Build Group Administrators to develop API integrations in the sandbox environment.

 

Upon request, API integrations written in this environment are reviewed by the OIT Automation team before being moved to production.

Upon request, the OIT Automation Team can add API integrations written by developers to the staging environment.

Apps
(entire Kuali Build application, including the form, workflow, and any integrations)

Most apps are developed and launched in this environment.

 

Version control is coming soon.

Request use of the sandbox environment when your app requires an extended development period/version control.

 

Upon request, OIT will move an app (and any API integrations) from sandbox to staging and production (via an app in development).

 

When moving an app from sandbox to staging/production:

 

  • Spaces and Space administrators will be recreated

  • Any Kuali Build Groups will be recreated

  • Any Group Manager synced groups will be recreated

Staging is used in preparation for moving apps to production.