Config Newton: Where to Start with your Agentic Builder
Config Newton is a chat assistant that configures your Risk Cloud environment. You can describe what you want, it will propose an implementation plan, and once you approve the plan Config Newton will make the changes.
This guide will help you get the most out of Config Newton by providing examples of how you can collaborate with the agent. It also outlines areas where Config Newton is still being improved and may need additional verification.
It's best to think of Config Newton as being able to help you in three roles: Advisor, Builder, and Collaborator.
As an Advisor, the agent reviews your applications and makes recommendations. It can Look at application health, maturity, and conduct design checks. Config Newton can also analyze trends in records and conduct an AI opportunity analysis.
As a Builder, Config Newton plans and configures Risk Cloud, turning your requirements into a build plan, executing it across workflows, fields, jobs, and more. The agent will provide a blueprint for review before taking action, and checks in if it has questions or needs clarification.
As a Collaborator, you can prompt the agent to help with documentation and teaching. Ask Config Newton how a job does or what a workflow represents and it can summarize the object. You can use the agent as a collaborator to generate administrator and end user guides, training materials, or notes for your team.
Recommended Use Cases
Review an existing application
Ask Config Newton for a “health check” or “design review” of any application. Config Newton will look at all the Risk Cloud objects that make up that application, from the workflows down to the fields, and shares it’s findings based on LogicGate’s design best practices.
Try: “Do a design review on our Vendor Risk application”
Build a new workflow
Describe a your organization’s process for a GRC program and Config Newton will draft the workflow, steps, fields, and connect them all with paths, allowing you to create an entire application from plain language.
Try: “Build an intake workflow for policy exceptions with three phases: Submit, Review, and Approved.”
Update existing workflows or steps
Add or rename steps, connect them with paths, set who gets assigned at a decision, and add fields to a step's form. Edits are made to the specific step or path you name, and Config Newton checks the path condition you described against the one in Risk Cloud before changing it.
Try: "Add a Legal Review step between Review and Approve." or "Add a Risk Rating field to the Assessment form, under a new section called Scoring."
Create table and visual reports and dashboards
Build table and visual reports from a description by describing the data you want and the format you’d like to see it presented in or add existing reports to a dashboard.
Try: "Create a table report of open findings with owner and due date."
Creating new jobs
Describe an automation and Config Newton builds the trigger, actions, and conditions.
Try: "When Status changes to Approved, move the record to Closed."
Trust But Verify: Developing Use Cases
We're continuing to expand and improve Config Newton's capabilities. Below are activities the agent is capable of, but we encourage you to validate the outputs. A simple framework that covers most of these scenarios:
Ask Config Newton for a plan and read it before approving.
After it makes changes, ask: "Re-read it and tell me what's there now."
Open the object it built in Risk Cloud, and inspect the changes.
Large or multi-part changes
Requests that touch many fields, sections or steps can finish partway. Config Newton reports what it completed and what it did not. Extremely large requests may be slow or may not finish.
Path conditions and assignments
Conditions need a value that maps clearly to the field. Config Newton should ask for clarification rather than guess
Deleting objects
Config Newton will typically ask you to delete objects manually to ensure there are no mistakes. For lower risk items that it may delete, Config Newton should always ask for confirmation before deleting anything. However it may not advise you of the effects. We recommend asking what a change with affect before approving it whether you or Config Newton will execute the deletion.
Analyzing the impact of Role and Permission Set changes
Config Newton can modify these objects, but may not be able to fully detail the affects of the change due to overlapping Roles or Permission Sets in your environment. You may want to ask it to analyze the related environment, application, or workflow first.
What Config Newton Can't Do Yet
Config Newton helps you build and adjust how your Risk Cloud environment is set up. It doesn't cover everything you can do in Risk Cloud today. When you ask for something it can't do, it should say so. You can then make that change directly in Risk Cloud.
Your data
- Config Newton can't add or change records. It sets up the workflows, fields, and forms that hold your data, but it doesn't enter or edit the data. Use Risk Cloud or an import for that.
- It can't test a workflow for you. While it can explain a process, it can't submit a record or walk one through your steps. After it builds something, run a test record yourself.
Workflows, steps, and paths
- Path conditions are simple. Each path can have one condition. For conditions that combine rules ("and" / "or") or use system information, set them up in Risk Cloud. To change other path settings, edit the path in Risk Cloud.
- Assignment is limited. Config Newton can assign the person named in a user field on the record. It can't assign a specific person or a role. If you build a whole workflow in one request, plan to set assignments afterward.
- It can't set step due dates or SLAs or change a workflow's map layout.
Fields and forms
- Some field types aren't available to it. If it can't create the type you need, add that field in Risk Cloud.
- It can rename and reword fields and change their options and formulas. It can't change a field's rules, such as required formats, default values, unique values, number or currency display, or date limits. It also can't change a field's type, and it can't delete or archive fields.
- Some form sections are off limits, including those that show a dashboard, a visual report, or a Jira link. Settings on sections that link workflows (such as required, bulk create, and search) also need to be changed in Risk Cloud.
Jobs (automations)
- Config Newton can build many common jobs, not all of them. Jobs that send webhooks or Teams messages, or create Automated Evidence Collections still need to be created by a user.
- It can't delete, pause, or resume jobs.
Reports and dashboards
- Chart formatting is limited. Legends, number formats, sorting, and filters set on a chart need to be done in Risk Cloud, and a chart can't be pointed at a different report after it's created.
- Dashboard settings are manual. Filters, sharing, home screen placement, and color or icon are set in Risk Cloud.
Outside Config Newton's reach
Some aspects of Risk Cloud are best left to a human, especially those that are high risk or require external systems. Config Newton currently cannot:
- Delete most objects: Instead of deleting objects, Config Newton will instruct a user on how to take that action from within Risk Cloud.
- Configure Integrations: Set up of integrations that connect to Risk Cloud require a user.
- Manage people and access: Adding, inviting, or disabling users, and managing groups need to be done by an administrator.
- Manage your environment: Syncing data from a production environment must be initiated by n administrator.
- Take action on whole applications: Copying, exporting or importing via json, and deleting applications must be done by a builder.