Wiki source code of Mandanteinstellungen


Hide last authors
gru 1.1 1 {{content/}}
2
MKO 18.2 3 {{figure image="1_en_ClientSettings.png" clear="h1"/}}
gru 1.1 4
MKO 18.2 5 == Base settings ==
gru 1.1 6
MKO 18.2 7 === Name ===
gru 1.1 8
MKO 18.2 9 The name of the client as it was assigned when the [[client was created>>doc:Formcycle.SystemSettings.UserInterface.Clients]]. In addition, the system-internal ID and the total memory occupied by the client are also displayed.
gru 1.1 10
11 === Alias ===
12
MKO 18.2 13 An alternative or alias name for this client. The alias name is a unique identifier for this client and can be used to generate easier to read links to your form. For example, it lets you open a form with a link like {{code language="none"}}https://formcycle.eu/form/alias/mandant/myform{{/code}} instead of {{code language="none"}}https://formcycle.eu/form/provide/692{{/code}}. See also [[how to publish your form>>doc:Formcycle.UserInterface.MyForms.Publish.WebHome]].
gru 1.1 14
MKO 18.2 15 === Language ===
gru 1.1 16
MKO 18.2 17 Default language for forms, when no language [[has been specified such as by URL parameters>>doc:Formcycle.Designer.Form.Internationalization]].
gru 1.1 18
MKO 18.2 19 This setting does not affect the language of the configuration interface of {{formcycle/}}, which will be determined either automatically by the browser's preferred language, or it can be chosen manually on the sign in page.
gru 1.1 20
MKO 18.2 21 === Base URL ===
gru 1.1 22
MKO 18.2 23 The base URL is used as the first part of the URL that will be used to open forms. Users of the form should be able to access this URL. For example, when the base URL has been set to
24 {{code language="none"}}http://pro.formcloud.de/formcycle/{{/code}}, the URL to the form would look like this: {{code language="none"}}http://pro.formcloud.de/formcycle/form/alias/<clientId>/<formName>{{/code}}
gru 1.1 25
MKO 18.2 26 === Description ===
gru 1.1 27
MKO 18.2 28 An optional short description for this client.
gru 1.1 29
MKO 18.2 30 === Maximum number of forms ===
gru 1.1 31
MKO 18.2 32 This setting can only be viewed and changed by the superadmin or //sadmin //of a cloud installation. This number defines the maximum number of forms that can be turned online simultaneously. If the number "0" is set here, the maximum number of forms that can be turned online defined in the license will be used.
gru 1.1 33
MKO 18.2 34 === Maximum number of invites ===
gru 1.1 35
MKO 18.2 36 This setting can only be viewed and changed by the superadmin or //sadmin//. This number defines the maximum number of invites that can be send in one invitation step. The number "-1" means unlimited number of invites. If the number "0" is set here, the default maximum number of invites that will be used (cloud demo clients: 10, cloud clients: 100, others: unlimited).
gru 1.1 37
MKO 18.2 38 == Support settings ==
gru 1.1 39
MKO 18.2 40 {{figure image="ClientSettings.png" width="600"}}
41 Settings to grant the support access to this client.
gru 1.1 42 {{/figure}}
43
MKO 18.2 44 These settings can be seen in a cloud environment only.
gru 1.1 45
MKO 18.2 46 ; Grant access to the administration area
47 : Sometimes the support team requires access to the backend of {{formcycle/}} to help you out. This may be the case, for example, when the support needs to check some technical settings. Only a client administrator may grant access.
48 ; Grant access to the inbox
49 : Once access was granted, you can grant access to the inbox as well, if required. Please note that the inbox may contain personal data which the support team may get access to. Do not grant access unless it is absolutely necessary. Once the support team is done, revoke the access by unchecking these options.
gru 1.1 50
MKO 18.2 51 == Mail settings ==
Release Notes 15.1 52
MKO 18.2 53 {{figure image="client_mail_settings_en.png" width="400" clear="h1"/}}
Release Notes 15.1 54
MKO 18.2 55 === Allow use of the system mail server {{version major="7" minor="3"/}} ===
Release Notes 15.1 56
MKO 18.2 57 Allows the system administrator to enable/disable the use of the system mail server for this client. If this is disabled, functionalities that require an e-mail server will only be available when configuring a client-specific e-mail server.
Release Notes 15.1 58
MKO 18.2 59 === Allow client specific mail server {{version major="7" minor="3"/}} ===
Release Notes 15.1 60
MKO 18.2 61 Allows the system administrator to enable/disable the configuration of a client-specific email server. If this is disabled and the use of the system mail server is not allowed, no functionalities which require an e-mail server are available to this client.
gru 1.1 62
MKO 18.2 63 === Mail address for support requests ===
gru 1.1 64
MKO 18.2 65 The email address to which [[support requests are sent to>>doc:Formcycle.UserInterface.Support]]. By default, when this is left empty, the global email address [[as set for the system>>doc:Formcycle.SystemSettings.UserInterface.EmailServer]] is used. This setting may not be available when the system administrator [[did not allow it>>doc:Formcycle.SystemSettings.UserInterface.EmailServer]].
gru 1.1 66
MKO 18.2 67 === Use custom mail server ===
Release Notes 11.1 68
MKO 18.2 69 A mail server should be setup for each client. When no mail server has been configured, the system mail server will be used when it is available. In case no system mail server was configured, no emails can be sent, even if a client-specific mail server exists.
gru 1.1 70
MKO 18.2 71 When no mail server is available, the following services will be deactivated:
gru 1.1 72
MKO 18.2 73 * Forgot password and [[Reset password>>doc:Formcycle.UserInterface.UserSettings.User]] (sending recovery mails)
74 * Actions of type [[Email>>doc:Formcycle.Designer.Workflow.Actions.EMail]]
gru 1.1 75
MKO 18.2 76 The following mail server options can be changed:
gru 1.1 77
MKO 18.2 78 ; Authentication {{version major="7" minor="3"/}}
79 : Specifies the type of authentication to the e-mail server
80 ; Mail server
81 : The mail server used for sending mails of this client. Mails will be sent by [[actions of type email>>doc:Formcycle.Designer.Workflow.Actions.EMail]] and by the [[system>>doc:Formcycle.UserInterface.UserSettings.WebHome]] when a password needs to be reset.
gru 1.1 82 ; Port
MKO 18.2 83 : The SMTP port to be used. When not port is specified, the default SMPT port 25 will be used.
84 ; Server supports UTF-8 message headers (RFC6532)
85 : When the email server supports UTF-8 message headers according to RFC6532, this option should be enabled. You can then send email to internationalized email addresses such as //山田太郎@株式.会社//.
86 ; Encryption
87 : Type of encryption to be used for the communication with the mail server.
88 ; Authorization required (until 7.3.0)
89 : When the mail server requires authorization, enable this option and enter the username and the password.
90 ; Sender address (System)
91 : The mail address to be used as the sender address (mail //form//) for mails sent by the systen, eg. for password recovery mails.
92 ; Sender name (System)
93 : The sender name that is to be used for system e-mails.
gru 1.1 94
MKO 18.2 95 ==== Username and password ====
Release Notes 10.1 96
MKO 18.2 97 {{figure image="client_mail_username_password_en.png" width="300" clear="h1"/}}
Release Notes 11.1 98
MKO 18.2 99 ; Username
100 : The username to access the email server.
101 ; Password
102 : The password for the username
Release Notes 10.1 103
104 ==== Microsoft Office 365 (Graph API) {{version major="7" minor="3"/}} ====
105
MKO 18.2 106 {{figure image="client_mail_office365_en.png" width="300" clear="h1"/}}
Release Notes 11.1 107
MKO 18.2 108 ; Directory (tenant) ID
109 : Unique ID of the directory (tenant), which is used for sending the emails. You can find this in the overview of your Azure tenant.
110 ; Application (client) ID
111 : Unique ID of the application (client). After creating a new app registration, you can take it from the list of registrations.
112 ; Client secret
113 : Secret key which is used to authenticate your client. After creating a new client key within Azure, it is displayed temporarily. It is not possible to view it later, so it must be created again if it is lost.
Release Notes 10.1 114
115 {{info}}
MKO 18.2 116 Please note that in the Azure Active Directory Admin Center, the API application permissions **Mail.Send** as well as **User.Read.All** must be granted. Furthermore, only a user within the Azure AD can be used as sender.
Release Notes 10.1 117 {{/info}}
118
MKO 18.2 119 == User management ==
gru 1.1 120
MKO 18.2 121 Change how users and user data should be managed. The following options are available:
gru 1.1 122
MKO 18.2 123 ; only System
124 : Users will be managed only by {{formcycle/}}. Users can be added or removed on the [[user management pages>>doc:Formcycle.UserInterface.UserSettings.WebHome]].
125 ; only LDAP
126 : All users are taken from [[LDAP account>>doc:Formcycle.UserInterface.UserSettings.LDAP]] and cannot be created manually.
127 ; LDAP and System mixed
128 : When you create a new users, you can choose whether the user should be linked to an [[LDAP account>>doc:Formcycle.UserInterface.UserSettings.LDAP]].
gru 1.1 129
MKO 18.2 130 == Changing the user management settings ==
gru 1.1 131
MKO 18.2 132 You can change how users are managed at any time. However, you should check whether all unauthorized users have been removed.
gru 1.1 133
MKO 18.2 134 ; Switching from //System only// to //LDAP and System//
135 ; Switching from //System only// to //LDAP only//
136 : All existing users will be kept and can still sign in. Check whether these users should be removed.
137 ; Switching from //LDAP and System// to //System//
138 ; Switching from //LDAP// to //System//
139 : All LDAP users are still referenced in the user management, but will not be able to sign in anymore and should be removed, unless you intend to change back LDAP at a later time.