Sybot Portals
Sybot Portals are authenticated web applications built in the Designer Workbench. They consolidate content, data, and operational actions into dedicated pages, using default widgets or custom HTML, CSS, and JavaScript components.
Functionality is visible only when enabled by the platform administrator. Each Portal belongs to a single Project and remains subject to both the Project permissions and the specific Portal permissions.
Create a Portal
- Open the Designer Workbench.
- Select Create → Portal.
- Specify the name and description.
- Choose a Project in which you have the Owner or Editor role.
- Select Create and open editor.
The new Portal opens in a Workbench tab with an initial source repository, a page, and a theme already set up. Unlike Workflows and BPMN, a Portal cannot be added to multiple Projects. In the Project object addition modal, accessible Portals are visible; those belonging to another Project are disabled and show the reason, without being moved.
Open a Portal
Accessible Portals appear in the Studio Catalogue, in the details of the relevant Project, and in the Workbench Open Portal panel.
Based on permissions, the following options are available:
- Open Editor, also in read-only mode for users who need to consult or review;
- Open Preview, to check the draft without publishing it;
- Open Portal, when an active version is available.
Permissions
| Portal Permission | Main Operations |
|---|---|
| Viewer | Consult the editor in read-only mode and the active Portal within your perimeter. |
| Designer | Edit pages, widgets, files, and custom code. |
| Developer | Edit pages, widgets, files, and custom code. |
| Reviewer | Consult sources and releases for review. |
| Publisher | Approve and publish allowed releases. |
| Owner | Manage access, audience, and all Portal operations. |
Higher-level permissions also require a modifiable role in the Project. A Project Viewer member can receive only the Viewer Portal permission.
Access to the Published Portal
Access always requires an authenticated Sybot session. The user must also belong to the Project and be authorised via an individual permission or a role included in the Portal's audience.
If the Portal does not open, check with the Owner:
- that the Portal is active;
- that the user still belongs to the Project;
- that the individual permission or audience role is present;
- that the publishing destination is available.
To design pages and components, consult Editor e widget.