Control · Users and Roles
The right person sees the right case, fields and buttons
Control works on four layers — who you are, what you may open, what you must do and what you may touch — at every step, on every device.
Users and Roles decide who sees which case, field and button at every workflow step. The server enforces the same rules the screen shows.
Connected through the AI Integration Engine
Control integration permissions
Assign separate permissions for viewing connections, editing settings, publishing changes, managing passwords and keys, and running operational tasks. Approvers are selected from the reporting line. For provider-version promotion and reverts, the maker cannot approve their own request, and the final approver publishes it. Flow publishing and saves to logical operations or provider groups are direct actions for authorised users in this release.
Company sign-in and access
Set single sign-on and authenticator policy per company, with secure sign-in on Android and access denied by default.
A clear permission catalogue
Choose what a role can do from a read-only catalogue of 32 company permissions. The platform defines each permission with a plain description. Areas include Integrations, AI Core, Environment, Users and access, Company settings, Design and Operations.
Permissions reach people only through roles. Choosing a higher permission automatically ticks the permissions it includes. You can only grant permissions you hold. Separation-of-duty warnings flag risky pairs, such as designing and approving. DynamicForm logs every change to a role's permissions.
Start by copying Integration Designer, Integration Approver, Integration Operator or Auditor. Review the copied permissions against the work that role needs.
Review the whole role
See responsibilities, application access and records together. The role page has Permissions, Application access and Data scope. Application access has a tab for each application, where you choose the menus that role can reach.
A role can reach menus in several applications. Menus follow permissions consistently on the web, on Android and offline. Application choices remain clear without recreating the role for each application.
Choose Own, Team, Branch or All for record scope. Own covers records the user created. Team covers their own records and those of everyone below them in the reporting line. Branch covers records of the user's own branches. All covers every record of the company. Review these choices with permissions to understand the role's reach. Explore Company Admin for shared users, organisation details and access administration.
Confirm roles and access
Roles come from the requirement document or a person. AI-suggested roles need confirmation, and every role has something to do. Near-duplicate role names always prompt a question.
Screen permissions can be taken from the document's permission table. Every screen has roles unless an administrator-only exception has been approved.
Where branch-aware workflow steps are chosen, users see and act only on tasks for records in their own branch. Access covering all branches allows a wider scope. Review these choices alongside the responsibilities described in the document. Roles in use cannot be deleted.
Build your first app free
All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.
Explore DynamicForm
Company Admin · Applications · AI Core · Security and identity · Compliance · Rules and calculations
Updated 16 November 2026