---
title: "Connect to servers"
description: "Request a work session to connect to a registered Alpacon server. Check access requirements and launch the browser terminal, editor, or file transfer tools."
---

> Full documentation index: https://docs.alpacax.com/llms.txt

# Connect to servers

Request a work session to connect to a server and launch the tools you need.

## Session-based access

A [work session](/use/work-sessions/) must be **Active** before you launch its allowed tools, including the browser terminal, file transfer, code editor, and command execution.

The first time you click **Connect**, a brief hint explains this flow: "Request a session to connect. Server access is available once approved."

## Connect to a server

1. Go to the **Servers** page.
2. Find the server you want to work on.
3. Click **Connect**—on the server card, or on the server detail page.
4. The session request form opens with that server already selected.
5. Choose the [features](/reference/work-session-features/) you need, add a purpose and duration, and submit. See [Request a session](/use/work-sessions/create/).

When the request is allowed and its start time arrives, the session becomes **Active** and you can launch its features. Your workspace's [access rules](/use/approvals/#access-rules) determine whether the request needs approval.

You can also add several servers to one session. Start from any server's **Connect** button, then add more servers in the request form.

## Requirements

The **Connect** button is available only when:

- The server is **commissioned** and **Online**.
- You belong to a user group assigned to the server (or are a workspace administrator).
- You're a workspace member.

If the server is offline or not commissioned, **Connect** is disabled and the card shows **No connection** instead of the server address.

## Launch tools from the session

Once the session is active, open its **Session** tab and find the server's row:

- Use **Terminal**, **Files**, or **Editor** on that server to open a feature included in the session.
- **Execute commands** and **Port forwarding** are used from the [Alpacon CLI](/reference/cli/) after you attach to the session.

On **Windows servers**, the code editor is not available. Web terminal, file transfer, and command execution are supported, and port forwarding works with Alpamon 2.5.1 or later. See [Windows servers](/reference/platforms/windows/).

For the full walkthrough—launching, attaching from the CLI, extending, and ending a session—see [Use a session](/use/work-sessions/detail/).

## Account selection

When you launch a feature, you work as a specific account on the remote server: the account you chose under **Connect as** when you requested the session. By default that's your own account, and you use [sudo with MFA](/use/work-sessions/terminal/sudo-with-mfa/) for privileged actions. The choice works the same on Linux, macOS, and Windows servers. See [Account selection](/use/work-sessions/account-selection/) for details.

The MFA verification that `sudo` asks for can be completed only from an interactive sign-in, in the web console or in the CLI after `alpacon login` without an API token. See [Which sign-ins can complete the verification](/use/work-sessions/terminal/sudo-with-mfa/#which-sign-ins-can-complete-the-verification).

On **Windows**, the selected account is an audit label only: features run as SYSTEM regardless of the account shown. See [Windows servers](/reference/platforms/windows/#permissions-and-identity-on-windows).

### Who can connect as which account

Which account you can open a session as depends on your role on the server:

| Who you are | Account you can connect as |
| --- | --- |
| Member of a user group assigned to the server | Your own account only |
| Owner or manager of an assigned group, a [maintainer of the server](/use/workspace/settings/roles/#permission-inheritance), or a user with the Staff or Superuser role | Any existing account on the server, except `root` |

Connecting as `root` additionally requires **Direct root login** to be enabled for the workspace. This setting is off by default; while it's off, use [sudo with MFA](/use/work-sessions/terminal/sudo-with-mfa/) for root-level actions. In every case, the target account must already exist on the server with login enabled. See [Account selection](/use/work-sessions/account-selection/).

Access with a personal [API access token](/use/settings/api-tokens/) or a [service token](/use/iam/applications/service-tokens/) doesn't go through the work session request flow. What those tokens can reach is controlled by each token's **Server ACL**—the list of allowed servers configured on the token.

## Troubleshooting

**Connect button is disabled:**

- Confirm the server is Online and commissioned.
- Confirm you're assigned to a user group with access to the server.
- Check [Alpacon status](https://status.alpacax.com) for an ongoing platform incident.

**Can't launch a feature:**

- The session must be **Active** and within its time window.
- The code editor and port forwarding require those features to be enabled on the server. See [Tunnel and code editor](/use/servers/manage/#tunnel-and-code-editor).

**A tool won't open in the browser:**

- Disable your browser's popup blocker, then retry.

## Related docs

- [Work sessions overview](/use/work-sessions/)
- [Request a session](/use/work-sessions/create/)
- [Session features](/reference/work-session-features/)
- [Account selection](/use/work-sessions/account-selection/)

Source: https://docs.alpacax.com/use/servers/connect/
