Skip to main content

User Views

User Views are operational interfaces built in Sybot to present data, indicators, and commands based on the needs of a user group.

The Available Widgets section, starting from Data and KPI widgets, describes every component present in the Editor with screenshots, configuration options, and usage instructions.

A view can include:

  • KPIs, charts, tables, and maps;
  • text, images, and layout containers;
  • interactive filters;
  • links to other Sybot pages;
  • commands to start and monitor Workflows;
  • multiple pages organised within the same experience.

The feature must be enabled by the platform administrator.

Lifecycle​

A User View goes through two main states:

  1. Draft, editable in the editor and visible in Preview;
  2. Published, available to authorised users in the Workspace and via the catalogue.

Publishing creates a stable version. Subsequent changes remain in the draft until a new version is published.

Create a view​

  1. Open Designer Workbench.
  2. Select Create and then User View.
  3. Enter the name and description.
  4. Select at least one project.
  5. Select at least one role.
  6. Select Create and open editor: the editor opens in an internal tab.

Projects and roles define the initial perimeter of the view. The user who creates the view becomes its owner.

Open a view​

From the Studio catalogue, two distinct actions are available:

  • Open Editor, to open the draft in Designer Workbench;
  • opening the published view, to use it as an end user.

The second action is available only after the first publication. Modification actions depend on the assigned permissions.

Access from Workspace​

The Workspace shows published and accessible User Views. You can search for them, sort them, and scroll through the results.

A view appears when the user:

  • belongs to at least one of the assigned projects;
  • holds at least one of the required roles;
  • has compatible sharing enabled, when required;
  • can access the published version.

Belonging to a project alone does not automatically grant modification permissions.

Recommended path​

To build a new view:

  1. define pages and layouts in the Visual Editor;
  2. configure data sources and interactions;
  3. verify the Preview;
  4. complete publishing and sharing;
  5. test the view with a profile equivalent to end users.

Expected outcome​

A correctly published User View:

  • appears in the catalogue and in the Workspace of authorised users;
  • loads only the permitted data;
  • maintains layout and behaviour across different screen sizes;
  • displays safe and understandable messages when a source or a Workflow is unavailable.