Rollen

Ordnen Sie Benutzer und Gruppen Rollen zu, und legen Sie fest, was jede Rolle darf.

  1. Das Attribut roles
  2. Die Rolle default
  3. Das Objekt Role
  4. Rollenoptionen

Das Attribut roles

Die Liste roles auf oberster Ebene von config.yaml:

Attribut Kommentare
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.

Beispiele:

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

Die Rolle default

Jeder angemeldete Benutzer hat die Rolle default, daher steht ein Formular mit roles: [default] jedem offen, der sich anmelden kann. Es gibt keinen anonymen Zugriff: Niemand erhält diese Rolle, ohne sich anzumelden.

Die Rolle enthält keine Gruppen und keine Benutzer, da sie bereits für alle gilt. Ihre options sind die Standardwerte für alle, wie unten unter Rollenoptionen beschrieben. config.yaml muss eine Rolle admin und eine Rolle default enthalten, und die Rollenseite zeigt beide als Erforderlich.

default hieß vor 7.0.0 public, und der alte Name funktioniert weiterhin:

  • In einem Formular passt roles: [public] weiterhin zu jedem Benutzer, daher müssen die Formulare in Ihren Repositories nicht geändert werden.
  • In config.yaml wird eine Rolle namens public beim Laden der Konfiguration in der Datei in default umbenannt. Nur der Name ändert sich, vorher wird eine Sicherung der Konfiguration angelegt, und eine in einem Repository gehaltene Konfiguration hat danach eine Änderung zum Pushen.
  • In einem ytt-Template wird das Template nicht umgeschrieben: Die daraus erzeugte Konfiguration wird umbenannt, und eine Warnung im Protokoll bittet Sie, die Rolle auch im Template umzubenennen. Version 8 weist dort eine Rolle public ab.

Eine Konfiguration mit sowohl einer Rolle default als auch einer Rolle public wird abgewiesen, da es dieselbe Rolle ist.

Das Objekt Role

Jeder Eintrag der Liste 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.

Attribut Kommentare
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

Rollenoptionen

Die options einer Rolle schalten Funktionen für ihre Mitglieder ein oder aus. Ab 7.3.0 zeigt die Seite der Rolle sie in vier Gruppen, jede Option mit einem (i), das sagt, was sie gewährt, derselbe Text, den die Ansicht Berechtigungen des Profils zeigt:

Option Erlaubt dem Benutzer Standard
Einstellungen    
showSettings Jede Einstellungsseite sehen und ändern; das Serverprotokoll und die Backups haben eigene Optionen Nur Admins
showAppearanceSettings Die Erscheinungsbild-Einstellungen ändern, ohne die übrigen Einstellungen (ab 7.3.0) Aus
showConnectionsSettings Die Verbindungs-Einstellungen verwalten (Anmeldedaten, Runner und mehr), ohne die übrigen Einstellungen (ab 7.3.0) Aus
showLogs Das Serverprotokoll sehen Nur Admins
showAuditLog Das Audit-Protokoll sehen, ohne die übrigen Einstellungen (ab 7.3.0) Nur Admins
allowBackupOps Die Datenbank sichern und wiederherstellen Nur Admins
Designer    
showDesigner Den Designer sehen und verwenden Nur Admins
allowFormDesign Die Formularkonfiguration im Designer bearbeiten: Kategorien, Konstanten und Formulare. Ohne sie nur lesen (ab 7.3.0) Ein
designAllForms Jedes Formular im Designer sehen und bearbeiten. Ohne sie nur die Formulare der Rollen des Benutzers (ab 7.5.0) Ein
allowPlaybookDesign Die Playbooks im Designer bearbeiten: speichern, erstellen, entfernen und pushen. Ohne sie nur lesen Ein
designAllPlaybooks Jedes Playbook im Designer sehen und bearbeiten. Ohne sie nur die, die die Formulare des Benutzers verwenden oder noch kein Formular verwendet (ab 7.5.0) Ein
allowWorkflowDesign Die Workflows im Designer bearbeiten: speichern, erstellen, entfernen und pushen. Ohne sie nur lesen Ein
designAllWorkflows Jeden Workflow im Designer sehen und bearbeiten. Ohne sie nur die, die die Formulare des Benutzers verwenden oder noch kein Formular verwendet (ab 7.5.0) Ein
allowInventoryDesign Die Inventare im Designer bearbeiten: speichern, erstellen, entfernen und pushen. Ohne sie nur lesen Ein
allowVarsFileDesign Die Variablendateien im Designer bearbeiten: speichern, erstellen, entfernen und pushen. Ohne sie nur lesen Ein
Jobs    
showJobs Die Seite Jobs sehen Ein
showAllJobLogs Die Jobs jedes Benutzers sehen, nicht nur die eigenen Nur Admins
manageAllJobs Die Jobs jedes Benutzers abbrechen, löschen und neu starten; Löschen und Neustarten brauchen zusätzlich die beiden Optionen unten (ab 7.3.0) Nur Admins
showExtravars Die Extravars eines Formulars und eines Jobs sehen Ein
showDebugButtons Die Debug-Buttons eines Formulars sehen Ein
showArtifacts Die Artefakte eines Jobs sehen: was ein AWX-Job zurückgibt oder was ein Playbook mit set_stats gesammelt hat Ein
allowVerboseMode Jobs im ausführlichen Modus ausführen Ein
allowJobRelaunch Einen Job mit den Formulardaten eines früheren Laufs neu starten Nur Admins
allowJobDeletion Jobs löschen: die eigenen oder mit manageAllJobs die aller Benutzer. Ohne sie bleibt der Job-Verlauf vollständig (ab 7.3.0) Ein
allowScheduledJobs Wiederkehrende und einmalige Zeitpläne erstellen und verwalten, auf der Seite Zeitpläne (siehe die Warnung unten) Nur Admins
allowPlannedJobs Einen Job einplanen, der einmal zu einer festgelegten Zeit läuft (Später ausführen) Ein
allowStoredJobs Die Daten eines Formulars speichern und später wieder laden Ein
Zugang und Integrationen    
allowLogin Sich bei AnsibleForms anmelden Ein
allowChat Den Chat-Assistenten verwenden, wenn er aktiviert ist Ein
allowMcp Den MCP-Server von einem KI-Agenten aus verwenden, wenn er aktiviert ist allowChat der Rolle
allowFileUploads Dateien über die Dateifelder eines Formulars hochladen (ab 7.3.0) Ein
allowApiTokens API-Token für Skripte erstellen, bis zur längsten Laufzeit, die die Instanz erlaubt (ab 7.3.0) Aus
extendedTokenExpiration Auch API-Token erstellen, die nie ablaufen; erfordert allowApiTokens Aus

