• Developer guide
  • API reference

›Polaris access

Getting started

  • Introduction to Imply Polaris
  • Quickstart
  • Navigate the console
  • Key concepts

Ingestion sources

  • Ingestion sources overview
  • Supported data formats
  • Create a connection
  • Ingest from files
  • Ingest from S3
  • Ingest from Kinesis
  • Ingest from Confluent Cloud
  • Kafka Connector for Imply Polaris
  • Push event data

Tables and data

  • Overview
  • Introduction to tables
  • Table schema
  • Create an ingestion job
  • Timestamp expressions
  • Data partitioning
  • Introduction to rollup
  • Approximation algorithms
  • Replace data

Analytics

  • Overview
  • Manage data cubes
  • Visualize data
  • Data cube dimensions
  • Data cube measures
  • Dashboards
  • Create a dashboard
  • Visualizations reference
  • Set up alerts
  • Set up reports
  • Embed visualizations
  • Query data

Monitoring

  • Overview

Management

  • Overview
  • Pause and resume a project

Billing

  • Overview
  • Polaris plans
  • Estimate project costs

Usage

  • Overview

Security

    Polaris access

    • Overview
    • Invite users to your organization
    • Permissions reference
    • Manage user groups
    • Enable SSO
    • SSO settings reference
    • Map IdP groups

    Secure networking

    • Connect to AWS

Developer guide

  • Overview
  • Authentication

    • Overview
    • Authenticate with API keys
    • Authenticate with OAuth
  • Manage users and groups
  • Migrate deprecated resources
  • Create a table
  • Define a schema
  • Upload files
  • Create an ingestion job
  • Ingestion sources

    • Ingest from files
    • Ingest from a table
    • Get ARN for AWS access
    • Ingest from Amazon S3
    • Ingest from Amazon Kinesis
    • Ingest from Confluent Cloud
    • Push event data
    • Kafka Connector for Imply Polaris
    • Kafka Connector reference
  • Filter data to ingest
  • Ingest nested data
  • Ingest and query sketches
  • Query data
  • Update a project
  • Link to BI tools
  • Connect over JDBC
  • Query parameters reference
  • API documentation

    • OpenAPI reference
    • Query API

Product info

  • Release notes
  • Known limitations
  • Druid extensions

Polaris access overview

The Organizational settings console is a web interface for setting up, monitoring, and managing user access to Imply Polaris. It encapsulates access settings across the entire organization. It is also where you configure authentication policies and connect third-party identity providers.

To access the Organizational settings console from the Home page, click the profile menu in the top right corner. Select User management from the list of menu options.

Authentication and authorization

Polaris identifies each authorized user of your account by a unique login tied to their email address. Polaris offers a role-based access control (RBAC) model that allows you to control the level of access available to users in your organization.

In particular, the RBAC model lets you manage the following permissions for Polaris authorized users:

  • Ability to manage projects and other users.
  • Ability to manage data cubes and dashboards.
  • Ability to see visualizations.
  • Ability to query data directly with SQL.
  • Ability to load new data.

You can also create API keys and custom OAuth clients to enable applications to call the Polaris API directly. To learn more about authenticating REST API requests to Polaris, see Authentication overview.

Permissions and groups

Permissions determine the operations a user can perform. For example, the AdministerDashboards permission lets a user view and manage all dashboards within an organization.

You grant permissions to users through groups. Polaris provides predefined groups that correspond to specific use cases, such as Organization Admin, Data Manager, and Viewer. Polaris adds all new users to the Viewer group by default.

For information on creating and managing groups, see Manage user groups.

Access control

You can restrict access to individual data cubes, dashboards, and alerts to specific users and groups. This is an optional feature that you can use in conjunction with Polaris permissions, to control access to your resources at a granular level.

For more information on how to restrict access to your resources, see the following topics:

  • Manage data cubes
  • Dashboards overview
  • Alerts
← OverviewInvite users to your organization →
  • Authentication and authorization
  • Permissions and groups
  • Access control
Key links
Try ImplyApache Druid siteImply GitHub
Get help
Stack OverflowSupportContact us
Learn more
BlogApache Druid docs
Copyright © 2023 Imply Data, Inc