Rols

Assigna usuaris i grups a rols, i defineix què pot fer cada rol.

  1. L’atribut roles
  2. El rol default
  3. Objecte Role
  4. Opcions de rol

L’atribut roles

La llista roles de primer nivell de config.yaml:

Atribut Comentaris
roles
array

Roles
🔗 valid role object

The roles provide RBAC. Each role has a name and 1 or more groups (local, ldap or entraid). The admin and default roles are mandatory (public is the old name of default, and still works).
Since version 4.0.11 you can also add users (local, ldap or entraid).
Since version 5.0.8 options are introduced to add specific role-options.

  • showDesigner: The user can see the designer
  • allowFormDesign: The user can edit the forms config in the designer (categories, constants, forms: save, restore, pull and push the forms repositories). Without it the designer shows them read-only. Default true. (Added in 7.3.0)
  • designAllForms: The designer shows and edits every form. Without it, only the forms whose roles hold one of the user’s roles: the others are left out (never named, a name taken by one is only said to be taken, a form of theirs naming one as a subform shows nothing of it). The subforms no hidden form uses (new ones included) are theirs to edit, a subform a hidden form uses as well as one of theirs is shown read only, and a form saved (a subform aside) must keep one of their roles. A file holding several forms keeps the hidden ones as they are, restoring a backup needs this option, and the form files are left out of the designer’s other explorers (a repository’s whole tree, as the workflows show it). The forms list leaves out the warning of a form name defined twice unless both copies are theirs, and the settings pages’ Forms tabs and a credential’s Used by tab, reached with a part of the settings only (not showSettings), list only the forms their designer shows. Limits the forms only (playbooks and workflows have designAllPlaybooks and designAllWorkflows); inventories, vars files, categories and constants stay visible to every designer. Off, the user may not run a raw expression either (POST /api/v2/expression with an expression of its own, as the designer previews a form not saved yet): it could read the files hidden from them. The expressions of the saved forms still run, and showSettings still allows a raw one. A form saved may not gain an expression or a query the server runs that it does not have already (403). Default true, always true for admins. (Added in 7.5.0)
  • allowPlaybookDesign: The user can edit the playbooks in the designer (save, new, remove, push). Without it the designer shows them read-only. Default true. (Added in 7.0.0)
  • designAllPlaybooks: Show and edit every playbook in the designer; without it, only the playbooks used by the forms the user can see, and the ones no form uses yet. A form uses a playbook by its playbook (with playbookSubPath), its ansible steps and the job template nodes of the workflows it runs (on the app or an rte runner); the forms it can see follow designAllForms. A hidden playbook is never listed nor read: it answers as a missing file, or as a file there already, and a form of theirs naming one, or a workflow file whose nodes run one, is refused. Edit Playbooks still decides whether the shown ones can be changed. Off, the user may not run a raw expression either (POST /api/v2/expression with an expression of its own, as the designer previews a form not saved yet): it could read the files hidden from them. The expressions of the saved forms still run, and showSettings still allows a raw one. A form saved may not gain an expression or a query the server runs that it does not have already (403). Default true, always true for admins. (Added in 7.5.0)
  • allowWorkflowDesign: The user can edit the workflows in the designer (save, new, remove, push). Without it the designer shows them read-only. Default true. (Added in 7.1.0)
  • designAllWorkflows: Show and edit every workflow in the designer; without it, only the workflows used by the forms the user can see, and the ones no form uses yet. A form uses the workflow file it runs (workflow) and the nested workflows that one runs (every workflow a reference may mean, when several have its name); the forms it can see follow designAllForms. A hidden workflow file is never listed nor read (nor named in a credential’s Used by tab, without showSettings): it answers as a missing file, or as a file there already, and a form of theirs naming one, or a workflow file whose nodes run one, is refused. Edit Workflows still decides whether the shown ones can be changed. Off, the user may not run a raw expression either (POST /api/v2/expression with an expression of its own, as the designer previews a form not saved yet): it could read the files hidden from them. The expressions of the saved forms still run, and showSettings still allows a raw one. A form saved may not gain an expression or a query the server runs that it does not have already (403). Default true, always true for admins. (Added in 7.5.0)
  • allowInventoryDesign: The user can edit the inventories in the designer (save, new, remove, push). Without it the designer shows them read-only. Default true. (Added in 7.1.0)
  • allowVarsFileDesign: The user can edit the vars files in the designer (save, new, remove, push). Without it the designer shows them read-only. Default true. (Added in 7.1.0)
  • showSettings: The user can see the settings page
  • showDebugButtons: The user can see the debug buttons on a form
  • showExtravars: The user can see the extravars on a form
  • showLogs: The user can see the server log (Settings > Server log)
  • showAuditLog: The user can see the audit log (Settings > Audit log) without the other settings. Default: admins. (Added in 7.3.0)
  • showAppearanceSettings: The user can change Settings > Appearance (defaults, name, logo, icon, links, environment label, announcements) without the other settings. Default false. (Added in 7.3.0)
  • showConnectionsSettings: The user can manage Settings > Connections (repositories, credentials, secret stores, runners, SSH, notifications, chat assistant, MCP, syslog) without the other settings. Default false. (Added in 7.3.0)
  • showJobs: The user can see the jobs page. Default true.
  • showArtifacts: The user can see the artifacts an AWX job returns. Default true.
  • allowFileUploads: The user can upload files through a form’s file fields. Without it the field is read-only and the upload is refused. Default true. (Added in 7.3.0)
  • allowApiTokens: The user can make API tokens (Profile > API token), living up to API_TOKEN_MAX_DAYS. Default false (true for a role that only sets extendedTokenExpiration, as before this option). (Added in 7.3.0)
  • extendedTokenExpiration: With allowApiTokens, the user can also make API tokens that never expire. Default false.
  • showAllJobLogs: The user can see all job logs (not only his own) (Added in 5.0.9)
  • admin: The role’s users are admins, as the admin role’s own: every form, the designer, the settings and the users, whatever the role is called (platformAdmins, infra_admins). Only an admin turns it on for a role with members or adds members to such a role, and a save that would take admin away from the admin saving it is refused. Never on the default role. Default false ; always true for the admin role. (Added in 7.6.0)
  • allowLogin: The user can login.
  • allowBackupOps: The user can perform database operations, such as backup and restore.
  • allowVerboseMode: The user can enable verbose mode on ansible forms.
  • allowJobRelaunch: The user can relaunch jobs with pre-filled form data from previous submissions.
  • allowJobDeletion: The user can delete jobs (their own ; an admin every job). Without it the job history stays whole. Default true. (Added in 7.3.0)
  • manageAllJobs: The user can abort, delete and relaunch the jobs of every user, not only their own, without the admin role (delete and relaunch also need allowJobDeletion and allowJobRelaunch). Default: admins. (Added in 7.3.0)
  • allowScheduledJobs: The user can create and manage scheduled jobs (recurring cron or one-time). Default for admins only. Grant it only to roles you would trust as admins: every user with this option sees and can change all schedules, not only their own, and a schedule they create runs with admin rights, for any form. (Added in 6.1.5)
  • allowStoredJobs: The user can store and load job data for later use. (Added in 6.1.5)
  • allowStoredJobsShare: The user can share a stored job, so other users can load it from the form (they need allowStoredJobsViewAll). The stored job stays theirs: only they (and the admins) can change or delete it. Default: admins. (Added in 7.5.0)
  • allowStoredJobsViewAll: The user sees the stored jobs other users shared, in the Load list of a form they may open, and can load them. Default: admins. (Added in 7.5.0)
  • allowPlannedJobs: The user can plan a one-time run of a form they may run (“Run later”). The job runs as that user, not as admin, and they cannot see or change other schedules. (Added in 6.1.5)
  • allowChat: The user can use the chat assistant (when it is enabled). Default true. (Added in 6.5.0)
  • allowMcp: The user can use the MCP server from an AI agent (when it is enabled). Defaults to the role’s allowChat. (Added in 7.0.0)

