Show last authors
1 {{content/}}
2
3 {{figure image="1_en_ClientSettings.png" clear="h1"/}}
4
5 == Base settings ==
6
7 === Name ===
8
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.
10
11 === Alias ===
12
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]].
14
15 === Language ===
16
17 Default language for forms, when no language [[has been specified such as by URL parameters>>doc:Formcycle.FormDesigner.Internationalization.WebHome]].
18
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.
20
21 === Base URL ===
22
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}}
25
26 === Description ===
27
28 An optional short description for this client.
29
30 === {{version major="6" minor="2"/}} Maximum number of forms ===
31
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.
33
34 === {{version major="6" minor="2"/}} Maximum number of invites ===
35
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).
37
38 == Support settings ==
39
40 {{figure image="ClientSettings.png" width="600"}}
41 Settings to grant the support access to this client.
42 {{/figure}}
43
44 These settings can be seen in a cloud environment only.
45
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.
50
51 == Mail settings ==
52
53 === Mail address for support requests ===
54
55 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]].
56
57 === Use custom mail server ===
58
59 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.
60
61 When no mail server is available, the following services will be deactivated:
62
63 * Forgot password and [[Reset password>>doc:Formcycle.UserInterface.UserSettings.User]] (sending recovery mails)
64 * Actions of type [[Email>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.Actions.EMail]]
65
66 The following mail server options can be changed:
67
68 ; Encryption
69 : Type of encryption to be used for the communication with the mail server.
70 ; Mail server
71 : The mail server used for sending mails of this client. Mails will be sent by [[actions of type email>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.WebHome]] and by the [[system>>doc:Formcycle.UserInterface.UserSettings.WebHome]] when a password needs to be reset.
72 ; Port
73 : The SMTP port to be used. When not port is specified, the default SMPT port 25 will be used.
74 ; Authorization required
75 : When the mail server requires authorization, enable this option and enter the username and the password.
76 ; Sender address (System)
77 : The mail address to be used as the sender address (mail //form//) for mails sent by the systen, eg. for password recovery mails.
78 ; Sender name (System)
79 : The sender name that is to be used for system e-mails.
80
81 == User management ==
82
83 Change how users and user data should be managed. The following options are available:
84
85 ; only System
86 : Users will be managed only by {{formcycle/}}. Users can be added or removed on the [[user management pages>>doc:Formcycle.UserInterface.UserSettings.WebHome]].
87 ; only LDAP
88 : All users are taken from [[LDAP account>>doc:Formcycle.UserInterface.UserSettings.LDAP]] and cannot be created manually.
89 ; LDAP and System mixed
90 : When you create a new users, you can choose whether the user should be linked to an [[LDAP account>>doc:Formcycle.UserInterface.UserSettings.LDAP]].
91
92 == Changing the user management settings ==
93
94 You can change how users are managed at any time. However, you should check whether all unauthorized users have been removed.
95
96 ; Switching from //System only// to //LDAP and System//
97 ; Switching from //System only// to //LDAP only//
98 : All existing users will be kept and can still sign in. Check whether these users should be removed.
99 ; Switching from //LDAP and System// to //System//
100 ; Switching from //LDAP// to //System//
101 : 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.
Copyright 2000-2021