Skip to main content
Skip table of contents

Scroll Documents Legacy Features

After careful consideration, we have made the decision to sunset the following legacy features within Scroll Documents:

This article aims to offer detailed insights and guidance regarding this change.

Why Are These Features Going Away?

Our team is dedicated to bringing advanced authoring and content management functionality to Confluence, so it can serve as a collaborative documentation authoring platform. However, features like read requests and the document reader were originally designed for smaller documents.

For larger documentation projects (over 100 pages), these features weren't the best fit. They caused slow loading times and weren't used much.

We're focused on bringing you new and improved features that make Confluence even better for creating and managing all your documentation, big or small!

Why is the Document reader going away?

The Document reader is being sunsetted for the following reasons:

  • Limited usefulness: While the Document reader lets you view all pages at once, most users search for specific information rather than reading an entire document.

  • Technical limitations: The Document reader relies on an "export view" that doesn't always display macros and Confluence content types correctly, leading to a frustrating user experience.

  • Redundancy: The Document reader offers similar functionality to the standard Confluence page view, but with fewer features and potential display issues.

Alternatives to the Document reader
Depending on your use case, we recommend the following alternatives to the Document reader:

  • Publishing: Use the Publish to Confluence option to publish a version, variant, or language to a dedicated location in Confluence, where it can be accessed by your readers.

  • Authoring and review: For authoring and review, we recommend using Confluence's native page view. If your Scroll Document contains variants, use the new Variant preview to review which variants a page exists in and its conditional content before exporting it with Scroll Exporters, publishing it to another Confluence space, or displaying it in Viewport.

Why are Read requests going away?

The Read requests are being sunsetted for the following reasons:

  • Mismatched with workflow: Document reviews typically happen page by page, not for an entire version at once. Scroll Documents' current read requests only work for whole versions, which isn't practical for most internal workflows.

  • Tied to document reader: Read requests rely on the Document reader, which is also being sunsetted.

  • Low usage: Very few users actively use read requests.

Alternatives to the Read requests

Instead of relying on Read requests, use Confluence's built-in features to notify your audience or reviewers about new or updated pages:

  • Share a page: Use the Share option to send a page link and a personalized message directly to your reviewers' email inboxes. You can read more about it here: Share a Page or Blog Post

  • @-Mentions: @-mention specific users and request their feedback in the page or comments. For more information see: Mentions

What Does This Mean for Existing Users?

No new updates

In September 2024, we announced the upcoming sunsetting of the Document Reader and Read requests, classifying them as legacy features. From that point forward, no new updates or improvements were made to these features.

With one of the later releases in January 2025, the following changes have occurred:

  • The Document Reader will be hidden from the user interface.

  • If you're not actively using Read requests this feature will also hidden from the user interface. For example, if there are no active read requests in a document.

Eventually, these features will be fully removed from the Scroll Documents user interface.

What if I still need the hidden features?

For a limited time, you can still reinstate legacy features in all spaces via the admin settings. To do this, go to General configuration > Scroll Documents > Settings > Legacy Features.

Please note that we cannot guarantee full functionality of legacy features with every new release.

What happens to old read requests and links to versions I’ve shared?

The following will happen to old read requests and shared links:

  • You will still be able to access old read requests, even if the Read request feature has been hidden.

  • Links shared to previously saved versions in the Document reader will continue to work as expected.

Support

Since September 30th, 2024, the K15t support team is no longer offering assistance for these features. Instead, we recommend using the already available alternative solutions mentioned earlier in this article.

Thank you!

We sincerely appreciate your trust and support as Scroll Documents users. Your feedback has been invaluable in shaping our product, and we're dedicated to providing you with even better features and solutions in the future.

If you have any questions or concerns during this transition, please don't hesitate to contact us. We're here to help every step of the way and look forward to hearing your thoughts on the upcoming improvements.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.