When options are not set, the admin role will have all options.
When options are set on the default role, they are everyone’s defaults: they have the lowest precedence and only fill the options none of the user’s own roles set.
You can add options on role level, which override the default role’s options. Between a user’s own roles the most restrictive wins (an option false on one of them is false).
The default role is every signed-in user’s ; there is no anonymous access. public is its name before 7 and keeps working (forms listing public still match), but new configs say default.

The allowLogin option is different, that is for the backend. By default everyone can login.
You can set it to false on default and then enable on the roles you want to give access. Watch out you don’t lock yourself out.

Exemples:

1) Roles

roles:
- name: admin        # is mandatory
  groups:
  - local/admins
  - ldap/Domain Admins
  - entraid/Domain Admins
- name: operator
  groups:
  - local/operator
- name: architect
  groups:
  - local/architect
  options:
    showDesigner: true      # architects can see the designer
    showLogs: true          # architects can see the logs
    allowJobRelaunch: true  # architects can relaunch jobs with pre-filled data
- name: demo
  groups:
  - local/demo
- name: usersonly
  users:
  - local/myuser
- name: default        # is mandatory
  groups: []  
  options:
    showDebugButtons: true  # everyone can see the debug buttons
    showExtraVars: true     # everyone can see the extravars

El rol default

Tots els usuaris que han iniciat sessió tenen el rol default, de manera que un formulari amb roles: [default] està obert a tothom qui pot iniciar sessió. No hi ha accés anònim: ningú no rep aquest rol sense iniciar sessió.

