Skip to main content

User roles

This page describes user roles in the H2O AI Cloud platform.

App Store roles​

Full access​

Grants access to anything that is ALL_USERS. You can set this role by using the fullAccessRoleName key in the App Store server config.yaml file. If fullAccessRoleName is not set, all users are automatically considered Full Access.

Creating, viewing, and launching Apps: Users with Full Access can upload apps and view and launch apps available to all users. They also have the ability to change the visibility of apps they own.

Creating, viewing, and modifying App instances: Users with Full Access can start any app and view any instance that has ALL_USERS visibility. They can view logs in the UI for any instance they own, and access logs with the command line interface (CLI) for any instance of an app they own.

Visitor​

Visitors can access and use applications based on their role assignments and may be assigned multiple roles. Any user without Full Access status is designated as a visitor.

Creating, viewing, and launching Apps: Visitors cannot upload apps. They can view and launch all apps with tags corresponding to the roles they belong to. They do not have access to view the email addresses of app owners.

Creating, viewing, and modifying App instances: Visitors can start any app with tags corresponding to their assigned roles. They can view and manage only the app instances they own, including pausing, resuming, and terminating these instances. However, they cannot view instance logs in either the UI or the CLI.

Admin​

Admins may have Full Access or be designated as Visitors. Their role is defined by the adminRoleName key in the App Store server config.yaml file. Admins possess full access to all H2O admin functionalities within the CLI.

Creating, viewing, and launching Apps: Admin permissions vary depending on whether the user has Full Access. Admins can view, delete, and manage the visibility of all apps through both the UI and the CLI. They can also run apps in the UI based on their Full Access status or assigned visitor roles.

Creating, viewing, and modifying App instances: Admins can start apps based on their Full Access status or specific visitor roles. They have the capability to view all instance logs, whether from the CLI or the UI.

AI Engine roles​

Admin​

Admins can create new versions of AI Engines and establish profiles to manage user access to various resources. They can view logs of AI Engine usage and all instances. Additionally, Admins have access to all User functionalities.

User​

Users can log into AI Engine Manager or Enterprise Steam and have the capability to launch, pause, resume, and terminate their instances. They can view and access all running instances they own. Additionally, users can hold one or more roles, letting them access various profiles or AI Engine parameters according to their specific roles.

Feedback