> ## 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.

# Link to Axottle

> Entry through Axottle, Agent Connection, Project Rights, SSH Check and Synchronization Diagnostics.

After [set-up](https://docs.axottle.com/en/telepurte/installation.md) Open Telepúrte and log in with the local owner, which allows you to verify the integration and grant rights regardless of the SSO.

## Entrance through Axottle

The user chooses to log in via Axottle, confirms the transition and, if necessary, passes the MFA according to Telepúrte's policy. The external account is linked using the stable Axottle identifier. The matching local username does not combine the two accounts.

Synchronization creates profiles in advance, but does not create a login session or assign a local owner role.

## Addition of nodes

**1. Check the imports**

Open **Import Axottle** to Telepúrte. Make sure the right nodes, their IP and designs are in the directory. Axottle sends inventory after launch and then once per minute.

**2. Launch the connection.**

For one node, press **Add** in its line, for the park - **Add all**. Confirm the Axottle Agent update and start the task.

**3. Wait for the prep.**

The task updates the agent, connects it to Telepúrte with a separate identification, prepares the SSH and checks the host key. It continues to run after the page is closed. The results of successful and unsuccessful connections are shown separately.

**4. Check the terminal.**

After successful preparation, check the owner's SSH access. A configured Telepúrte gateway with an HTTPS route should be available for the browser terminal and Web SFTP.

Re-addition allows you to restore incomplete training. Changing the IP requires a new host identity check. Error connecting Telepúrte to the agent does not in itself mean that the Axottle node is turned off.

## Rights of users and projects

Project membership is transferred from Axottle, which limits access, but does not allow SSH by itself. Use Telepúrte's individual permissions and roles to access.

Axottle also has an explicit user setting **Access to all SSH machines of designated projects**. When enabled, Telepúrte creates controlled access under `root` to the machines of these projects. Disabling revokes this access; separately issued Telepúrte roles and permissions continue to operate within the membership.

> [!WARNING]
>
> Allowance to log in to Axottle, a successful SSO and access to `root` are different rights. Check the final user permissions before transferring access to the park.

File transfers and agent operations have their own limitations, and being able to open a terminal does not mean permission to any file path or bulk task.

## Synchronization and recall

The user list is updated once a minute, and if the fresh list is not received for three minutes, the access of the imported accounts is suspended, including open connections, and the owner's local login remains a separate recovery method.

An inactive or disappeared account is blocked from the recipient. The return of the active state does not include the profile that the local owner disabled in Telepúrte. The disappearance of the node from Axottle also does not delete its history in Telepúrte.

## Typical problems

| Symptoms of | What to Test for | |
| - | - | - |
| Node visible, but terminal inaccessible | Completion of agent connection, SSH key verification, user rights and status of | gateway |
| No Node or User | Synchronization Freshness, Selected Project and Communication Activity with Axottle | |
| Local input but not SSO | Accounting activity in Axottle, MFA and freshness of | user list |
| `ca_conflict` or `config_conflict` | Presence of a former SSH CA; study conflict prior to | trust replacement |
| Connection stopped working after changing IP | Host Re-check and current rights | |
| Health data obsolete | Age of last Axottle image; this is a separate check from readiness of SSH | |

For conflicts of the former SSH CA, the Telepúrte Agents section provides a massive replacement with explicit confirmation. Requires Axottle Agent 1.3.15 or later. Apply it only to nodes that really need to be replaced with the previous binding.

## Further work at Telepúrte

After import, use the [node page](https://docs.axottle.com/en/telepurte/node-workspace.md), [Rols and grants ](https://docs.axottle.com/en/telepurte/roles.md), [terminal ](https://docs.axottle.com/en/telepurte/terminal.md) and [playbooks](https://docs.axottle.com/en/telepurte/playbooks.md). Communication with Axottle is one of the ways to fill the catalog and enter; the remaining features of Telepúrte are described in separate chapters.

## Verification

Under a regular account, check the list of available machines, log in to one allowed node, and opt out for the node outside its rights. After a test revocation of permission, make sure that new login is no longer allowed. For Web SFTP, separately check the allowed path and file operation rights.

## Rollback

Revoke the given role or permission in Telepúrte. If access was given by the Axottle switch, turn it off and wait for the synchronization. Check the remaining independent permissions. Disabling the user in Telepúrte closes his access, but does not delete the servers and the changes already made on them.

The script requires compatible versions of both panels and agents.


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