El rol no conté cap grup ni cap usuari, perquè ja s’aplica a tothom. Les seves options són els valors predeterminats de tothom, tal com es descriu a Opcions de rol més avall. config.yaml ha de tenir un rol admin i un rol default, i la pàgina de rols mostra tots dos com a Obligatori.

default es deia public abans de la 7.0.0, i el nom antic continua funcionant:

  • En un formulari, roles: [public] continua coincidint amb tots els usuaris, així que els formularis dels teus repositoris no necessiten cap canvi.
  • A config.yaml, un rol anomenat public es reanomena default al fitxer quan es carrega la configuració. Només canvia el nom, abans es fa una còpia de seguretat de la configuració, i una configuració guardada en un repositori queda amb un canvi pendent de fer push.
  • En una plantilla ytt, la plantilla no es reescriu: es reanomena la configuració que produeix, i un avís al registre et demana que també reanomenis el rol a la plantilla. La versió 8 hi rebutja un rol public.

Una configuració que té alhora un rol default i un rol public es rebutja, perquè són el mateix rol.

Objecte Role

Cada entrada de la llista roles:

A role allows RBAC. Each role has 1 or more groups (local or ldap). Except the default role (public its old name), which has no groups.
The default and admin roles are mandatory.

Atribut Comentaris
name
string / required / unique

The name of the role
alphanumeric + dash + underscore + space

The name of a role has to be unique. The default and admin roles are mandatory.
groups
array / required

Groups
A group (local, ldap or entraid)

A list of groups. They must be in the format of local/groupname or ldap/groupname or entraid/groupname

A Microsoft Entra ID group can be named by its object id, entraid/<object id>: unique, where two groups can share a display name. Both work ; the object id is the one to prefer.

azuread/, the Microsoft Entra ID prefix of before 7.3, still works the same as entraid/ (deprecated, removed in 8.0) ; the roles editor writes entraid/.
users
array / required
added in version 4.0.10

User
A user (local, ldap or entraid)

A list of local or ldap users. They must be in the format of local/username or ldap/username or entraid/username (azuread/username before 7.3, still accepted)
credentials
array
added in version 7.0.0

The credentials this role may use
regular expressions, matching a whole credential name

Limits the credentials a user of this role may use: those a job passes to a playbook or a template (the form’s credentials, ansibleCredentials, vaultCredentials, a credential field), and those a form query or fnCredentials reads while the user fills in a form. Each entry is a regular expression that must match the whole name ; __self__ is AnsibleForms’ own database.

