1. Prepare an installation#
Installer distribution details will be documented when the installer channel is finalized. No public installer URL or silent-install switches are verified in this snapshot. See Installation for the current boundary.
2. Open the interface and authenticate#
The application has a login page and a cookie-session web interface. Sign in using local identity, or AD identity when AD authentication is enabled and configured. This application login is separate from an account on yaadmin.io.
3. Set your language#
The interface supports English, Ukrainian and Russian preferences per user. Canonical language codes are en, uk and ru; ua is normalized as an alias for Ukrainian.
4. Connect useful tools#
An administrator manages Modules and MCP servers. Configure one provider first and inspect its health or discovery result. Enabled modules are not a guarantee that a provider is correctly configured or reachable.
5. Assign access#
Administrators manage users, roles and permission effects. Authentication alone does not grant access to all tools. Review Roles & Permissions before granting execution rights.
6. Start with a read request#
Use chat to ask for information supported by your connected tools. For example, an Action1-connected environment can list endpoint inventory, while the AD module can search directory users. Actual access depends on enabled modules, credentials and permissions.
7. Review activity and approvals#
Follow Live Activity, inspect results and review pending execution previews. Approvals authorize one fingerprint-bound request. Stop requests can cancel processing but do not reverse actions already submitted to an external system.
- Request
- Tool selection
- Permission check
- Approval if required
- Result