Some pages within the platform include setup guides.

The intention of these guides is to help you get started by explaining the purpose of the page and the recommended steps to complete in order to gain the intended value from it.

If a page has a setup guide (and you have not already disabled it), the guide appears at the top of the page.

Here's an example of what a setup guide looks like:

Support

The following pages have setup guides implemented:

• Focus dashboard (the default starting page of the platform) (disabled 28.02.2023)

Close guide

To close (remove) a guide, click the "Close guide" button. Guides which have been closed can not be reopened.

Closing of guides is user-specific, meaning that if you close the guide on a page, the guide will still appear for other users (until they close it as well).

To get help, click the question icon in the top, right corner to trigger the context sensitive help menu, or use the keyboard shortcut h.

The help panel displays content from the documentation relevant to the page you're currently visiting.

When multiple documentation pages are relevant, click the title of the individual pages to expand and collapse their associated content.

Whenever you encounter unexpected behaviour from the Platform, we would love to hear about it so that we can fix it.

Please report the issue via email to your designated insight consultant.

Here's the information we require in order to understand the issue as quickly and with as little back and forth as possible.

1. Which user is experiencing the issue?
2. At which URL did the issue occur?
3. Which action did the user perform?
4. What did the user expect to happen?
5. What actually happened?

Any screenshots (including the URL bar) explaining the issue is also greatly appreciated. 

Whenever you feel that there's something missing from the platform, feel free to let us know.

We prefer feature request which focus on the problem the feature is intended to solve, rather than how you envision a solution.

A good way of requesting a feature is by means of a user story.  A user story follows the following format:

As a [role] I would like to [action] in order to [benefit experienced].

A user story has the advantage of exposing:

• Who (what kind of role) is looking to solve the problem
• What are they looking to do
• Which benefit would they gain from completing the action

Here are some examples:

• As a user, I want to upload photos so that I can share photos with others.
• As an administrator, I want to approve photos before they are posted so that I can make sure they are appropriate.
• As a social media manager, I want to tag the photos under specific categories so that I can filter and search the photos for future use.