Customer Portal configuration¶
You can overwrite the default configuration of the Customer Portal to fit its capabilities to the unique needs of your business.
corporate SiteAccess in
config/packages/ibexa.yaml) serves the Customer Portal.
If you need a multisite setup with multiple Customer Portals,
add any additional SiteAccesses to
ibexa_default_settings.yaml contains a setting that indicates what Content Types should be treated like Users in terms of, for example, usage in
1 2 3 4
Roles and Policies¶
You can add custom roles to your installation
by listing them under the
This key overwrites the default list set in
vendor/ibexa/corporate-account/src/bundle/Resources/config/default_settings.yaml (the following example redeclares them for clarity):
1 2 3 4 5
You can do it per SiteAccess or SiteAccess group by using SiteAccess-aware configuration.
Content Type names¶
You can change names of default Content Types by assigning what
Content Types should be used to describe
Member in the Back Office.
Proceed only if you already have a
Company Content Type in your system, and you don't want to change its identifier.
Configuration for Content Type names is placed under the
like shown in
To change Content Type names, adjust corporate account configuration in the following way:
1 2 3
If you decide to change deafult names of Content Types, during migration you have to adjust files accordingly.
You can define what fields are required in the Customer Portal registration form. To do so, create and configure user registration form.
With the Address Field Type, you can customize address Fields and configure them per country. To learn more, see Address Field Type documentation.
You can also define new templates for, among others: invitation email,
reset password message and the information screens after any of the user's actions in
1 2 3 4 5 6 7 8 9