The DataGalaxy extension is a browser extension for Chrome, Edge, Brave and Opera. It is available to every license type, and the access a user gets inside it is the access they already have in the DataGalaxy web application.
This page lists the extension's technical characteristics, how it is installed and updated, and how authentication and authorization work.
What are the extension's specifications?
| Latest version | 2.1.0 |
|---|---|
| Compatibility | Chrome, Edge, Brave, Opera |
| Users | all license types (steward, reader) |
| User access | as defined via the DataGalaxy web application |
| Prerequisites | A DataGalaxy instance must exist. |
| Browser versions | We don't impose specific constraints, beyond keeping up with browser updates. Recommended: Chrome 129+, Edge 138+. |
| Installation | Via the Chrome Web Store or bulk pre-installation (contact DataGalaxy for more information on the options available). |
| Version updates | After a new release is deployed to production, the browser will automatically update the installed extension. This process can take up to 24 hours. If needed, you can force an update by manually installing the latest version. |
| Web application compatibility | The browser extension (versions 1.0+ and 2.0+) is compatible with the web application (v3). |
| Production releases and rollback | We deploy incremental improvements to production 1 to 4 times a month. Risk management: if a major issue is detected in production, rolling back to the previous version can be considered as a mitigation option. |
How does authentication work?
The DataGalaxy extension can authenticate using the same mechanisms as the main platform, ensuring secure and seamless access:
- Native authentication: the extension can prompt users to authenticate with their DataGalaxy username and password. Credentials are handled and stored securely, following cryptographic practices consistent with market standards, as with the main platform.
- Federated authentication (SSO): the extension supports 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.
How does authorization work?
Regardless of the authentication mode, access to the extension's features is controlled within DataGalaxy. Authorization for the extension is built into the platform's role- and rule-based model:
- Role- and rule-based access: access to the extension 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 the extension's features.
- Global access: workspace administrators can create global rules to provide read-only access to every user in the client account, including the extension's features.
Administrators can also define fine-grained access rules for the extension, specifying the allowed actions:
- View — read-only access to the extension's data or features
- Edit — ability to create, modify, or delete objects related to the extension
In summary, the extension follows the same authentication and authorization principles as DataGalaxy: secure sign-in via native or federated methods, and fine-grained access control based on roles, managed within the platform.