Skip to main content
All CollectionsData VisualizationPresentations
How to ensure consistent Presentation Slides in Ardoq
How to ensure consistent Presentation Slides in Ardoq

Understand how presentation slides may differ by user role and how to make sure they're consistent for all viewers.

Mathias Pedersen avatar
Written by Mathias Pedersen
Updated this week

When sharing presentations in Ardoq, users may see different content based on their role (Admin, Reader, Writer, Contributor, or Public Viewer). This article explains why this happens and how to ensure everyone sees the same information in your presentation.

In Ardoq, the data shown in a presentation depends on two things:

  1. Opened data: The workspaces and components you open in Ardoq; found in the sidebar.

  2. One-Degree-Out: Components directly connected to the Opened Data, shown in the Perspectives section of the sidebar.

Role-Based View Differences:

  • Admins, Readers, and Writers: See both Opened Data and One-Degree-Out Data in the presentation based on their permission to the respective Workpace.

  • Contributors and Public Viewers: See only the Opened Data, which may cause some components to be missing from their view.

How do I ensure consistent Presentation slides?

Follow these steps to make sure your presentation looks the same for all users:

1. Open all the Workspaces you want to display data from

  • In Ardoq, open the workspaces with the data you want to show.

  • Use Perspecitves to Filter out any data you don’t want to include.

Tip: Right-click on the component you want to display and select 'Navigate to workspace'. This will open and take you to the workspace for the selected component. Afterward, you can navigate back to the component you want in context.

2. Save the view to your Presentation

  • Once you've added the data and configured it how you want it, add it to the presentation.

3. Check the Slide as a Public Viewer

  • If you want to verify that everything is displayed as intended, you can temporarily make the presentation public and view the slide in an incognito browser window.

  • If everything looks correct, you can be confident it will display the same for other viewers. Afterward, you can unpublish the presentation again.

Alternative: Use the Viewpoint Builder to avoid these issues

If you want to make sure everyone sees the same content when viewing a slide, consider using the Viewpoint Builder. When creating slides with the Viewpoint Builder:

  • All the necessary data is loaded into the view, so what you see while building the slide is exactly what your audience will see when viewing it in a slide.

This avoids the issue of missing components or different views for different users because the Viewpoint Builder ensures that all necessary data is included automatically. By using the Viewpoint Builder, you can easily create slides that look the same for everyone, regardless of their role or access level.

What’s Coming: Permission Zones Feature (Closed Beta)

Ardoq is working on a new feature called Permission Zones, currently in closed beta for some customers. This feature aims to reduce the discrepancies between what Admins/Writers and Contributors/Public Viewers see in presentations.

With Permission Zones:

  • Admins and Writers will still see more data during slide creation, especially if not all workspaces are open.

  • However, once the slide is created, all users will see the same content, regardless of their role. This should help ensure consistency across presentations for all users.

If you are part of the closed beta, you can expect more simplicity when sharing presentations with mixed audiences.

Conclusion

To avoid confusion when sharing presentations in Ardoq, ensure all necessary data is part of the Opened Data. Test your presentation using an incognito window before sharing it publicly to make sure everyone sees the same thing.

For a more reliable experience, consider using the Viewpoint Builder to ensure that all data is loaded and visible to all users.

For more help, reach out to our Tech Support team.

Did this answer your question?