Permission levels
Permissions determine the level of access that a user has to various components of the Feature Store. For example, depending on the level of permission granted, a user may be authorized to edit feature sets, while another user with limited view-only permission can only observe the feature set.
Levels of permission
Feature Store has six levels of permission:
These roles apply both at the workspace level (governing the workspace and, as a prerequisite, access to the feature sets it contains) and at the feature set level (governing a single feature set). See Migrate from Projects for how workspaces replace the legacy Projects concept.
Additionally, Feature Store also has the concept of an admin account. An admin is any user with the admin role specified in their identity provider. Admin users can perform additional management tasks.
The name of the claim storing the roles and name of admin role is configurable during Feature Store deployment.
Owner
- Owner role on a workspace
- Owner permission for feature sets
You become the owner by creating a workspace. As the owner, you can delete the workspace, manage its access level, and assign roles to other users (currently only through the UI — see the note below). As a workspace owner, you can manage every feature set within the workspace.
You become the owner by creating a feature set. As the owner, you can remove the feature set and assign the owner, editor, consumer, sensitive consumer or viewer permission levels to other users.
As the owner, you have all the other permissions.
- Editor
- Sensitive consumer
- Consumer
- Viewer
- Metadata viewer
Editor
- Editor role on a workspace
- Editor permission for feature sets
If you have the editor role on a workspace, you are authorized to update the workspace's metadata and register new feature sets within it. As a workspace editor, you can also manage the feature sets within the workspace.
If you have editor permission for a feature set, you are authorized to update the feature set's metadata and call ingest on the feature set.
As an editor, you also have the following permissions,
- Sensitive consumer
- Consumer
- Viewer
- Metadata viewer
Sensitive consumer
- Sensitive consumer role on a workspace
- Sensitive consumer permission for feature sets
If you have the sensitive consumer role on a workspace, you are authorized to list and obtain feature sets from the workspace, with sensitive consumer access to those feature sets.
If you have sensitive consumer permission for a feature set, you are authorized to call retrieve on
the feature set. The retrieved data contains data in its original,
unmasked variant (raw data).
As a sensitive consumer, you also have the following permissions:
- Consumer
- Viewer
- Metadata viewer
Consumer
- Consumer role on a workspace
- Consumer permission for feature sets
If you have the consumer role on a workspace, you are authorized to list and obtain feature sets from the workspace. In other words, as a consumer of a workspace, you can retrieve data from its feature sets.
If you have consumer permission for a feature set, you are authorized to call retrieve on
the feature set. Among retrieved features, only masked features will be displayed as
hashed values.
As a consumer, you also have the following permissions:
- Viewer
- Metadata viewer
Viewer
- Viewer role on a workspace
- Viewer permission for feature sets
If you have the viewer role on a workspace, you are authorized to see which feature sets are within the workspace. This behaviour is also influenced by the Workspace access levels.
This permission allows you to get a feature set and various information about it, including preview access. Viewer is the lowest permission level that can call preview on a feature set.
As a viewer, you also have the following permission:
- Metadata viewer
Metadata viewer
- Metadata viewer role on a workspace
- Metadata viewer permission for feature sets
If you have the metadata viewer role on a workspace, you are authorized to see which feature sets are within the workspace. This is metadata-only access — you cannot retrieve or preview data. Metadata viewer is the default level of access for public workspaces, granting the minimum access needed to discover and inspect feature sets without accessing underlying data.
If you have metadata viewer permission for a feature set, you can view the feature set's metadata, features, feature metrics, model references, ingest history, and pin or unpin the feature set. You can also request higher permissions.
Metadata viewer cannot call preview or retrieve on a feature set — it is metadata-only access. To preview data, you need at least Viewer permission.
Workspace access levels
Access levels on a workspace control what users can additionally do and are reflected internally by permissions. See Workspace access levels for more information.
- Submit and view feedback for this page
- Send feedback about H2O Feature Store to cloud-feedback@h2o.ai