Portal guide

The portal (portal.fortswift.com) is where you manage your own account, devices and grants.

WARNING

Page names and layout change between versions; the app itself is authoritative.

My account

/account/profile — three sections:

• Account information — email, display name, role, status, registration date, last sign-in;
• Security — sign-in password, two-factor (account code), passkeys (add, recovery codes, password sign-in toggle);
• Resource usage — current consumption.

My devices

/account/devices — the devices under this account.

A device registers itself here on its first sign-in from the client. The list has a Control permission (「控制权限」) column:

• when it can be enabled, an Enable control permission (「启用控制权限」) button — see enabling a host;
• once enabled, Enabled v4 (「已启用 v4」);
• otherwise, a dash.

Device grants

/account/device-grants — split into Pending / Authorized / History.

• Pending — requests submitted by controllers. Approving or rejecting both need the account code. Rejecting frees the slot immediately.
• Authorized — grants in effect and their expiry dates. You can revoke here (account code required), and when issuance has gone wrong there is also a Retry issuance (「重试签发」) action.
• History — rejected, expired and revoked records.

Only owners and administrators can act

Approve, reject and revoke all require the tenant's account owner or administrator role. Other roles can only view, and the page says so.

See device grants for the detail.

Governance controller approvals

/account/trust-approvals — manages the account's governance controller set (the members that take part in the signing quorum).

This page uses the keymachine operator code, not the account code, and the count is bounded by the quorum ceiling.

Day-to-day remote control does not go through here

To give a computer remote-control rights, use Device grants above — it only needs the account code and does not consume governance slots. See controller governance.

Session history

/account/sessions — recent remote-control sessions.

Client downloads

/account/downloads — official installers and first-run steps.

Prefer the website for downloads

Version information on the portal's download page can lag. For the current versioned download links see https://fortswift.com/download.

---

Admin back office

The following live in the admin back office, not in the customer portal, and need administrator rights:

Account management and sub-accounts

Administrators create sub-accounts for team members. The key points:

• the platform has no public registration; every account is issued by an administrator;
• a sub-account hangs off its creator, forming the account tree;
• the parent's quota ceilings constrain the whole subtree — a sub-account can never exceed the tenant root's ceiling;
• each sub-account has its own sign-in credentials, passkeys and account code;
• roles and quotas can be set per account;
• disable the sub-account when someone leaves.

All devices

Every device across every account in the tenant: registered, approved, pending review. Administrators can also enable control permission on a device from here.

Audit log

Sign-ins, create/read/update/delete operations and connections are all written to one place, for after-the-fact investigation — answering "who opened this permission, and when".

For retention period and export capability, the app itself and your plan are authoritative.

Next

• Device grants — the flow you will use most
• Enabling a host — make a machine reachable
• Troubleshooting — an error in the portal