diff --git a/docs/link/guide/autoresponders.md b/docs/link/autoresponders.md
similarity index 100%
rename from docs/link/guide/autoresponders.md
rename to docs/link/autoresponders.md
diff --git a/docs/link/features/backups.md b/docs/link/backups.md
similarity index 97%
rename from docs/link/features/backups.md
rename to docs/link/backups.md
index b5c4bc8..3112fdc 100644
--- a/docs/link/features/backups.md
+++ b/docs/link/backups.md
@@ -1,6 +1,6 @@
---
title: Backups
-sidebar_position: 20
+sidebar_position: 90
---
## Daily Backups
@@ -26,7 +26,7 @@ If you wish to export data yourself in CSV or similar formats, you can do so thr
## Receiving Regular Database Dumps
-If you are moving away from SR2 Cloud, see [our page on Moving Away](./../moving_away.md).
+If you are moving away from SR2 Cloud, see [our page on Moving Away](./moving_away.md).
This feature is not currently available, however we plan to make available a feature that makes regular database dumps
available to you via our upcoming object storage system, which would be encrypted to your GPG key.
diff --git a/docs/link/channels/e2e_channels/index.md b/docs/link/channels/e2e_channels/index.md
deleted file mode 100644
index fb7a628..0000000
--- a/docs/link/channels/e2e_channels/index.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 50
-sidebar_label: E2EE Channels
----
-
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-# End-to-End Encrypted Channels
-
-
diff --git a/docs/link/channels/e2e_channels/supported_handsets.md b/docs/link/channels/e2e_channels/supported_handsets.md
deleted file mode 100644
index 6e01613..0000000
--- a/docs/link/channels/e2e_channels/supported_handsets.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Mobile Devices
-sidebar_position: 50
-description: E2EE channels require a physical mobile device for operation
----
-
-Signal and WhatsApp channels require a physical mobile device to be set up to create the related accounts, and this
-device must be monitored and maintained to ensure the integrity of the end-to-end encryption and the availability of
-the channel.
-
-## Fully Managed Devices
-
-We will provide a fully managed Android device to support your use of one Signal and one WhatsApp channel, if desired,
-per Link Helpdesk.
-Our devices are provisioned with UK mobile numbers (+44 country code) however you can choose your own username and
-provide any branding you would like to have set up.
-Additional channels will be subject to a fee to cover the additional cost of each required mobile device.
-
-If for any reason you choose to move away from our hosted platform in the future, see [Moving Away](../../moving_away)
-for details on porting your number to your new provider.
-
-## Self-Managed Devices
-
-If due to your organisational policies you require to be in posession of the device, it is possible for you to manage
-your own devices.
-If you require support for these devices, an additional fee will be charged.
-As of May 2026 this will be the same fee as is charged for an additional fully managed device.
-
-:::info
-There are no discounts available for self-managing your device as, in our experience, the increased support costs
-outweigh the hardware and mobile service costs.
-Support provided to self-managed device users is on a best-effort basis. We make no claims regarding expected
-response times, time between failures, or time to recovery for any issues.
-:::
-
-### Hardware and Configuration
-
-* We only support OEM Google Pixel devices and these must be in current security support
- ([end of life dates](https://endoflife.date/pixel)).
-* The device must have a mobile service contract that:
- * has a sufficient monthly allowance for data for operating system and application updates, as well as the messaging
- data which may include audio and video content;
- * allows inbound and outbound calls and SMS; and
- * has a permanently assigned mobile number.
-* The device must not be in use for any other purpose and interactions with the device should only be performed for the
- purpose of monitoring and maintenance.
-* The device should be managed with a Mobile Device Management (MDM) solution to:
- * automatically install operating system and application updates;
- * restrict the installed apps, which may only be installed when signed with a valid certificate from a trusted app
- store;
- * enforce lock timeouts and strong unlock credential requirements;
- * disable unnecessary features that would otherwise provide attack surface (e.g., WiFi and Bluetooth); and
- * provide remote wipe capability.
-
-### Procedures
-
-* The device:
- * must be continuously connected to the mobile network with data access enabled;
- * must be kept turned on and charged, **using a charging system that does not keep the device connected to power 24 hours a day as this will lead to battery failure and risk of fire**;
- * must have sufficient physical security considerations taken (e.g. kept in locked room when unattended);
- * must not have mobile signal blocked from operation (e.g. do not store it in a metal safe);
- * must have well-documented access control policies in place; and
- * must be restarted once a week.
-* Monitor the logs of the MDM to ensure updates are applied.
-* Subscribe to security advisories for Android, Signal, WhatsApp and your MDM solution to endure critical and high
- impact vulnerabilities are patched promptly.
-* Check channel operation regularly and relink the device if needed.
-* Regularly audit the device configuration and procedures, and who can access it.
-
-
-:::warning
-While we can advise you on a configuration for the device, security is a combination of applied configuration,
-physical security and formal processes such as regular internal or external audits.
-Only your organisation is able to ensure these recommendations are followed when self-managing your device.
-For this reason, we do not accept any responsibility related to any security incidents related to your self-management
-of the device.
-:::
\ No newline at end of file
diff --git a/docs/link/channels/index.mdx b/docs/link/channels/index.mdx
deleted file mode 100644
index c68f061..0000000
--- a/docs/link/channels/index.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 20
-sidebar_label: Channels Guide
----
-
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-# Channels Guide
-
-
diff --git a/docs/link/channels/proton.md b/docs/link/channels/proton.md
deleted file mode 100644
index c135dda..0000000
--- a/docs/link/channels/proton.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Proton Mail Channel
-sidebar_label: Proton Mail Channel
-sidebar_position: 55
-description: Using a ProtonMail email account
----
-
-[Proton Mail](https://proton.me/mail) is the largest end-to-end encrypted email hosting service.
-It was launched in 2014 and is headquartered in Geneva, Switzerland.
-It is owned by the non-profit Proton Foundation through its subsidiary Proton AG.
-Proton Mail uses client-side encryption to protect email content and user data before they are sent to Proton Mail
-servers, unlike other common email providers.
-
-The source code for the back end of Proton Mail remains closed-source, but Proton Mail released the source code for the
-web interface, iOS and Android apps, and the [Proton Mail Bridge app](https://github.com/ProtonMail/proton-bridge)
-under an open-source licence.
-
-Although Proton Mail's encryption uses the open standard OpenPGP, and the Link platform support OpenPGP when used with
-other email providers, it is not possible to directly interact with the encryption from the Link platform.
-This is because Proton Mail does not provide the traditional IMAP and SMTP server endpoints to send and receive emails
-and only allows connection via the Proton Mail bridge app which handles all encryption and decryption of messages.
-
-## Requirements
-
-* You must have a paid plan to use the Proton Mail channel as the use of the Proton Mail Bridge app is not possible on
-a free account.
-* Additionally, a user must be dedicated for the use of the helpdesk, it is not sufficient to create an alias on an
-existing user.
-
-## Encryption & Key Management
-
-OpenPGP private keys are created automatically for each Proton Mail account, although these are stored in a way that
-they are not generally available other than when successfully authenticated to the platform.
-In the case of Link, this means that the Proton Mail Bridge app is authenticated and then has access to the OpenPGP
-private key.
-
-It is not currently possible to import public keys of 3rd-party (i.e. non-Proton Mail) email addresses, and so only
-emails between Proton Mail users will be end-to-end encrypted.
-The service also
-[does not support the Autocrypt standard](https://protonmail.uservoice.com/forums/945460-general-ideas/suggestions/32845105-autocrypt-support),
-which allows other clients to import discovered public keys automatically on new conversations.
-The Proton Mail documentation [has more on this topic](https://proton.me/support/proton-mail-encryption-explained).
-
-We will provide you with your public OpenPGP key when the channel is set up, and you can make this discoverable via your
-website, but for conversations with 3rd-party accounts we expect the conversations will only be encrypted in one
-direction and your replies will not be encrypted.
-
-The helpdesk is unaware of the encryption happening in Protonmail, and cannot inform agents when an email that was sent
-or received by the helpdesk was encrypted or not.
-
-## Setting up
-
-If you do not have an organisational account, we can fully manage the Proton Mail account setup including billing.
-Please [contact us](https://www.sr2.uk/contact) to discuss this.
-
-If you have an organisational account,
-[send an invite for the new user](https://proton.me/support/add-users-organization#create-a-new-user) (the new helpdesk
-channel address) to contact@sr2.uk, and email the same address to let us know you are doing this and that you would
-like the channel added to your helpdesk.
-
-Once the setup is complete we will provide you with OpenPGP public key and will also upload it to
-[keys.openpgp.org](https://keys.openpgp.org/) to aid in its discovery by users.
-We can also provide support on setting up Web Key Discovery (WKD) on your custom email domain if desired to further
-increase the chances that inbound emails will be automatically encrypted, although this still cannot help to encrypt
-replies to 3rd-party email services.
\ No newline at end of file
diff --git a/docs/link/channels/e2e_channels/setup.md b/docs/link/e2e_channels.md
similarity index 95%
rename from docs/link/channels/e2e_channels/setup.md
rename to docs/link/e2e_channels.md
index bf8deeb..7937345 100644
--- a/docs/link/channels/e2e_channels/setup.md
+++ b/docs/link/e2e_channels.md
@@ -1,15 +1,12 @@
---
-sidebar_label: Initial Setup
-sidebar_position: 10
+label: E2E channels
+sidebar_position: 40
description: Setting up E2E channels (Signal and WhatsApp)
---
-# Initial setup
+# End-to-end encrypted channels
-:::info
-If you have requested a Signal and/or WhatsApp channel as part of your helpdesk setup, or you have a fully-managed
-handset provided by us, these steps will already have been completed by our support team.
-:::
+## Initial setup
1. Log in to your CDR Link helpdesk admin panel using either ‘Sign in with Google button’ or Sign in with Zammad credentials’:
@@ -140,3 +137,5 @@ You will see a pop up window like the one below:
- Click the blue ‘Save’ button.
🎉 Congrats! Your connection is ready!
+
+## Reconnection
\ No newline at end of file
diff --git a/docs/link/features/index.mdx b/docs/link/features/index.mdx
deleted file mode 100644
index 76069b6..0000000
--- a/docs/link/features/index.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 10
-sidebar_label: Features
----
-
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-# Features
-
-
diff --git a/docs/link/channels/google_channel.md b/docs/link/google_channel.md
similarity index 100%
rename from docs/link/channels/google_channel.md
rename to docs/link/google_channel.md
diff --git a/docs/link/guide/index.mdx b/docs/link/guide/index.mdx
deleted file mode 100644
index 7da5f98..0000000
--- a/docs/link/guide/index.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 20
-sidebar_label: Agents Guide
----
-
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-# Features
-
-
diff --git a/docs/link/hosted.md b/docs/link/hosted.md
index b418acc..0540182 100644
--- a/docs/link/hosted.md
+++ b/docs/link/hosted.md
@@ -4,15 +4,6 @@ sidebar_position: 500
# CDR Link FAQ
-:::warning[CDR Sunset]
-The Center for Digital Resilience will be sunsetting, with all programs and activities drawing to a full close on
-December 31st, 2026.
-Existing CDR users have been contacted and will all be offered to migrate their service contracts to SR2 at time of
-renewal.
-Read more [on our blog](https://www.sr2.uk/posts/2026-link-new-home/).
-:::
-
-
CDR offers hosted Link helpdesk instances managed by [SR2 Communications](https://www.sr2.uk/),
a trusted team within the digital rights community, with a proven track record of securely handling sensitive data.
diff --git a/docs/link/index.mdx b/docs/link/index.mdx
index d0e2312..579a575 100644
--- a/docs/link/index.mdx
+++ b/docs/link/index.mdx
@@ -8,13 +8,14 @@ import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
# Link Helpdesk
-Our secure digital helpdesk platform, Link, is customised and hardened version of [Zammad](https://zammad.com/en),
-an open source, flexible, multi-channel ticketing platform that enables those in need to ask for help, and providers to
-respond.
+:::warning[Under construction]
+This documentation is a work in progress. Please [get in touch with us](mailto:contact@sr2.uk) if you have any questions.
+:::
+
+Our secure digital helpdesk platform, Link, is customised and hardened version of Zammad, an open source, flexible,
+multi-channel ticketing platform that enables those in need to ask for help, and providers to respond.
The helpdesks have integrations with popular messaging apps, including Signal, WhatsApp, and Telegram, making it easier
to securely allow responders to request assistance.
-
-
diff --git a/docs/link/guide/logging_in.md b/docs/link/logging_in.md
similarity index 67%
rename from docs/link/guide/logging_in.md
rename to docs/link/logging_in.md
index 0202231..ce78992 100644
--- a/docs/link/guide/logging_in.md
+++ b/docs/link/logging_in.md
@@ -8,9 +8,6 @@ To log in to your instance, visit the helpdesk URL provided. This will usually e
To begin the login flow, select to login with "SR2 Cloud".
-