A user none of whose roles lists credentials may use every credential, as before. Once one of their roles lists them, they may use what any of the roles that list them allows. The admin role is never limited. A launch that needs a credential the roles do not allow is refused before the job is created.
secretStores
array
added in version 7.0.0

The secret stores this role may read inline
secret store names

Limits the secret stores a user of this role may read through an inline reference (vault:<path>, secret:<store>:<ref>) in a credential map, a query or fnCredentials. When a role limits the credentials and none limits the stores, an inline reference must match a credential pattern itself: it is no way around them. Combined across roles as credentials.
runners
array
added in version 7.0.0

The runners this role may run jobs on
runner names

Limits the runners a job of a user of this role may run on: the form’s runner, or the default runner when it names none. Combined across roles as credentials.
options
object
added in version 5.0.8

Role options
Key value pairs

Since version 5.0.8 you can add specific role options. The options are used to enable or disable certain features for a role.
The options are:

  • showDesigner: The user can see the designer
  • allowFormDesign: The user can edit the forms config in the designer (categories, constants, forms: save, restore, pull and push the forms repositories). Without it the designer shows them read-only. Default true. (Added in 7.3.0)
  • designAllForms: The designer shows and edits every form. Without it, only the forms whose roles hold one of the user’s roles: the others are left out (never named, a name taken by one is only said to be taken, a form of theirs naming one as a subform shows nothing of it). The subforms no hidden form uses (new ones included) are theirs to edit, a subform a hidden form uses as well as one of theirs is shown read only, and a form saved (a subform aside) must keep one of their roles. A file holding several forms keeps the hidden ones as they are, restoring a backup needs this option, and the form files are left out of the designer’s other explorers (a repository’s whole tree, as the workflows show it). The forms list leaves out the warning of a form name defined twice unless both copies are theirs, and the settings pages’ Forms tabs and a credential’s Used by tab, reached with a part of the settings only (not showSettings), list only the forms their designer shows. Limits the forms only (playbooks and workflows have designAllPlaybooks and designAllWorkflows); inventories, vars files, categories and constants stay visible to every designer. Off, the user may not run a raw expression either (POST /api/v2/expression with an expression of its own, as the designer previews a form not saved yet): it could read the files hidden from them. The expressions of the saved forms still run, and showSettings still allows a raw one. A form saved may not gain an expression or a query the server runs that it does not have already (403). Default true, always true for admins. (Added in 7.5.0)
  • allowPlaybookDesign: The user can edit the playbooks in the designer (save, new, remove, push). Without it the designer shows them read-only. Default true. (Added in 7.0.0)
  • designAllPlaybooks: Show and edit every playbook in the designer; without it, only the playbooks used by the forms the user can see, and the ones no form uses yet. A form uses a playbook by its playbook (with playbookSubPath), its ansible steps and the job template nodes of the workflows it runs (on the app or an rte runner); the forms it can see follow designAllForms. A hidden playbook is never listed nor read: it answers as a missing file, or as a file there already, and a form of theirs naming one, or a workflow file whose nodes run one, is refused. Edit Playbooks still decides whether the shown ones can be changed. Off, the user may not run a raw expression either (POST /api/v2/expression with an expression of its own, as the designer previews a form not saved yet): it could read the files hidden from them. The expressions of the saved forms still run, and showSettings still allows a raw one. A form saved may not gain an expression or a query the server runs that it does not have already (403). Default true, always true for admins. (Added in 7.5.0)
  • allowWorkflowDesign: The user can edit the workflows in the designer (save, new, remove, push). Without it the designer shows them read-only. Default true. (Added in 7.1.0)
  • designAllWorkflows: Show and edit every workflow in the designer; without it, only the workflows used by the forms the user can see, and the ones no form uses yet. A form uses the workflow file it runs (workflow) and the nested workflows that one runs (every workflow a reference may mean, when several have its name); the forms it can see follow designAllForms. A hidden workflow file is never listed nor read (nor named in a credential’s Used by tab, without showSettings): it answers as a missing file, or as a file there already, and a form of theirs naming one, or a workflow file whose nodes run one, is refused. Edit Workflows still decides whether the shown ones can be changed. Off, the user may not run a raw expression either (POST /api/v2/expression with an expression of its own, as the designer previews a form not saved yet): it could read the files hidden from them. The expressions of the saved forms still run, and showSettings still allows a raw one. A form saved may not gain an expression or a query the server runs that it does not have already (403). Default true, always true for admins. (Added in 7.5.0)
  • allowInventoryDesign: The user can edit the inventories in the designer (save, new, remove, push). Without it the designer shows them read-only. Default true. (Added in 7.1.0)
  • allowVarsFileDesign: The user can edit the vars files in the designer (save, new, remove, push). Without it the designer shows them read-only. Default true. (Added in 7.1.0)
  • showSettings: The user can see the settings page
  • showDebugButtons: The user can see the debug buttons on a form
  • showExtravars: The user can see the extravars on a form
  • showLogs: The user can see the server log (Settings > Server log)
  • showAuditLog: The user can see the audit log (Settings > Audit log) without the other settings. Default: admins. (Added in 7.3.0)
  • showAppearanceSettings: The user can change Settings > Appearance (defaults, name, logo, icon, links, environment label, announcements) without the other settings. Default false. (Added in 7.3.0)
  • showConnectionsSettings: The user can manage Settings > Connections (repositories, credentials, secret stores, runners, SSH, notifications, chat assistant, MCP, syslog) without the other settings. Default false. (Added in 7.3.0)
  • showJobs: The user can see the jobs page. Default true.
  • showArtifacts: The user can see the artifacts an AWX job returns. Default true.
  • allowFileUploads: The user can upload files through a form’s file fields. Without it the field is read-only and the upload is refused. Default true. (Added in 7.3.0)
  • allowApiTokens: The user can make API tokens (Profile > API token), living up to API_TOKEN_MAX_DAYS. Default false (true for a role that only sets extendedTokenExpiration, as before this option). (Added in 7.3.0)
  • extendedTokenExpiration: With allowApiTokens, the user can also make API tokens that never expire. Default false.
  • showAllJobLogs: The user can see all job logs (not only his own) (Added in 5.0.9)
  • admin: The role’s users are admins, as the admin role’s own: every form, the designer, the settings and the users, whatever the role is called (platformAdmins, infra_admins). Only an admin turns it on for a role with members or adds members to such a role, and a save that would take admin away from the admin saving it is refused. Never on the default role. Default false ; always true for the admin role. (Added in 7.6.0)
  • allowLogin: The user can login.
  • allowBackupOps: The user can perform database operations, such as backup and restore.
  • allowVerboseMode: The user can enable verbose mode on ansible forms.
  • allowJobRelaunch: The user can relaunch jobs with pre-filled form data from previous submissions.
  • allowJobDeletion: The user can delete jobs (their own ; an admin every job). Without it the job history stays whole. Default true. (Added in 7.3.0)
  • manageAllJobs: The user can abort, delete and relaunch the jobs of every user, not only their own, without the admin role (delete and relaunch also need allowJobDeletion and allowJobRelaunch). Default: admins. (Added in 7.3.0)
  • allowScheduledJobs: The user can create and manage scheduled jobs (recurring cron or one-time). Default for admins only. Grant it only to roles you would trust as admins: every user with this option sees and can change all schedules, not only their own, and a schedule they create runs with admin rights, for any form. (Added in 6.1.5)
  • allowStoredJobs: The user can store and load job data for later use. (Added in 6.1.5)
  • allowStoredJobsShare: The user can share a stored job, so other users can load it from the form (they need allowStoredJobsViewAll). The stored job stays theirs: only they (and the admins) can change or delete it. Default: admins. (Added in 7.5.0)
  • allowStoredJobsViewAll: The user sees the stored jobs other users shared, in the Load list of a form they may open, and can load them. Default: admins. (Added in 7.5.0)
  • allowPlannedJobs: The user can plan a one-time run of a form they may run (“Run later”). The job runs as that user, not as admin, and they cannot see or change other schedules. (Added in 6.1.5)
  • allowChat: The user can use the chat assistant (when it is enabled). Default true. (Added in 6.5.0)
  • allowMcp: The user can use the MCP server from an AI agent (when it is enabled). Defaults to the role’s allowChat. (Added in 7.0.0)