Manche Optionen schließen andere ein, und die Seite der Rolle zeigt die eingeschlossenen eingeschaltet und ausgegraut:

  • showSettings gewährt auch showAppearanceSettings, showConnectionsSettings und showAuditLog.
  • manageAllJobs gewährt auch showAllJobLogs, da man die Jobs jedes Benutzers sehen muss, um mit ihnen zu arbeiten.
  • Die Design-Optionen zählen nur mit showDesigner, und extendedTokenExpiration nur mit allowApiTokens.

Bis 7.2.0 ließ showAllJobLogs einen Benutzer auch die angezeigten Jobs abbrechen und löschen; ab 7.3.0 braucht das manageAllJobs. Eine Rolle aus der Zeit vor 7.3.0 mit extendedTokenExpiration und ohne allowApiTokens erhält allowApiTokens, sodass sie ihre Token behält.

designAllForms, designAllPlaybooks und designAllWorkflows sind für Admins immer eingeschaltet, und was der Designer einem Benutzer ohne sie zeigt, beschreibt Eingeschränkte Designer.

Nur Admins bedeutet eingeschaltet für Benutzer mit der Rolle admin und ausgeschaltet für alle anderen. Passt ein Benutzer zu mehreren Rollen, werden die Optionen wie folgt kombiniert:

  • Zwischen den Rollen des Benutzers ist eine Option nur eingeschaltet, wenn jede Rolle, die sie setzt, zustimmt: Ein explizites false gewinnt.
  • Die Rolle default ergänzt die Optionen, die keine der anderen Rollen des Benutzers setzt, und kann so Standardwerte für alle enthalten.
  • Nirgends gesetzte Optionen übernehmen den Standard aus der Tabelle.

showExtraVars mit großem V wird als andere Schreibweise von showExtravars akzeptiert; ist eine der beiden Schreibweisen false, ist die Option ausgeschaltet.

Behandeln Sie allowScheduledJobs als Option auf Admin-Ebene. Zeitpläne gehören nicht dem Benutzer, der sie erstellt hat: Jeder Benutzer mit der Option sieht alle Zeitpläne und kann sie ändern. Ein Zeitplan läuft außerdem mit Admin-Rechten, für jedes Formular, unabhängig von den eigenen Zugriffsrechten des Erstellers. Gewähren Sie sie nur Rollen, denen Sie wie Admins vertrauen würden.

allowLogin: false auf der Rolle default sperrt jeden Benutzer aus, dessen andere Rollen nicht allowLogin: true setzen, einschließlich der Admins. Gewähren Sie sie den Rollen, die sich anmelden müssen, wieder, bevor Sie speichern.