1️⃣Creating a Tenant
Let's create our first tenant on the archive system.
1. Navigate to your Admin URL.
The Solar Archive login page will be displayed.
2. Enter your credentials and click Login.
The Company List will be displayed. The Company Settings section allows Administrators to set basic information of the company, such as the company name and tag, Solr Collection, database server, creation, and contract end dates, contact details, host URL, Outlook preferences, forwarding options, and so on. These settings affect the look and feel of the system to search users (basic and privileged users).
3. Click Add New Company.
The form to enter company details will be displayed. You can enter any details of a tenant on this page, but for the purpose of this tutorial we'll be using "Acme Inc."
Fields marked * are mandatory and cannot be edited once the company is created.
4. Enter the details of the company.
Refer to the table at the bottom of this guide for field names and descriptions.
5. Click "Save"
We have now created our tenant and are now ready to proceed to the next guide.
If you are opting for "Automated Onboarding" this is where the guide ends. Please make sure you have checked "Send setup email" from the list of options. After clicking "save" the user will now receive an email to proceed with onboarding.
| Field Name | Description |
|---|---|
Tag | Short name of the company that will be used in the URL to access a specific company login and will be displayed in the Preferences dialog. For multi-tenant Solar Archive systems, each company will have a different Company Tag. It cannot be changed (via the Admin area) after the company has been created. |
Company Name | Full name of the company and what you set here will appear on the login page and in the footer line of all subsequent pages, and on some alert emails. |
Solr Collection | SOLR Collection that will be allotted to the company. It is a logical index spread across multiple servers. |
DB Server | Address of the database server on which the company database will be stored. |
Contact Name | Name of the contact person in the company, preferably the Admin user. |
Contact Email | Email address of the contact person in the company |
Contact Phone | Phone number of the contact person in the company |
Email domain(s) | Add up to 3 email domains used in email addresses for this company. These are used to determine the direction of each email (inbound / outbound etc.) and to compute the number of Active Email Accounts at this customer. |
Administrator | Provide the administrative login details added here to the customer, and then guide the customer through the administrative facilities that they have access to. |
🆕 Send Setup Email | Checking this box will send the automated onboarding email to the customer. |
Data Guardians | A Data Guardian is, in Solar Archive, an email address to which transcripts of administrator access and privileged user searches will be sent. At least one data guardian must be added, before adding any local user accounts. You can also specify whether or not this data guardian can receive Privileged User Search transcripts and Administrator access transcripts. |
Licensed users limit | Number of active mailboxes that should be recorded by Solar Archive. As emails are being archived, Solar Archive will compute an active mailbox count. When the computed active mailbox count exceeds the Licensed users limit, then the usage data will be highlighted to the administrator. Note: Active accounts are computed by Solar Archive as the number of unique ‘local’ email addresses that are used for both sending and receiving emails. It is computed on a daily basis and averaged over the month. ‘Local’ addresses are those that match the configured local email domains. |
*Encryption Key | Specify the type of encryption key to be used. The available options are System Level Key, Parent’s Key, and Custom Key. |
Reference | Any account number or billing number or any note related to the customer can be used as a reference. This can be used to link to an Accounting system, project number, or any other reference desired. Solar Archive supports an API, allowing remote systems to connect and query various aspects of the system. This reference, in combination with the API, can be used to automate some business processes. |
Contract End Date | The date on which the customer’s contract ends. |
Use System-wide SMTP Services | Specify whether or not to allow system-wide SMTP services. |
Last updated
