ADMINA platform for getting work done through AI chat#
YAADMIN is a platform for carrying out tasks through an AI-assisted conversation. Connect your systems, tools and workflows, then describe the result you want in ordinary language. IT administration is one application; reporting, data analysis, document-related tasks and connected business processes can also fit the platform.
Its capabilities grow with the native modules, compatible MCP services, trusted custom integrations and authorized execution tools you connect. An external automation system such as n8n can extend the workflow when its actual operations are exposed through a compatible tool interface. This is an integration approach, not a claim that a native n8n module is already provided.
For example, you can ask “What programs are installed on OFFICE-PC-07?” In an environment connected to Action1, YAADMIN can identify the computer, request its software information and bring the result into your conversation. You can then ask a follow-up question using that information.
The practical value is having one place to describe a task, work with connected tools and review what they returned. You still configure the connections and decide which users may read information, run scripts or make changes.
Find a user account and inspect its directory information.
ad.search_usersad.get_userResolve the account → check access → query the directory → review returned information.
No live user data or fabricated execution output is shown.What can you use it for?#
Work often crosses several applications: obtain information, identify the correct record, prepare a report and request the next action. YAADMIN brings supported steps into one conversation. The connected tools determine which parts can be performed; roles, provider access and approval policy determine what a particular user may do.
The table below includes concrete examples from the currently documented integrations. More scenarios explain how compatible workflows, commands and application interfaces can broaden the scope.
| Administration task | How YAADMIN can help |
|---|---|
| Investigate a computer | Use Action1 to inspect a known computer, its reported status and installed software. |
| Review directory information | Find an AD user, inspect their account details and read group memberships. |
| Prepare a software change | Find a real Action1 repository package, inspect its version and request authorized deployment. |
| Read business-system information | Find items, warehouses, stock or movements through a compatible read-only 1C HTTP service. |
| Work with reports | Query an owned stored table, inspect its rows and export results to Excel. |
| Connect another service | Discover and use the tools supplied by a compatible MCP server. |
These examples require the relevant connection, data access and YAADMIN permissions. Connecting one service does not make the capabilities of every other service available.
A practical example: help an employee get a program#
Imagine an employee needs Firefox on their office computer and your organization manages that computer through Action1.
- Identify the computer. Ask “Find OFFICE-PC-07 in our Action1 organization.” Review the actual match; clarify if several records fit.
- Check its software. Ask “Show the programs installed on this computer.” YAADMIN reads the information Action1 reports.
- Find an available package. Ask “Find the Firefox package in our Action1 repository.” Inspect the actual package and deployable version.
- Request the change. If authorized, ask to install that package/version on the selected computer. The tool's permissions and execution policy apply, including approval when required.
- Review the outcome. A submitted job is not the same as a finished installation. Inspect the returned status and provider activity before telling the employee the work is complete.
You can stop after the information steps. You do not need to grant software deployment or script access just to evaluate a useful read-only workflow.
How a request becomes an operation#
- Your request
- Identify the real target
- Select a supported tool
- Check access
- Approval if required
- Execute and review
The AI interprets the request and can choose from tools made available by configured modules and connections. A tool is a specific implemented operation, such as reading one computer's installed software or listing a directory group's members.
YAADMIN checks whether the current user may use the operation. The connected service also applies its own access rules. If the applicable execution policy requires approval, the request waits for a valid decision. Authorized routine operations may run without a new confirmation prompt.
The conversation and Live Activity help you inspect tool calls, results and failures. AI wording can still be mistaken or incomplete, so check the returned data and actual operation state when the outcome matters. A chat answer is not independent proof that a change succeeded.
The parts of YAADMIN, explained#
| Component | Its role |
|---|---|
| Core | The central YAADMIN application: its web workspace, tool registry and execution runtime. Install Core on a Windows host, then access that deployment's web interface. |
| Modules | Connections and functions for particular tasks or systems, such as Action1, AD, 1C, files and target lookup. Each has its own prerequisites and permissions. |
| AI connection | Interprets requests and helps select tools. The configured provider, available model and your account determine the supported AI path. An optional Codex integration has separate setup and user opt-in. |
| MCP connection | Links a compatible external tool server. The server supplies its actual available operations and input requirements. |
| YAADMIN Agent | A separate Windows-to-Core development path for trusted endpoint/session tasks and developing visual interaction. Its inspected checkpoint is not proof of a production-ready deployed Agent. |
| yaadmin.io account | Your website account for purchases, issued license information and eligible technical support. It is separate from signing into your installed Core. |
External service accounts and AI usage can have their own charges. A YAADMIN edition or a free module does not include a third party's subscription.
Who can use it?#
Home users and people managing their own computer can use YAADMIN for personal tasks as well as work: analyze an owned spreadsheet, prepare a downloadable report, or request supported work on their own PC through a configured execution connection. You do not need a company network to have useful tasks. Describe the result in ordinary language; the connected tools and account permissions determine which steps can be carried out.
For personal PC control, choose an execution path that actually supports the task. The inspected Agent implementation includes PowerShell, CMD, scripts, program launch and developing visual interaction with applications. Its current release and Windows/Vision acceptance limits still apply; installing Core alone does not establish unrestricted control of your computer.
People working with data and business processes can use connected read/report tools and implemented workflow operations to bring information from their systems into a conversation. Available actions depend on the actual interfaces and access configured for the task.
IT administrators and help-desk teams can start with computer or directory lookups, then enable carefully scoped changes where useful.
Infrastructure engineers can evaluate supported script execution and provider-backed reporting while retaining control of identities, targets and execution context.
System integrators and automation teams can connect compatible MCP services, expose external workflows such as those built in n8n, or develop trusted modules through the documented SDK. An existing system needs an actual supported interface; describing a desired integration in chat does not implement it.
Technical decision-makers can evaluate one real workflow before selecting an edition, module package or support arrangement. The module browser distinguishes available packages, source capabilities and planned integrations.
APIs, commands and visual interaction#
YAADMIN can use purpose-built integration tools or an authorized execution path. Action1 provides documented PowerShell execution; the inspected YAADMIN Agent implementation includes PowerShell, CMD, scripts and executable launch. Execution takes place in a specific environment and account context, with the relevant permissions and approval rules.
Agent with Vision provides the source-implemented path for observing a Windows application's screen and interacting with its interface inside a bounded task. This broadens the interaction model beyond APIs. Current Agent/Windows/model acceptance and complete full-screen reconstruction remain limited as explained below; it is not a guarantee of compatibility with every application.
Explore commands, Vision and connected workflow scenarios.
Who controls access and changes?#
YAADMIN separates three decisions:
- Authentication: which account is signed in.
- Permission: which tools that account may use.
- Approval: authorization for a particular execution when required by policy.
A connected administrator credential does not mean every chat user receives administrator access. Likewise, confirmation cannot create a missing permission or a missing tool. Approval behavior depends on the operation; there is no universal promise that every action needs a second administrator.
Review roles and permissions and approvals before enabling consequential operations. Stopping a conversation does not undo work already submitted to an external service.
What should you verify before relying on it?#
Read the guide for the exact module you intend to use. The native AD tools described here read directory information; they do not provide password resets or account deletion. The 1C integration needs a compatible published service and is read-only. MCP capabilities depend on successful discovery and authentication with the chosen server.
Agent capture/input and session/process functionality are documented from a separate source checkpoint. Real Windows/model acceptance and complete full-screen reconstruction conformance remain incomplete. Check Agent status before planning desktop automation around it.
The documentation distinguishes inspected source, partial implementation and planned functionality. Commercial edition rights and update coverage are a separate question from whether a particular module is configured, distributed and operational in your deployment. Review licensing and updates for their specific limits.
How to start#
- Install YAADMIN Core using the official installer and the illustrated setup guide.
- Complete first run and open your own deployment's application interface.
- Connect one module or MCP server that matches a real need.
- Assign a narrow read permission and choose an AI path.
- Ask one clear information question and check the target, source and returned result.
- Enable change operations only after reviewing the relevant module's permissions and approval behavior.
Follow the getting-started guide · Browse practical examples · Compare editions · Get help