Submit a ticket My tickets
Welcome
Login  Sign up
  1. DataGalaxy
  2. DataGalaxy's Extension
  3. Extension's roadmap and main updates

General Information about DataGalaxy Extension

Modified on: Wed, 1 Apr, 2026 at 6:01 AM
Last version2.1.0
CompetabilityChrome, Edge, Brave, Opera
Usersall licences (steward, reader)
User accessas defined via DataGalaxy's webapp
Requirements
DataGalaxy's instance should exist
Browsers versionsWe do not set up any requirements from our side. General practice - to follow browsers updates
Recommendations:
Chrome 129+
Edge 138+
InstallationVia Chrome Web Store, or bulk pre-install (please contact DataGalaxy for more info on available options)
Version updateAfter a new release is deployed to production, the browser will automatically update the installed extension. This process may take up to 24 hours.
If needed, you can force the update by manually installing the latest version.
Webapp compatibilityThe browser extension (versions 1.0+ and 2.0+) is compatible with the webapp (v3).
Production and rollbackWe release granular improvements to production 1–4 times per month.
Risk mitigation: In case major issues are detected in the production version, rolling back to the previous version is considered as a mitigation option.

Authentication


DataGalaxy extension can authenticate using the same mechanisms as the core platform, ensuring secure and seamless access:

  • Native Authentication: Extensions can prompt users to authenticate using their DataGalaxy login/password. Credentials are securely handled and stored according to industry-standard cryptographic practices, just like the main platform.
  • Federated Authentication (SSO): Extensions support authentication via SAML v2 or OpenID Connect (OIDC). Organizations can delegate authentication to their own Identity Provider, applying their internal security policies (password complexity, MFA, etc.), while the extension relies on DataGalaxy to manage authorizations consistently.

Extension inherits the authentication context of the logged-in user, meaning that users do not need to re-authenticate if they are already logged in to DataGalaxy.

Authorization


Regardless of the authentication method, access to extension functionality is controlled within DataGalaxy. Authorization for extensions is integrated with the platform’s role- and rule-based model:

  • Role- and Rule-Based Access: Extension access is determined by the user’s role and the workspace access rules.
  • Workspace-Level Control: Each workspace is closed by default; only administrators or explicitly authorized users can access extension features.
  • Access Rules for Extensions: Administrators can define fine-grained access rules for extensions, specifying:
    • What actions are permitted:
      • View – read-only access to extension data or features.
      • Edit – ability to create, modify, or delete extension-related objects.
  • Global Access: Workspace administrators can create global rules to provide read-only access to all users in the customer account, including extension functionality.

In short, extensions follow the same authentication and authorization principles as DataGalaxy itself: secure login through native or federated methods, and fine-grained, role-based access control managed within the platform



Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.

Table of contents

Related Articles