When options are not set, the admin role will have all options.
When options are set on the default role, they will have the lowest precedence and can be used as default options for all roles.
You can add options on role level, which will override the default role options.
Examples

1) Roles

roles:
- name: admin        # is mandatory
  groups:
  - local/admins
  - ldap/Domain Admins
- name: operator
  groups:
  - local/operator
  users:
  - entraid/mike
- name: architect
  groups:
  - local/architect
  options:
    showDesigner: true # architects can see the designer
    showLogs: true     # architects can see the logs
- name: demo
  groups:
  - local/demo
- name: default        # is mandatory
  groups: []  
  options:
    showDebugButtons: true  # everyone can see the debug buttons
    showExtraVars: true     # everyone can see the extravars

Opcions de rol

Les options d’un rol activen o desactiven funcions per als seus membres. Des de la 7.3.0 la pàgina del rol les mostra en quatre grups, cada opció amb una (i) que explica què dona, el mateix text que mostra la vista Permisos del perfil:

Opció Permet a l’usuari Predeterminat
Configuració    
showSettings Veure i canviar totes les pàgines de configuració; el registre del servidor i les còpies de seguretat tenen les seves pròpies opcions Només admins
showAppearanceSettings Canviar la configuració d’aparença, sense la resta de la configuració (des de la 7.3.0) Desactivat
showConnectionsSettings Gestionar la configuració de connexions (credencials, runners i més), sense la resta de la configuració (des de la 7.3.0) Desactivat
showLogs Veure el registre del servidor Només admins
showAuditLog Veure el registre d’auditoria, sense la resta de la configuració (des de la 7.3.0) Només admins
allowBackupOps Fer còpies de seguretat de la base de dades i restaurar-la Només admins
Dissenyador    
showDesigner Veure i utilitzar el dissenyador Només admins
allowFormDesign Editar la configuració de formularis al dissenyador: categories, constants i formularis. Sense aquesta opció, només lectura (des de la 7.3.0) Activat
designAllForms Veure i editar tots els formularis al dissenyador. Sense aquesta opció, només els formularis dels rols de l’usuari (des de la 7.5.0) Activat
allowPlaybookDesign Editar els playbooks al dissenyador: desar-los, crear-los, treure’ls i fer-ne push. Sense aquesta opció, només lectura Activat
designAllPlaybooks Veure i editar tots els playbooks al dissenyador. Sense aquesta opció, només els que fan servir els formularis de l’usuari o que cap formulari fa servir encara (des de la 7.5.0) Activat
allowWorkflowDesign Editar els workflows al dissenyador: desar-los, crear-los, treure’ls i fer-ne push. Sense aquesta opció, només lectura Activat
designAllWorkflows Veure i editar tots els workflows al dissenyador. Sense aquesta opció, només els que fan servir els formularis de l’usuari o que cap formulari fa servir encara (des de la 7.5.0) Activat
allowInventoryDesign Editar els inventaris al dissenyador: desar-los, crear-los, treure’ls i fer-ne push. Sense aquesta opció, només lectura Activat
allowVarsFileDesign Editar els fitxers de variables al dissenyador: desar-los, crear-los, treure’ls i fer-ne push. Sense aquesta opció, només lectura Activat
Tasques    
showJobs Veure la pàgina de tasques Activat
showAllJobLogs Veure les tasques de tots els usuaris, no només les seves Només admins
manageAllJobs Avortar, suprimir i tornar a llançar les tasques de tots els usuaris; suprimir i tornar a llançar també necessiten les dues opcions següents (des de la 7.3.0) Només admins
showExtravars Veure les extravars d’un formulari i d’una tasca Activat
showDebugButtons Veure els botons de depuració d’un formulari Activat
showArtifacts Veure els artefactes d’una tasca: el que retorna una tasca d’AWX, o el que un playbook ha recollit amb set_stats Activat
allowVerboseMode Executar tasques en mode detallat Activat
allowJobRelaunch Tornar a llançar una tasca amb les dades del formulari d’una execució anterior Només admins
allowJobDeletion Suprimir tasques: les seves, o les de tots els usuaris amb manageAllJobs. Sense aquesta opció, l’historial de tasques es conserva sencer (des de la 7.3.0) Activat
allowScheduledJobs Crear i gestionar programacions recurrents i puntuals, a la pàgina Programacions (vegeu l’avís més avall) Només admins
allowPlannedJobs Planificar una tasca perquè s’executi una vegada a una hora fixada (Executa més tard) Activat
allowStoredJobs Desar les dades d’un formulari i tornar-les a carregar més tard Activat
Accés i integracions    
allowLogin Iniciar sessió a AnsibleForms Activat
allowChat Utilitzar l’assistent de xat, quan està activat Activat
allowMcp Utilitzar el servidor MCP des d’un agent d’IA, quan està activat L’allowChat del rol
allowFileUploads Pujar fitxers mitjançant els camps de fitxer d’un formulari (des de la 7.3.0) Activat
allowApiTokens Crear tokens d’API per a scripts, fins a la durada màxima que permet la instància (des de la 7.3.0) Desactivat
extendedTokenExpiration Crear també tokens d’API que no caduquen mai; necessita allowApiTokens Desactivat

