The superuser for in-house customers can add new tenants to your server using the Manage Tenants page.
You cannot remove or copy the d (Default tenant).
The superuser for in-house customers can use the Tenant page to add a new tenant . We recommend using lower case for the tenant name as the tenant name becomes part of your user's login names which are case sensitive.
To display the Tenant page,
Here is a brief explanation of the fields:
Are you creating a tenant for Confluence? - Check this if you are planning on integrating with Confluence. If checked, the Security Manager Class field displays the Delegating Security Manager. This is the Security Manager needed for Confluence. If unchecked, the Default Security Manager will be used.
If you are not using Confluence, select a Security Manager Option from the following choices:
Tenant ID - Enter the tenant Id in this field - The tenant id can contain characters, numbers, dot(.), hyphen (-) and the underscore. It cannot start with a number. A common practice is to use your domain name for the tenant id.
The superuser or tenant admin can set up the Business Calendar for your tenant. will then use the calendar information when calculating an escalation deadline for workflow steps and to determine the date/time for notification/reassign emails if they are configured. A tenant can only have one Business Calendar.
In the Business Calendar section of the Add/Edit Tenant screen:
The Business Calendar makes it very simple to configure workflow escalations based on a 5 - day work week. Once the calendar is set up, simply check the Business Calendar checkbox on the escalation condition in your workflow.
It is no longer necessary to use a rule to Calculate a Date based on a five day work week.
Live forms offers a user interface to specify credentials to external secure web services that are accessed by the forms/flows in your tenant. For example, if you have a rule that connects to a web service or a Form/Doc action that posts to a web service that is not publicly accessible, credentials can be configured for the services in each of your tenants.
The specification of http credentials for in-house customers was previously supported globally and configured in the httpclient-auth.properties file. This method is no longer used. In-house customers using this file for HTTP authentication should read the Migration Considerations before upgrading.
To configure http security credentials at the tenant level, follow these steps:
Basic - a common HTTP Authentication protocol that assumes that client credentials consist of a username and a password where the latter is a secret known only to you and the server
NTLM - a Windows network authentication protocol that allows a client to prove its identity without sending a password to the server.
Scheme, host, user name and password are required.
Port is optional and may be left blank. Either blank or -1 equates to any port and the system will alter blank to be -1.
All fields are specified in plain text and not encoded in any way.
Domain is only generally used for NTLM.
There are some configuration items that must be performed before creating a tenant using the LDAPContainer Security Manager. Once the prerequisites have been completed, adding a tenant that uses the LDAP Container Security Manager is exactly the same as configuring a tenant using the LDAP/Active Directory Security Manager. Please follow the steps listed here.
Refer to the Configuring the LDAP Container Security Manager topic for the instructions.
Creating/editing the SAML tenant is performed by the superuser (on-premise) or the tenant admin (cloud). Refer to Configuring the Azure SAML Security Manager for the details.
The Database Container Security Manager should be selected when authentication is the container's responsibility and you want to use the database interface to fetch users/roles for design time functionality from an external database. Click here for the configuration details.
A tenant admin or a superuser admin can use the Tenant page to configure or edit information about a tenant.
To display the Tenant page:
Note that you cannot change the Tenant Id, although you can change the Name and Description.
The following Security Manager changes can be made by clicking the Change button and making a selection from the dropdown. Cloud customers should contact email@example.com to initiate the procedure.
Click the button to see details about a field. Click Submit to save your changes. The message "Tenant updated successfully" will display.
Be aware that changing the Security Manager of your tenant is a ONE-WAY operation. Once completed, you CANNOT change it back to the original security manager.
If you are editing a tenant using the SAML Secuirty Manager, configured metadata and attribute mappings will display. These values can be modified using this screen.
Remember, if you check the Authentication Only checkbox, only the User Id field displays for mapping.
If you are editing a tenant using the Azure SAML Security Manager, configured metadata and attribute mappings will display. These values can be modified using this screen.
Authentication Only is checked so only the field for User Id mapping is displayed.
Changes to the Business Calendar can be made in the Business Calendar section:
Changes to the HTTP Authentication Credentials can be made by expanding the section:
The email address entered in this section is used as the from email address for email notifications and doc action emails for forms and workflows in the tenant. If you want to setup the email address with a user friendly name, enter the text in the Display Name field. You can specify a different from email address for Document Action and Activity Document action emails by entering a valid email address in the from field in both wizards. The values in these fields overrides the address entered on the Edit Tenant screen.
Refer to the Email configuration or integration topics for more information.
A user designing a form, viewing their task list, or using a form to enter values and submit has a certain number of minutes to complete the activity. This time limit is call the Session Timeout. By default the session will expire after 30 minutes of inactivity. When the session expires a designer user will have to re-login to to continue designing forms and users filling forms will have to get new form instance and re-enter the values. The tenant admin can override the default session timeout by entering a different value in the Session Timeout field. See Session Timeout topic in the Installation & Configuration Guide for full details.
The Max Concurrent Users field only appears if you are logged in as a superuser admin. This field enables you to restrict the number of users who can simultaneously login to a particular tenant. For example if you have purchased and installed a 20 user license key and want to set tenant A to use 5 and tenant B to use 15, setup that configuration here. See Concurrent Users for more information.
Max Users is subject to your license.
The Deployment State lets you toggle the default deployment state of your form between two states: PRODUCTION and DEVELOPMENT. When a form is in development state it contains a watermark. If you have a unlimited user license key you may want all the forms created by the designer to automatically be deployed for production with no water mark.
See also the deployment form property.
Anonymous signup lets you publish a registration Url for your tenant so people can signup and create a user account in your tenant themselves. In the Edit Tenant form, check the anonymous signup property and then select the default roles you want them to have when they signup. You can click the "+" to add multiple roles. If you select the designer role, these new users will have permission to design forms and workflows.
Then publish the registration Url:
https://www.frevvo.com/frevvo/web/tn/<your tenant name>/register?edit=true
At this Url people will see a signup form.
When they submit this form they'll be notified via email to activate their account. Until they activate via the email their account will remain disabled.
Now this person has a user account on your tenant and can login. If you gave them the designer role they will also be able to create forms and workflows. If not, when they login, they will see their task list as shown below.
Tenants configured with an LDAP or SAML Security Manager do not display the Anonymous Signup checkbox as this feature is not applicable for an LDAP or SAML tenant.
To setup your tenant, first login to your new tenant as the tenant admin. The tenant admin can add users to the tenant. You need to add at least one designer user in order to begin creating forms.
We strongly recommend that you do not use the admin user to create your own forms. You can create users and roles in your new tenant for that purpose.