WEB-INF/resources/config/form-builder-permissions.xml
.hr
app, while other can edit forms in the sales
app, then you'll want to setup the form-builder-permissions.xml
.form-runner-roles.xml
.hr-form-editor
can edit or create forms in the hr
app, and only users with the role sales-form-editor
can edit or create forms in the sales
app. As you can infer from the syntax, you could be even more specific and only give access to users with a given role to a specific form in a specific app.<role>
element refers to as single role name. It is not possible to place multiple space-separated roles in the name
attribute.form-builder-permissions.xml
and done the appropriate setup for container-driven or header-driven roles, as described below:form-builder-permissions.xml
are at this point not supported; only restrictions on the app name are supported. This means that you should always use form="*"
. If you define a restriction on the form name, it won't be enforced at the time the form is created, allowing users to create, save, and publish a form with an undesirable name. However they then won't be able to see the form they created when going back to the summary page.form-builder-permissions.xml
also impacts the Form Runner Home page, which supports unpublishing and publishing forms.<role>
.<role>
elements are present<role>
elements<role name="*" app="*" form="*">
:/orbeon/fr/orbeon/builder/new
/orbeon/fr/orbeon/builder/edit/{id}
/orbeon/fr/orbeon/builder/summary