Algunes opcions n’inclouen d’altres, i la pàgina del rol mostra les incloses activades i en gris:

  • showSettings també dona showAppearanceSettings, showConnectionsSettings i showAuditLog.
  • manageAllJobs també dona showAllJobLogs, ja que actuar sobre les tasques de tots els usuaris vol dir veure-les.
  • Les opcions de disseny només compten amb showDesigner, i extendedTokenExpiration només amb allowApiTokens.

Fins a la 7.2.0, showAllJobLogs també permetia a l’usuari avortar i suprimir les tasques que mostrava; des de la 7.3.0 això requereix manageAllJobs. Un rol d’abans de la 7.3.0 amb extendedTokenExpiration i sense allowApiTokens rep allowApiTokens, de manera que conserva els seus tokens.

designAllForms, designAllPlaybooks i designAllWorkflows estan sempre activades per als admins, i el que el dissenyador mostra a un usuari sense aquestes opcions es descriu a Dissenyadors limitats.

Només admins vol dir activat per als usuaris que tenen el rol admin, i desactivat per a tota la resta. Quan un usuari coincideix amb diversos rols, les opcions es combinen així:

  • Entre els rols de l’usuari, una opció només està activada quan tots els rols que la defineixen hi estan d’acord: un false explícit guanya.
  • El rol default completa les opcions que no defineix cap dels altres rols de l’usuari, de manera que pot contenir valors predeterminats per a tothom.
  • Les opcions que no es defineixen enlloc prenen el valor predeterminat de la taula.

showExtraVars, amb V majúscula, s’accepta com una altra grafia de showExtravars; quan qualsevol de les dues és false, l’opció està desactivada.

Tracta allowScheduledJobs com una opció de nivell d’admin. Les programacions no pertanyen a l’usuari que les ha creat: tots els usuaris amb l’opció veuen i poden canviar totes les programacions. A més, una programació s’executa amb drets d’admin, per a qualsevol formulari, sigui quin sigui l’accés del creador. Concedeix-la només a rols en què confiaries com a admins.

allowLogin: false al rol default deixa fora tots els usuaris els altres rols dels quals no defineixen allowLogin: true, inclosos els admins. Torna-la a concedir als rols que han de poder iniciar sessió abans de desar.