18 docs tagged with "Solution Architect"

Overview

Introduction

The Qrvey platform enables end users to display dates and times in their local time zone. The Qrvey platform stores data in UTC/GMT+0 and adjusts the time displayed to the end user based on their preferred settings. The default time zone setting is specified in Qrvey Admin Center, but it can be overridden programmatically. The possible settings are:

A Connection is a link established between Qrvey and an external data source.

The initial Qrvey Administrator account was created when your instance of Qrvey platform was created. You may create additional Administrator accounts using the User Management feature in Qrvey Admin Center. You also have the option to create a Qrvey Administrator account in the AWS IAM service.

This feature is disabled by default and must be enabled by your team admin. For details, please see Customizing Qrvey Composer.

The Infrastructure page of the Qrvey Admin Center enables you to view, monitor, and manage the configuration of your Elasticsearch cluster.

This article contains frequently asked questions organized by user persona. If you still can't find what you're looking for, ask us!

The Health Dashboard in Qrvey Admin Center provides an easy-to-read status of the health of the Elasticsearch cluster in this instance of the Qrvey platform.

Introduction

The Qrvey platform is an all-in-one analytics solution that enables SaaS providers to put cutting-edge analytics into the hands of their users. This article contains essential information required to understand how to work with the Qrvey platform.

<!--

Qrvey platform supports internationalization and localization for end users in a comprehensive manner. Multi-lingual support is offered for both “static” and “dynamic” text, as well as formatting of numbers and dates based on regions and cultures.

This section describes how to configure security to restrict and grant access to the columns and records in the dataset. Articles include:

In the User Management tab, you can not only create users and groups but also restrict access to certain portions of your application. For instance, you may wish to hide individual pages or components from certain users or allow certain groups of users to access only specific datasets.

Overview

Before Creators can use the OpenID provider to log in, you must set up your OpenID provider account in order to obtain the OAuth 2.0 credentials: ClientID, Client Secret, Realm; set a redirect URL (Return URL); and optionally, customize the branding information that creators will see on the user-consent screen.

Before Creators can use the OpenID provider to log in, you must set up your OpenID provider account in order to obtain the OAuth 2.0 credentials: ClientID, Client Secret, Realm; set a redirect URL (Return URL); and optionally, customize the branding information that creators will see on the user-consent screen.