Administration is done in the FlexIt web application as shown here:
There are a few ways for new users to be added:
- Bulk User Upload – from a .csv file
- Add Individual User – enter username, fullname, and role. The user will be emailed a link to set their own password (if using FlexIt authentication).
- Self-registration – Users can click the “Register” link on the Login page. This will send an email to Admin users and will also show “1 new user request” when the Admins log into the FlexIt portal. Once the user has been approved, they will be emailed a link to set their own password (if using FlexIt authentication).
Groups & Roles Management
Roles define what features of the application a set of users have access to. Groups define what content (folders, reports, dashboards, etc.) a set of users has access to. Both groups and roles can be used to secure content and data, but only roles can define application functionality (e.g. create new dashboard).
Data sources are the connection details for the underlying databases and other sources used to pull data for reporting. To add a new Data Source,
Data models are the presentation layer (a.k.a business view, metadata layer) the report and dashboard authors see when they create new content. Data models connect to underlying data sources and define metadata such as relationships between entities, user-friendly names (e.g. First Name instead of F_NAME), calculations, formatting, drill paths, and more. See the “Metadata Modeling (Business Views)” knowledge base article for detailed instructions on how to create metadata models.
Details for each of the configuration settings can be found below.
The content database is where everything (reports, dashboards, users, groups, folders, etc.) is stored. By default, FlexIt comes with an enterprise-grade PostgresSQL 10 deployment that is production-ready. See the “Install and Configure FlexIt Server” knowledge base document for details on managing this database. If you do not use the default database, or would like to change to another database, you can change the settings under “Configuration > Content Database,” as shown below:
By default, authentication is handled by storing secured credentials in the FlexIt Content Store database. You may also use other authentication methods like LDAP (Lightweight Directory Authentication Protocol), Active Directory, or SAML based Single Sign On from providers like Okta, OneLogin, etc. Each method is shown below:
SAML Single Sign On Provider
For the “SAML Configuration” section, the identity provider (Okta, OneLogin, etc.) will provide you with the following when you set up a new application in their tool:
- Entry Point URL, also called “Identity Provider Single Sign-On URL” or “ACS (Consumer) URL”
- Identity Provider Issuer, also called “Issuer URL”
- X.509 Certificate
The “User Attribute Statements” and “Group Attribute Statements” should match the names used in step 7 above. Note the following options:
- “Sync Provider Groups?” defaults to “none”. Set it to “seed” if you want FlexIt to automatically assign the user group ONLY on the first login. Set it to “sync” if you always want FlexIt to use the Okta groups. If you use “seed” or “sync”, FlexIt will automatically assign the Okta group “FlexIt Admin” to the “Admin” role, “FlexIt Author” to the “Author” role, and “FlexIt Consumer” to the “Consumer” role. Note that the Okta group names must be assigned to the FlexIt Analytics application and exactly match FlexIt [Admin, Author, Consumer].
- “Default Group” defaults to “none”. If a user is assigned to the FlexIt Analytics application in Okta, but is not part of any Okta groups, you can automatically assign them either as a “Consumer” or “Author” in FlexIt.
By default, FlexIt comes with a development SMTP server configuration so that you don’t have to configure anything to test FlexIt. For production purposes and to properly secure your email transmissions, you may want to use your own SMTP server. Configuration details are shown below:
You can change the host name, port, and number of processes to use for load balancing, as shown below:
Backup and Restore
Back up and restore the entire content database, or individual reports, folders, dashboards, models, etc. Backups are stored in physical .zip files on your server under the installation directory “[installdir]/deployments”.
If you want to deploy the samples data to any database, change the setting here and Save:
To enable https on the server, you must place both the Private Key and Certificate file on the server under the “[installdir]/config/certs” folder. The Private Key must be in a PEM file named “privatekey.pem”. The Certificate can be in a file named “certificate.pem” or “certificate.cert”. You may also need to change the port to 443, see the Server Settings administration section. Restart the server for changes to take affect.