> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# First working scenario

> Connect the test node, open the terminal and files, give access to the operator and execute the first playbook.

This route introduces the full cycle of Telepúrte on a single Linux test machine, and by the end, you will have a prepared node, operator access, working SSH and files, task result and action record.

## Before you start.

You need an installed panel with HTTPS, a local owner with a configured MFA and a test Linux server with systemd. To add a server, prepare an address, an SSH port and a one-time administrative input. The terminal will need a valid bastion, for tasks - an agent with support for the selected action.

If Telepúrte is not already installed, go through [Installation](https://docs.axottle.com/en/telepurte/installation.md). If the node is already in Axottle, use [import](https://docs.axottle.com/en/telepurte/access.md), then continue with the connection check.

## 1. Add the node.

In **Park Node → Add nodes**, select the connection of an existing Linux server. Specify a clear name, such as `test-web-01`, address and SSH port. Complete a one-time SSH access and complete the final wizard check. When you first connect, the SSH key is automatically fixed; after preparation, check it with an independent trusted source, such as the ISP console.

Wait for the result of the preparation. The appearance of a line in the park is not enough: open the card and check the SSH readiness. If you make a mistake, first disassemble the cause by [connection instructions](https://docs.axottle.com/en/telepurte/nodes.md).

## 2. Check the connection route

On the tab. **Connection.** You can see the address, the SSH port, the transport, and the bastion you've chosen. Direct SSH requires network reachability of the node; a tunnel through an agent is a working agent channel. **Bastions.** SSH/Web entry points should be available.

Open the terminal and execute reading commands:

```bash theme={null}
whoami
hostname
pwd
```

Check the system user and the server name. This checks the actual login, not just the status of the icon in the directory.

## 3. Open the files

Go to the node file tab and open the current user's home directory. View the list, open a small text file and download it. To check the record, use the new test file in the directory where the user is authorized to write.

If the terminal is running and files are not available, check SFTP, authorized root directories and file bans. These actions are subject to separate restrictions; details are in the [Web SFTP](https://docs.axottle.com/en/telepurte/files.md) manual.

## 4. Give access to the operator

Create a local user or invite him in the section **Users**. For the first experience, a separate role with node viewing and access only to `test-web-01` is more convenient. Select a personal Linux account if its preparation is supported by an agent, or specify an existing system login.

Assign a role to the user. For personal registration, wait for the confirmation of preparation on the node. Open another browser session and enter under the operator: complete the MFA, check the visibility of the node and execute `whoami`. Having a meter in the panel does not in itself give SSH.

## 5. Perform the first playbook

In **Playbooks and Schedules**, create a single-action script **Diagnostics host**. This is a reading operation: it returns a snapshot of the CPU, uptime, memory and root disk. Save the playbook, press **Run**, select the test node and check the targets.

Confirm **Run now**. Open a task from a run list or history. Wait for the final result for the selected node and see the result of the step. If the preliminary check indicates that the agent is not ready, first correct its state; SSH connection does not replace agent support.

After that, you can go to [Bash and Ansible](https://docs.axottle.com/en/telepurte/scripts.md), a few steps and [schedules](https://docs.axottle.com/en/telepurte/schedules.md).

## 6. Find traces of work.

Close the terminal and open the **Sessions**. Find the user and node connection, open the record and check the output of test commands. In **Audit**, find the access output and connection events. Check the playbook result in the history of tasks: this is a separate source from the recording of the interactive terminal.

## Verification

The operator logs in under the expected Linux login, the authorized file operation is performed, the diagnosis ends with the result, the session and the access are in history, additionally make sure that the operator does not have access to a node that you did not give him.

## Rollback

Delete the created test file, revoke test access, and check for new login failure. Unnecessary playbook archive; schedule, if created, suspend. Role revocation does not delete user-created files on the server. Disabling test node saves history, but closes new connections.

Feature availability depends on the panel version, bastions, and agents; older builds may not contain the features described.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.